W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2014

Re: #540: "jumbo" frames

From: Michael Sweet <msweet@apple.com>
Date: Fri, 27 Jun 2014 14:53:12 -0400
Cc: Martin Thomson <martin.thomson@gmail.com>, Greg Wilkins <gregw@intalio.com>, Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
Message-id: <1CEFD2A9-704F-4D27-AC34-CAFB697694AF@apple.com>
To: Jason Greene <jason.greene@redhat.com>
Jason,

On Jun 27, 2014, at 2:31 PM, Jason Greene <jason.greene@redhat.com> wrote:
> On Jun 27, 2014, at 1:08 PM, Martin Thomson <martin.thomson@gmail.com> wrote:
> 
>> On 27 June 2014 11:05, Michael Sweet <msweet@apple.com> wrote:
>>>> b) you receive a CONTINUATION frame?
>>> 
>>> 413
>> 
>> And the header compression state changes it might contain?  Or are you
>> setting the header table to size 0
> 
> Even if you set table size to 0 you still have to process them before you can return a 413, since the setting is delayed. and you might get them before it takes effect. Only way to not process them is GOAWAY + close.

How does a client know not to reconnect and try the same request again after getting a GOAWAY?

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


Received on Friday, 27 June 2014 18:53:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:31 UTC