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

Re: Set-Cookie and Cookie Optimized Binary Encoding

From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 18 Jan 2013 10:04:36 -0800
Message-ID: <CABkgnnULTzjbCC8P2YRS_1UkCxp8BW6jdskJ+G1y=uXOFHUztQ@mail.gmail.com>
To: James M Snell <jasnell@gmail.com>
Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
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:05:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:09 UTC