Custom page for 400 (Bad Request)
igor at sysoev.ru
Wed Dec 15 15:09:14 MSK 2010
On Wed, Dec 15, 2010 at 01:57:58PM +0200, Eugaia wrote:
> On 15/12/2010 13:50, Igor Sysoev wrote:
> > Yes, mention of "cookie" is useful here, since this is the main cause
> > of these errors. "Header line or cookie too big". I use "line"
> > because nginx has another couse of 400 error: large header.
> > "Header line is too long" is logged when a single line of client header
> > is bigger than a buffer in large_client_header_buffers.
> > "Header is too large" is logged when sum of all header lines are bigger
> > than client_header_buffer_size plus large_client_header_buffers.
> Is this for a single header, all the headers or either?
I have looked in the sources.
"client sent too large request" is logged if all request headers can not
be read in client_header_buffer_size plus large_client_header_buffers.
"client sent too long header line: "...." is logged if a single header line
does not fit in a buffer of large_client_header_buffers.
> It might be
> useful to have 'Headers too large' if more than a single header is
> included in the calculation.
> > Probably this reason should cause 494 error too. And the resulting
> > message should be as you have suggested: "Request header or cookie too big".
> Sounds good to me.
The current edition is "Request header or cookie too large".
> It might also be useful to specify 'Cookie too large' in the log file,
> if it is the cookie that is too large.
The header line name and about 1800 value charecters are logged.
More information about the nginx