- From: James M Snell <jasnell@gmail.com>
- Date: Fri, 23 Aug 2013 16:01:16 -0700
- To: Robert Collins <robertc@squid-cache.org>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
Received on Friday, 23 August 2013 23:01:43 UTC
1 to 2 would cause the header values to encode as legacy encodings without any transformation. When those go from 2 to 1, legacy octets are encoded as is without transformation. So there is no risk of double encoding in the common case. Impls that choose to transform when they decide it's possible will have to understand the possible issues that come along with that. On Aug 23, 2013 3:21 PM, "Robert Collins" <robertc@squid-cache.org> wrote: > > On 24 Aug 2013 04:02, "James M Snell" > > There is no normative translation from HTTP/1 to HTTP/2. All HTTP/1 > > header field values would be passed without translation using the > > Legacy Value Encoding. > > Surely PCT encoding has to be undone or 1 to 2 to 1 will double encode. > > -rob >
Received on Friday, 23 August 2013 23:01:43 UTC