Closed cat-ninja closed 1 year ago
@shubhendumadhukar do you feel comfortable switching the text middleware config to a wildcard? I can prepare a PR.
Sure, go ahead. I was actually looking into ways to make it a configurable input, but haven't been able to give it much thought.
:tada: This issue has been resolved in version 0.14.3 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Describe the bug While trying to integrate a middleware for requests with
multipart/form-data
content type I kept seeingPayloadTooLargeError: request entity too large
error coming from express despite it hadmulter
middleware installed and configured to accept files of any size.Here is the stack trace:
At the 4th line from the top I noticed the error is coming from
textParser
, which, I assume, is called internally by thetext()
middleware. Going trough the sources I noticed thattype
configuration for thetext
middleware is configured to returntrue
by default. So right now this middleware will be responsible for processing everything that is notapplication/json
orapplication/x-www-form-urlencoded
.I see two possible solutions here:
type
to a wildcard such astext/*
, so it wont override any other content types middlewares.limit
option to thetext
middleware with some size (ielimit: '100mb'
) so it'll be possible to accept relatively big files.@shubhendumadhukar what do you think?
To Reproduce Steps to reproduce the behavior:
{}
HTTP/1.1 200 OK Content-Type: text/html