Error: Request Entity Too Large #710

laddi · 2014-07-11T14:28:21Z

We are trying to do some json parsing with a large file in a server route and run into this problem: "Error: Request Entity Too Large"

Instead of having to manually edit the package code it would be nice to have some kind of way to set the bodyParser limit in the configuration.

(same issue as here: http://stackoverflow.com/questions/23899209/setting-request-limit-in-a-meteor-js-app)

All help greatly appreciated.

cmather · 2014-07-13T17:31:58Z

Ah yes this should be much improved. I think the body parser is actually being used in Meteor core too. In the next major version of IR you can add connect middleware directly to the router and I won't be adding any middleware by default. So that might fix this issue. But if Meteor is already including bodyParser middleware upstream, then I guess you'd have to configure that too. As a short-term hack, can you configure the bodyParser middleware after it's been initialized? And just get to it through the connectHandlers array? I'll try to see if that's possible.

cmather · 2014-07-13T17:36:47Z

Meh looks hard to set the options after the fact. I'm not sure why we force using this middleware anyway. I would take a PR to devel to remove it. That way you can set it up yourself using WebApp.connectHandlers.use(...).

cmather · 2014-07-26T16:12:59Z

This is fixed in the refactor branch where you can add your own middleware. Due to be released sometime around the Meteor 0.9 release.

gerwinbrunner · 2014-09-16T13:24:27Z

This is still in the refactor branch, right?
When do you plan to put release those changes?

gerwinbrunner · 2014-09-26T21:12:28Z

Any timeframe on this?

gerwinbrunner · 2014-10-15T16:53:02Z

@cmather This is still now working right?

gerwinbrunner · 2014-10-22T16:31:07Z

Any updates on this?

tmeasday · 2014-10-23T02:15:39Z

@gerwinbrunner yes I think you can add your own middleware with a line line

Router.use(Router.bodyParser.urlencoded());

gerwinbrunner · 2014-10-23T09:25:16Z

@tmeasday It seems that this feature is only available in a version that is not yet available thru the regular packaging system. Can you point me to some resource on how I can easily add a package directly from a github url? Is there an easy way?

I did the following command:

meteor add iron:router

So is there something similar to add a package with an github url?
Somehing like this:

meteor add iron:router https://github.com/EventedMind/iron-router/

Or what is the easiest way for me to use this feature you mentioned above?

Thanks,
Gerwin

P.S.: Sorry if this is a stupid question, but I was not able to find any good solution yet.

tmeasday · 2014-10-23T21:07:51Z

Hey @gerwinbrunner - sorry. You can install the latest pre-release of IR 1.0 with meteor add iron:router@1.0.0-pre4

gerwinbrunner · 2014-10-27T15:36:10Z

@tmeasday Thanks. I'll give it a try.

gerwinbrunner · 2014-11-09T20:03:30Z

@tmeasday: Just tried it with version 1.0.1 and I get the following error:

W20141109-21:02:53.792(1)? (STDERR) /Users/ap/.meteor/packages/meteor-tool/.1.0.35.k5cfzw++os.osx.x86_64+web.browser+web.cordova/meteor-tool-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/future.js:173
W20141109-21:02:53.792(1)? (STDERR)                         throw(ex);
W20141109-21:02:53.792(1)? (STDERR)                               ^
W20141109-21:02:53.795(1)? (STDERR) TypeError: Cannot call method 'urlencoded' of undefined
W20141109-21:02:53.796(1)? (STDERR)     at server/router/api-routes.coffee:3:29
W20141109-21:02:53.796(1)? (STDERR)     at /Users/ap/Documents/workspaces/VilangoWork/le3_meteor_app_2/meteor/.meteor/local/build/programs/server/app/server/router/api-routes.coffee.js:51:3
W20141109-21:02:53.796(1)? (STDERR)     at /Users/ap/Documents/workspaces/VilangoWork/le3_meteor_app_2/meteor/.meteor/local/build/programs/server/boot.js:168:10
W20141109-21:02:53.796(1)? (STDERR)     at Array.forEach (native)
W20141109-21:02:53.796(1)? (STDERR)     at Function._.each._.forEach (/Users/ap/.meteor/packages/meteor-tool/.1.0.35.k5cfzw++os.osx.x86_64+web.browser+web.cordova/meteor-tool-os.osx.x86_64/dev_bundle/lib/node_modules/underscore/underscore.js:79:11)
W20141109-21:02:53.796(1)? (STDERR)     at /Users/ap/Documents/workspaces/VilangoWork/le3_meteor_app_2/meteor/.meteor/local/build/programs/server/boot.js:82:5

A call to Router.bodyParser gives me undefined

Do I need to do something else?

gerwinbrunner · 2014-11-09T20:20:14Z

@tmeasday

I also tried this:
Router.use( Iron.Router.bodyParser.urlencoded(), {where: 'server'} );

And it gave me this error:

W20141109-21:19:10.215(1)? (STDERR) Sun, 09 Nov 2014 20:19:10 GMT body-parser deprecated undefined extended: provide extended option at app/server/router/api-routes.coffee.js:4:35
W20141109-21:19:10.218(1)? (STDERR) 
W20141109-21:19:10.218(1)? (STDERR) /Users/ap/.meteor/packages/meteor-tool/.1.0.35.k5cfzw++os.osx.x86_64+web.browser+web.cordova/meteor-tool-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/future.js:173
W20141109-21:19:10.219(1)? (STDERR)                         throw(ex);
W20141109-21:19:10.219(1)? (STDERR)                               ^
W20141109-21:19:10.223(1)? (STDERR) TypeError: Object function router(req, res, next) {                                                          // 13
W20141109-21:19:10.223(1)? (STDERR)     //XXX this assumes no other routers on the parent stack which we should probably fix      // 14
W20141109-21:19:10.223(1)? (STDERR)     router.dispatch(req.url, {                                                                // 15
W20141109-21:19:10.223(1)? (STDERR)       request: req,                                                                           // 16
W20141109-21:19:10.223(1)? (STDERR)       response: res                                                                           // 17
W20141109-21:19:10.223(1)? (STDERR)     }, next);                                                                                 // 18
W20141109-21:19:10.224(1)? (STDERR)   } has no method 'use'
W20141109-21:19:10.224(1)? (STDERR)     at server/router/api-routes.coffee:3:7
W20141109-21:19:10.224(1)? (STDERR)     at /Users/ap/Documents/workspaces/VilangoWork/le3_meteor_app_2/meteor/.meteor/local/build/programs/server/app/server/router/api-routes.coffee.js:47:3
W20141109-21:19:10.224(1)? (STDERR)     at /Users/ap/Documents/workspaces/VilangoWork/le3_meteor_app_2/meteor/.meteor/local/build/programs/server/boot.js:168:10
W20141109-21:19:10.224(1)? (STDERR)     at Array.forEach (native)
W20141109-21:19:10.224(1)? (STDERR)     at Function._.each._.forEach (/Users/ap/.meteor/packages/meteor-tool/.1.0.35.k5cfzw++os.osx.x86_64+web.browser+web.cordova/meteor-tool-os.osx.x86_64/dev_bundle/lib/node_modules/underscore/underscore.js:79:11)
W20141109-21:19:10.224(1)? (STDERR)     at /Users/ap/Documents/workspaces/VilangoWork/le3_meteor_app_2/meteor/.meteor/local/build/programs/server/boot.js:82:5

tmeasday · 2014-11-09T23:09:21Z

Hi @gerwinbrunner

try

Router.onBeforeAction( Iron.Router.bodyParser.urlencoded(), {where: 'server'} );

gerwinbrunner · 2014-11-09T23:41:01Z

@tmeasday
Thanks for your quick reply. I was able to set the bodyParser now.
I still get the error :(

W20141110-00:39:25.207(1)? (STDERR) Error: request entity too large
W20141110-00:39:25.207(1)? (STDERR)     at makeError (/Users/ap/.meteor/packages/iron:router/.1.0.1.1uflvuf++os+web.browser+web.cordova/npm/node_modules/body-parser/node_modules/raw-body/index.js:184:15)
W20141110-00:39:25.207(1)? (STDERR)     at module.exports (/Users/ap/.meteor/packages/iron:router/.1.0.1.1uflvuf++os+web.browser+web.cordova/npm/node_modules/body-parser/node_modules/raw-body/index.js:40:15)
W20141110-00:39:25.207(1)? (STDERR)     at read (/Users/ap/.meteor/packages/iron:router/.1.0.1.1uflvuf++os+web.browser+web.cordova/npm/node_modules/body-parser/lib/read.js:62:3)
W20141110-00:39:25.207(1)? (STDERR)     at jsonParser (/Users/ap/.meteor/packages/iron:router/.1.0.1.1uflvuf++os+web.browser+web.cordova/npm/node_modules/body-parser/lib/types/json.js:87:5)
W20141110-00:39:25.207(1)? (STDERR)     at packages/iron:router/lib/router.js:264
W20141110-00:39:25.207(1)? (STDERR)     at _.extend.withValue (packages/meteor/dynamics_nodejs.js:56)
W20141110-00:39:25.208(1)? (STDERR)     at hookWithOptions (packages/iron:router/lib/router.js:263)
W20141110-00:39:25.208(1)? (STDERR)     at boundNext (packages/iron:middleware-stack/lib/middleware_stack.js:245)
W20141110-00:39:25.208(1)? (STDERR)     at runWithEnvironment (packages/meteor/dynamics_nodejs.js:108)
W20141110-00:39:25.208(1)? (STDERR)     at packages/meteor/dynamics_nodejs.js:121

Any ideas?

tmeasday · 2014-11-09T23:43:21Z

I think maybe it's a different body parser you need @gerwinbrunner ? I don't really know too much about this but by the sounds of it "urlencoded" probably doesn't deal with the body of the request?

gerwinbrunner · 2014-11-10T14:16:45Z

I got it working by forking iron:router and changing the file global_router.js to this:

Router = new Iron.Router;
if (Meteor.isServer) {
  Router.onBeforeAction(Iron.Router.bodyParser.json({limit: "10mb"}));
}

Just adding the line in my own code did not fix the error, so I had to fork and change the original.
But now it works. :)

landland · 2015-01-30T18:51:05Z

I'm running into this issue as well. Any chance we can up the limit in iron router?

travisdahl · 2015-02-08T09:59:42Z

+1. Trying to upload 3 images as base64 (i save to s3 on server) but limit wont allow

Clarification: I have the upload and everything working with small files, just having problems with the limit.

cmather · 2015-02-08T19:42:29Z

@gerwinbrunner has the right idea. But you can put this in Router.configureBodyParsers on the server. Look in lib/router_server.js for how it's done in source. Here's an example:

Router.configureBodyParsers = function () {
  Router.onBeforeAction(Iron.Router.bodyParser.json({limit: '10mb'});
};

For uploading files, @DirkStevens can you show an example of how to do it? We worked on an example together.

I haven't had time to properly integrate multipart uploading. Under the hood Iron Router just uses body parser for parsing http bodies. And at some point they decided not to support multipart uploads (I didn't realize this until last weekend). So we have to plug in a third party multipart uploading Connect middleware package, or you can do it yourself. There are a few npm packages for this (http://www.senchalabs.org/connect/multipart.html).

DirkStevens · 2015-02-09T08:07:52Z

Hey all - at #1190 you'll find info and a link to an experimental "multipart" package that @cmather and I worked on.

travisdahl · 2015-02-09T19:11:55Z

@cmather , just as @gerwinbrunner mentioned...

Just adding the line in my own code did not fix the error, so I had to fork and change the original.
But now it works. :)

adding this to my own server side code doesn't seem to make a difference. I still get the limit error. Any ideas why defining it in our own code wouldn't work?

OK, I figured it out...My orginal code that did NOT work was...

Router.configureBodyParsers = function() {
  Router.onBeforeAction(Iron.Router.bodyParser.json({
    limit: '500mb'
  }));
  Router.onBeforeAction(Iron.Router.bodyParser.urlencoded({
    extended: true
  }));
};

I needed to just add the limit to the urlencoded like so:

Router.configureBodyParsers = function() {
  Router.onBeforeAction(Iron.Router.bodyParser.urlencoded({
    extended: true,
    limit: '500mb'
  }));
};

THIS WORKS!

kkm · 2015-02-24T19:06:09Z

@travisdahl
Can you tell me which version did you use for iron router?
I did try with 1.0.7.1 but doesnt work for me.

kkm · 2015-02-24T20:36:50Z

AH I found:
Router = new Iron.Router;
Router.configureBodyParsers = function() {
Router.onBeforeAction(Iron.Router.bodyParser.urlencoded({
extended : true,
limit : '500mb'
}));
};

I didnt know that it needs class of Iron.Router..that is fix now..thanks

jackphilippi · 2017-01-30T23:32:50Z

For people who still encounter this issue after adding the above snippet from @kkm (minus the not-needed Router = new Iron.Router; line), your problem may very well be the placement of the said snippet.

Move your Router.configureBodyParsers = function() ... snippet to be immediately before your route definitions. I had placed the snippet in a Meteor.startup() block in the server/main.js file and this did not work. Moving the snippet to lib/routes/main.js (immediately before my routes) solved this issue!

I believe this is because the Router object gets initialised after the code in server/main.js, meaning it overwrites the extended function. Hopefully this saves someone the months of trouble it caused me!

cmather closed this as completed Jul 26, 2014

cmather added the enhancement label Jul 26, 2014

michaelleuzinger mentioned this issue Jun 3, 2015

Iron-Router Error: request entity too large at makeError kahmali/meteor-restivus#78

Closed

xauxatz mentioned this issue May 2, 2017

Request entity too large perak/kitchen-site#375

Open

micahalcorn mentioned this issue May 26, 2017

request too large || body empty when increasing limit #1500

Open

KillianRousseau mentioned this issue Jul 4, 2018

Request entity too large error #1599

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error: Request Entity Too Large #710

Error: Request Entity Too Large #710

laddi commented Jul 11, 2014

cmather commented Jul 13, 2014

cmather commented Jul 13, 2014

cmather commented Jul 26, 2014

gerwinbrunner commented Sep 16, 2014

gerwinbrunner commented Sep 26, 2014

gerwinbrunner commented Oct 15, 2014

gerwinbrunner commented Oct 22, 2014

tmeasday commented Oct 23, 2014

gerwinbrunner commented Oct 23, 2014

tmeasday commented Oct 23, 2014

gerwinbrunner commented Oct 27, 2014

gerwinbrunner commented Nov 9, 2014

gerwinbrunner commented Nov 9, 2014

tmeasday commented Nov 9, 2014

gerwinbrunner commented Nov 9, 2014

tmeasday commented Nov 9, 2014

gerwinbrunner commented Nov 10, 2014

landland commented Jan 30, 2015

travisdahl commented Feb 8, 2015

cmather commented Feb 8, 2015

DirkStevens commented Feb 9, 2015

travisdahl commented Feb 9, 2015

kkm commented Feb 24, 2015

kkm commented Feb 24, 2015

jackphilippi commented Jan 30, 2017

Error: Request Entity Too Large #710

Error: Request Entity Too Large #710

Comments

laddi commented Jul 11, 2014

cmather commented Jul 13, 2014

cmather commented Jul 13, 2014

cmather commented Jul 26, 2014

gerwinbrunner commented Sep 16, 2014

gerwinbrunner commented Sep 26, 2014

gerwinbrunner commented Oct 15, 2014

gerwinbrunner commented Oct 22, 2014

tmeasday commented Oct 23, 2014

gerwinbrunner commented Oct 23, 2014

tmeasday commented Oct 23, 2014

gerwinbrunner commented Oct 27, 2014

gerwinbrunner commented Nov 9, 2014

gerwinbrunner commented Nov 9, 2014

tmeasday commented Nov 9, 2014

gerwinbrunner commented Nov 9, 2014

tmeasday commented Nov 9, 2014

gerwinbrunner commented Nov 10, 2014

landland commented Jan 30, 2015

travisdahl commented Feb 8, 2015

cmather commented Feb 8, 2015

DirkStevens commented Feb 9, 2015

travisdahl commented Feb 9, 2015

kkm commented Feb 24, 2015

kkm commented Feb 24, 2015

jackphilippi commented Jan 30, 2017