W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2013

Re: Set-Cookie and Cookie Optimized Binary Encoding

From: James M Snell <jasnell@gmail.com>
Date: Fri, 18 Jan 2013 10:34:04 -0800
Message-ID: <CABP7RbfgF78ShBJarhaPx7hU40HwJuX1YVSfe4hu3gKK+ziVDA@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: ietf-http-wg@w3.org
I'm not convinced it is critical really. I included that basically in case
others think lossless bidirectional transformation between 1.1 and 2.0 it's
essential.
On Jan 18, 2013 10:04 AM, "Martin Thomson" <martin.thomson@gmail.com> wrote:

> On 18 January 2013 09:49, James M Snell <jasnell@gmail.com> wrote:
> > When translating an optimized Http/2 Set-Cookie to Http/1, if the Binary
> > Value Bit is set, the val is Base64 encoded and a new "Binary" flag is
> added
> > to the Http/1 Set-Cookie.
>
> This, I have no problem with, it merely indicates that the header
> originated in HTTP/2.0.  What I have a problem with is this:
>
> >  Cookie: key*={base64}
>
> Having the name change is surprising.  Why is it so critical for an
> HTTP/1.1 encoded value to be encoded in the binary form in HTTP/2.0?
>
Received on Friday, 18 January 2013 18:34:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 18 January 2013 18:34:33 GMT