Welcome! Log In Create A New Profile

Advanced

Re: client sent header field with too long length value while processing HTTP/2 connection

January 25, 2020 11:08AM
Sergey Kandaurov Wrote:
-------------------------------------------------------
> > On 24 Jan 2020, at 21:02, andreios <nginx-forum@forum.nginx.org>
> wrote:
> >
> > "client sent header field with too long length value while
> processing HTTP/2
> > connection"
>
> This means that a header field name or value was detected as if it
> was represented as a string literal with length encoded as an integer
> using of more than 4 bytes (allows to represent values above 2097278).
> Although the integer representation used by HPACK allows for values
> of indefinite size, this is not supported by nginx.
>
> See RFC 7541, section 5.2 for some details.
>
> You could try to see what's actually gets sent, for debugging purpose
> (you might want to decrypt it first).
>
> --
> Sergey Kandaurov
>
Is there any workaround possible?
Is there any howto on how to decrypt an see what actually gets send?
Subject Author Posted

client sent header field with too long length value while processing HTTP/2 connection

andreios January 24, 2020 01:02PM

Re: client sent header field with too long length value while processing HTTP/2 connection

Sergey Kandaurov January 24, 2020 04:40PM

Re: client sent header field with too long length value while processing HTTP/2 connection

andreios January 25, 2020 11:08AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 92
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready