Bug: custom error_page doesn't work for HTTP 413 (content too large)
mdounin at mdounin.ru
Mon Jun 21 03:20:09 MSD 2010
On Fri, Jun 18, 2010 at 12:48:24PM -0400, estebistec wrote:
> Has the patch been worked into a release? We are still experiencing this
> bug on version 0.7.65.
This patch was introduced in 0.8.14 and merged to stable in
Are you sure you are experiencing *this* bug, i.e. you see
*nginx's* default error page?
The main problem with 413 errors is that *browsers* doesn't show
them. Instead they consider connection abnormally terminated and
show some default error (browser's one).
More information about the nginx