Error request entity too large

Question

I m receiving the following error with express   Error  request entity too large     at module exports   Users michaeljames Documents Projects Proj mean node modules express node modules connect node modules raw-body index js 16 15      at json   Users michaeljames Documents Projects Proj mean node modules express node modules connect lib middleware json js 60 5      at Object bodyParser  as handle    Users michaeljames Documents Projects Proj mean node modules express node modules connect lib middleware bodyParser js 53 5      at next   Users michaeljames Documents Projects Proj mean node modules express node modules connect lib proto js 193 15      at Object cookieParser  as handle    Users michaeljames Documents Projects Proj mean node modules express node modules connect lib middleware cookieParser js 60 5      at next   Users michaeljames Documents Projects Proj mean node modules express node modules connect lib proto js 193 15      at Object logger   Users michaeljames Documents Projects Proj mean node modules express node modules connect lib middleware logger js 158 5      at next   Users michaeljames Documents Projects Proj mean node modules express node modules connect lib proto js 193 15      at Object staticMiddleware  as handle    Users michaeljames Documents Projects Proj mean node modules express node modules connect lib middleware static js 55 61      at next   Users michaeljames Documents Projects Proj mean node modules express node modules connect lib proto js 193 15  TypeError   Users michaeljames Documents Projects Proj mean app views includes foot jade 31     29  script type  text javascript   src   js socketio connect js       30      gt  31  if  req host  localhost       32        Livereload script rendered      33      script type  text javascript   src  http   localhost 35729 livereload js         34    Cannot set property  host  of undefined     at eval  eval at  lt anonymous gt    Users michaeljames Documents Projects Proj mean node modules jade lib jade js 152 8    lt anonymous gt  273 15      at  Users michaeljames Documents Projects Proj mean node modules jade lib jade js 153 35     at Object exports render   Users michaeljames Documents Projects Proj mean node modules jade lib jade js 197 10      at Object exports renderFile   Users michaeljames Documents Projects Proj mean node modules jade lib jade js 233 18      at View exports renderFile  as engine    Users michaeljames Documents Projects Proj mean node modules jade lib jade js 218 21      at View render   Users michaeljames Documents Projects Proj mean node modules express lib view js 76 8      at Function app render   Users michaeljames Documents Projects Proj mean node modules express lib application js 504 10      at ServerResponse res render   Users michaeljames Documents Projects Proj mean node modules express lib response js 801 7      at Object handle   Users michaeljames Documents Projects Proj mean config express js 82 29      at next   Users michaeljames Documents Projects Proj mean node modules express node modules connect lib proto js 188 17   POST  api 0 1 people 500 618ms   I am using meanstack  I have the following use statements in my express js    Set Request Size Limit app use express limit 100000000      Within fiddler I can see the content-length header with a value of  1078702  I believe this is in octets  this is 1 0787 megabytes   I have no idea why express is not letting me post the json array I was posting previously in another express project that was not using the mean stack project structure

User · Answer

in my case    setting parameterLimit 50000 fixed the problem  app use  bodyParser json  limit   50mb       app use bodyParser urlencoded     limit   50mb     extended  true    parameterLimit 50000

User · Answer

Little old post but I had the same problem  Using express 4   my code looks like this and it works great after two days of extensive testing   var url           require  url        homePath        dirname               apiV1         require homePath    api v1 start        bodyParser    require  body-parser   json  limit  100mb      module exports   function app       app get      function  req  res            res render  homePath    public template index                 app get   api v1    function  req  res            var query   url parse req url  query          if    query                 res redirect                         apiV1   GET   query  function  response                res json response                            app get      function  req res            res redirect                    app post   api v1    bodyParser  function  req  res            if    req body                 res json                   status   error                   response   No data to parse                                    apiV1   POST   req body  function  response                res json response

User · Answer

The setting below has worked for me Express 4 16 1 app use bodyParser json   limit   50mb      app use bodyParser urlencoded     limit   50mb     extended  false       Nginx client max body size 50m client body temp path  data temp

User · Answer

I don t think this is the express global size limit  but specifically the connect json middleware limit  This is 100kb by default when you use express bodyParser   and don t provide a limit option   Try   app post   api 0 1 people   express bodyParser  limit   5mb     yourHandler

User · Answer

I had the same error recently  and all the solutions I ve found did not work   After some digging  I found that setting app use express bodyParser  limit   50mb      did set the limit correctly    When adding a console log  Limit file size    limit   in node modules express node modules connect lib middleware json js 46 and restarting node  I get this output in the console    Limit file size  1048576 connect multipart   will be removed in connect 3 0 visit https   github com senchalabs connect wiki Connect-3 0 for alternatives connect limit   will be removed in connect 3 0 Limit file size  52428800 Express server listening on port 3002   We can see that at first  when loading the connect module  the limit is set to 1mb  1048576 bytes   Then when I set the limit  the console log is called again and this time the limit is 52428800  50mb   However  I still get a 413 Request entity too large   Then I added console log  Limit file size    limit   in  node modules express node modules connect node modules raw-body index js 10 and saw another line in the console when calling the route with a big request  before the error output      Limit file size  1048576   This means that somehow  somewhere  connect resets the limit parameter and ignores what we specified  I tried specifying the bodyParser parameters in the route definition individually  but no luck either   While I did not find any proper way to set it permanently  you can  patch  it in the module directly  If you are using Express 3 4 4  add this at line 46 of node modules express node modules connect lib middleware json js    limit   52428800     for 50mb  this corresponds to the size in bytes   The line number might differ if you don t run the same version of Express  Please note that this is bad practice and it will be overwritten if you update your module   So this temporary solution works for now  but as soon as a solution is found  or the module fixed  in case it s a module problem  you should update your code accordingly   I have opened an issue on their GitHub about this problem    edit - found the solution   After some research and testing  I found that when debugging  I added app use express bodyParser  limit   50mb       but after app use express json      Express would then set the global limit to 1mb because the first parser he encountered when running the script was express json    Moving bodyParser above it did the trick   That said  the bodyParser   method will be deprecated in Connect 3 0 and should not be used  Instead  you should declare your parsers explicitly  like so    app use express json  limit   50mb      app use express urlencoded  limit   50mb        In case you need multipart  for file uploads  see this post    second edit   Note that in Express 4  instead of express json   and express urlencoded    you must require the body-parser module and use its json   and urlencoded   methods  like so   var bodyParser   require  body-parser    app use bodyParser json  limit   50mb      app use bodyParser urlencoded  limit   50mb   extended  true       If the extended option is not explicitly defined for bodyParser urlencoded    it will throw a warning  body-parser deprecated undefined extended  provide extended option   This is because this option will be required in the next version and will not be optional anymore  For more info on the extended option  you can refer to the readme of body-parser    third edit   It seems that in Express v4 16 0 onwards  we can go back to the initial way of doing this  thanks to  GBMan for the tip    app use express json  limit   50mb      app use express urlencoded  limit   50mb

User · Answer

If you are using express json   and bodyParser together it will give error as express sets its own limit   app use express json     app use express urlencoded   extended  false        remove above code and just add below code  app use bodyParser json   limit   200mb       app use bodyParser urlencoded   limit   200mb    extended  true  parameterLimit  1000000

User · Answer

The following worked for me    Just use   app use bodyParser  limit   50mb        that s it   Tried all above and none worked  Found that even though we use like the following   app use bodyParser     app use bodyParser  limit   50mb      app use bodyParser urlencoded  limit   50mb        only the 1st app use bodyParser     one gets defined and the latter two lines were ignored   Refer  https   github com expressjs body-parser issues 176    see  dougwilson commented on Jun 17  2016

User · Answer

I too faced that issue  I was making a silly mistake by repeating the app use bodyParser json    like below   app use bodyParser json    app use bodyParser json   limit   50mb        by removing app use bodyParser json     solved the problem

User · Answer

If someone tried all the answers  but hadn t had any success yet and uses NGINX to host the site add this line to  etc nginx sites-available  client max body size 100M   100mb

