Keystone-classic: Unhandled error 'Request Entity Too Large'

[mjmaix]

422 adds the ability to set a file size limit but the exception thrown is not handled properly.

Upload is stopped but the page rendered shows like this:

Server error: Error: Request Entity Too Large at Object.exports.error
It would be better if this is handled by req.flash error

[JedWatson]

I agree, would welcome a PR fixing this. It should probably be implemented as a validation step on the field, and returned like the other validation errors.

[creynders]

Closing due to inactivity, feel free to comment again if this issue persists for you!

[christroutner]

One of my clients just ran into this error when they tried to create a blog post using Keystone. I'm just starting down the path of researching it and figuring out a work around. I'd welcome any tips.

[christroutner]

I appear to have fixed the issue I was having. I tried two solutions, and I'm not sure which one was the one that did it.

First, I use nginx to route https stuff on the server. I found this Stack Overflow thread that inspired me to add the following line to server block:

client_max_body_size 50M; #all file uploads up to 50 MB

I restarted nginx, but I was still getting the error. However, I didn't reboot the server or restart keystone.js.

The second thing I tried was to add this line to keystone.init() in keystone.js:

'file limit': '50MB'

I had no idea if this was the right syntax or not. But when I restarted keystone.js, it ran and didn't complain. I rebooted the server and when it came up I stopped getting the entity.to.large error.

Hopefully this helps someone in the future if they come across this issue.

[kengres]

@christroutner this just saved my ass. almost 2 years later. thanks mate

[Vincent-Loi]

@christroutner this also just saved my life. almost 2 years later. thanks mate