- From: Zhong Yu <zhong.j.yu@gmail.com>
- Date: Tue, 5 Aug 2014 15:29:34 -0500
- To: Martin Thomson <martin.thomson@gmail.com>
- Cc: Johnny Graettinger <jgraettinger@chromium.org>, HTTP Working Group <ietf-http-wg@w3.org>
On Tue, Aug 5, 2014 at 3:09 PM, Martin Thomson <martin.thomson@gmail.com> wrote: > On 5 August 2014 11:39, Johnny Graettinger <jgraettinger@chromium.org> wrote: >> Section 8.1.3 "Examples" provides guidance on how an intermediary should do >> so, however section 8.1.2.2 "Hop-by-Hop Header Fields" says that stripping >> Transfer-Encoding is a SHOULD, not a MUST. > > Yeah, so the only reason that it's not a MUST is that some > intermediaries don't look and we don't want to force them to look. > That's all. Transfer-Encoding has no meaning in HTTP/2 (unless an > extension restores that meaning). > > Seeing the chunked framing in DATA frames would be wrong. > That is quite confusing and dangerous. Should we require that anyone *generating* the initial HTTP2 message MUST NOT include the Transfer-Encoding header? Zhong Yu bayou.io
Received on Tuesday, 5 August 2014 20:30:05 UTC