- From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
- Date: Sat, 7 Apr 2018 10:46:15 +0000
- To: Amos Jeffries <squid3@treenet.co.nz>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Hi Amos, > Not just from a purist perspective. If any one header block is too large > to process properly, or was not processed by the recipient, it screws up > the HPACK state - causing corruption of all following HEADERS and > CONTINUATION frames. So yes it MUST be the last thing on that > connection. The only optional part is whether the 4xx status code is > produced before termination. I think we are agreeing, thanks for the highlighting that point. To go back to the specific problem with this in mind. It seems that the H2 layer is improperly configured to support the HTTP semantic of this particular use case. Which leads to the connection error; the implementation choosing not to execute the optional 4xx status doen't meet the client expectation. Regards Lucas ----------------------------- http://www.bbc.co.uk This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. -----------------------------
Received on Saturday, 7 April 2018 10:46:57 UTC