Image upload system does not catch errors caused by exceeding webserver maximum filesize/POST-size

We’ve experienced these errors one of our staging servers when the user tried to upload a 4MB image.

2014/09/10 09:46:33 [error] 27068#0: *86706 client intended to send too large body: 4405744 bytes, client: ...

The result of which is the image upload system falling back to its most default error message, “An error occurred”. This needs addressing to improve this useless message and to avoid us repeatedly troubleshooting this for other people.

Wagtail’s image features are all about high quality images so it seems likely that user would be eager to have large original image files and would therefore encounter file size limits, whatever they are, regularly.

Ideally wagtail would somehow be made aware of the server’s filesize/post limits. Failing that, the implementer would define a settings entry relating to filesize which merely duplicated the underlying server’s limits. Perhaps by setting this low enough and commenting suitably, implementers would be more likely to remember to raise the limit.

[gasman]

@prokaktus Thanks for the report! I can confirm that the error report no longer appears on recent Wagtail versions - it seems that this was inadvertently dropped in #2538. Have now opened #4163 to fix this.

[prokaktus]

I have feeling, that this logic become broken somehow. Because now when I stucked with this problem (my Nginx was configured with max size of 1mb), nothing was shown to me.

No errors were reported by Image Uploader: