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

Re: Type codecs within hpack

From: James M Snell <jasnell@gmail.com>
Date: Fri, 23 Aug 2013 15:19:42 -0700
Message-ID: <CABP7Rbfk-H3enCLc9sFWdXSpmGPs+mtWG-5iAquPm_XLYCdYzw@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
The opaque type does not have an existing standard analog in http/1, the
translation path is to simply base64 encode those.
On Aug 23, 2013 3:11 PM, "Martin Thomson" <martin.thomson@gmail.com> wrote:

> On 23 August 2013 14:58, James M Snell <jasnell@gmail.com> wrote:
> > But that makes translation to http/1 harder.  You'd have to know in
> advance
> > that any given header is a http-date or number.
>
> At the point you move to typed headers, I think that you need to
> accept this possibility.  Solving the problem for dates specifically
> still leaves the opaque type.
>
Received on Friday, 23 August 2013 22:20:09 UTC

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