Bug: custom error_page doesn't work for HTTP 413 (content too large)

[estebistec]

Yeah, I'm fairly certain it's nginx's page. It's a plain page with just
"413 Request Entity Too Large" (an h1) and below that and an hr,
"nginx". I would assume the browser's own page would not say "nginx".
I'm using Chrome, btw.

Maxim Dounin Wrote:
-------------------------------------------------------
> Hello!
> 
> 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 
> 0.7.63.
> 
> 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).
> 
> Maxim Dounin
> 
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://nginx.org/mailman/listinfo/nginx

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,2620,100805#msg-100805