- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Tue, 25 Feb 2014 11:28:19 -0800
- To: Michael Sweet <msweet@apple.com>
- Cc: Jesse Wilson <jesse@swank.ca>, Jeff Pinner <jpinner@twitter.com>, Mark Nottingham <mnot@mnot.net>, Zhong Yu <zhong.j.yu@gmail.com>, Roberto Peon <grmocg@gmail.com>, Patrick McManus <mcmanus@ducksong.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 25 February 2014 11:07, Michael Sweet <msweet@apple.com> wrote: > I'd have to check the old mailing list logs from 1998, but I think it wasn't intentional but a mistake based on the compression keyword values (none, compress, deflate, gzip) - the same sort of mistake that's been made by HTTP implementors due to the unfortunately confusion between zlib the format and deflate the encoding name being used when zlib is meant. Do you think that this is something that we can realistically fix? People have put up with bad "deflate" in HTTP/1.1, but do you think that there is any chance that we can address that problem in HTTP/2 by saying "deflate MUST be RFC1950, reject otherwise"?
Received on Tuesday, 25 February 2014 19:28:46 UTC