Hello!
On Tue, Feb 04, 2020 at 10:03:23AM -0800, Frank Liu wrote:
> Thanks Maxim for the quick fix!
> Based on https://tools.ietf.org/html/rfc6585#section-5 , shall we by
> default return 431 instead of 400?
That's a separate question (and I don't think changing the code
from 494/400 to 431 act
Thanks Maxim for the quick fix!
Based on https://tools.ietf.org/html/rfc6585#section-5 , shall we by
default return 431 instead of 400?
On Mon, Feb 3, 2020 at 8:47 AM Maxim Dounin wrote:
> Hello!
>
> On Sun, Feb 02, 2020 at 11:09:14PM -0800, Frank Liu wrote:
>
> > When I send a request with too
Hello!
On Sun, Feb 02, 2020 at 11:09:14PM -0800, Frank Liu wrote:
> When I send a request with too longer header value to nginx 1.16.1, I get
> 400 Bad Request response code and default nginx error page.
> If I create a custom error page:
> error_page 494 /my4xx.html;
> now I can see my error pag
Thanks for the reply!
My question is more about why there is inconsistent response code between using
default error page and default error page.
> On Feb 3, 2020, at 5:20 AM, Francis Daly wrote:
>
> On Sun, Feb 02, 2020 at 11:09:14PM -0800, Frank Liu wrote:
>
> Hi there,
>
>> When I send a r
On Sun, Feb 02, 2020 at 11:09:14PM -0800, Frank Liu wrote:
Hi there,
> When I send a request with too longer header value to nginx 1.16.1, I get
> 400 Bad Request response code and default nginx error page.
> If I create a custom error page:
> error_page 494 /my4xx.html;
> now I can see my error
Hi,
When I send a request with too longer header value to nginx 1.16.1, I get
400 Bad Request response code and default nginx error page.
If I create a custom error page:
error_page 494 /my4xx.html;
now I can see my error page but the http response code becomes 494. Is that
a bug?
Shall I see 400