User · Answer

I ve used another practice for this problem with multer dependancie   Example    multer   require  multer     var uploading   multer     limits   fileSize  1000000  files 1        exports uploadpictureone   function req  res      cloudinary uploader upload req body url  function result        res send result             module exports   function app        app route   api upload   uploading  all uploadPolicy isAllowed           post upload uploadpictureone

User · Answer

For me the main trick is   app use bodyParser json     limit   20mb        app use bodyParser urlencoded     limit   20mb     parameterLimit  100000    extended  true         bodyParse json first bodyParse urlencoded second

User · Answer

A slightly different approach - the payload is too BIG  All the helpful answers so far deal with increasing the payload limit  But it might also be the case that the payload is indeed too big but for no good reason  If there s no valid reason for it to be  consider looking into why it s so bloated in the first place   Our own experience  For example  in our case  an Angular app was greedily sending an entire object in the payload  When one bloated and redundant property was removed  the payload size was reduced by a factor of a 100  This significantly improved performance and resolved the 413 error

User · Answer

For those who start the NodeJS app in Azure under IIS  do not forget to modify web config as explained here Azure App Service IIS  quot maxRequestLength quot  setting

User · Answer

In my case it was not enough to add these lines   var bodyParser   require  body-parser    app use bodyParser json  limit   50mb      app use bodyParser urlencoded  limit   50mb   extended  true      I tried adding the parameterLimit option on urlencoded function as the documentation says and error no longer appears   The parameterLimit option controls the maximum number of parameters that are allowed in the URL-encoded data  If a request contains more parameters than this value  a 413 will be returned to the client  Defaults to 1000   Try with this code  var bodyParser   require  body-parser    app use bodyParser json  limit   quot 50mb quot      app use bodyParser urlencoded  limit   quot 50mb quot   extended  true  parameterLimit 50000

User · Answer

In my case removing Content-type from the request headers worked

User · Answer

Express 4 17 1 app use  express urlencoded        extended  true      limit   50mb         Demo csb

User · Answer

2016  none of the above worked for me until i explicity set the  type  in addition to the  limit  for bodyparser  example     var app   express      var jsonParser         bodyParser json  limit 1024 1024 20  type  application json       var urlencodedParser   bodyParser urlencoded   extended true limit 1024 1024 20 type  application x-www-form-urlencoded        app use jsonParser     app use urlencodedParser

User · Answer

In my case the problem was on Nginx configuration  To solve it I have to edit the file   etc nginx nginx conf and add this line inside server block   client max body size 5M    Restart Nginx and the problems its gone  sudo systemctl restart nginx

User · Answer

After  o many tries I got my solution  I have commented this line  app use bodyParser json       and I put  app use bodyParser json  limit   50mb       Then it works

User · Answer

For express  4 16 0  express json with limit works directly  app use express json  limit   50mb

User · Answer

for me following snippet solved the problem   var bodyParser   require  body-parser    app use bodyParser json  limit   50mb

User · Answer

I faced the same issue recently and bellow solution workes for me   Dependency    express  gt  gt  version   4 17 1 body-parser  gt  gt  version quot   1 19 0   const express   require  express    const bodyParser   require  body-parser     const app   express     app use bodyParser json  limit   50mb      app use bodyParser urlencoded  limit   50mb   extended  true      For understanding   HTTP 431   The HTTP 413 Payload Too Large response status code indicates that the request entity is larger than limits defined by server  the server might close the connection or return a Retry-After header field

User · Answer

The better use you can specify the limit of your file size as it is shown in the given lines   app use bodyParser json  limit   10mb   extended  true    app use bodyParser urlencoded  limit   10mb   extended  true      You can also change the default setting in node-modules body-parser then in the lib folder  there are JSON and text file  Then change limit here  Actually  this condition pass if you don t pass the limit parameter in the given line app use bodyParser json  limit   10mb   extended  true

[javascript] Error: request entity too large

Examples related to javascript

Examples related to node.js

Examples related to http

Examples related to express