W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2010

Re: #73: httpbis and deflate compression...

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 01 Apr 2010 16:45:26 +0200
Message-ID: <4BB4B186.3020902@gmx.de>
To: Mark Nottingham <mnot@mnot.net>
CC: HTTP Working Group <ietf-http-wg@w3.org>, "Mahdavi, Jamshid" <jamshid.mahdavi@bluecoat.com>
On 27.03.2010 00:10, Mark Nottingham wrote:
> Thanks, Mahdavi.
> The proposal we've had in the ticket<http://trac.tools.ietf.org/wg/httpbis/trac/ticket/73>  for eight months is to add:
> "Note that some incorrect implementations may send deflate encoding without a zlib wrapper when using this encoding."
> The proposal below seems like an elaboration of this:
> "NOTE:  Some implementations have incorrectly used only the RFC1951 encoding when returning data using the "deflate" content-coding.  Implementers should be aware the a compliant implementation of the "deflate" content-coding should follow the "ZLIB Compressed Data Format Specification" as defined in RFC1950."
> Any objections to this?
> ...

I didn't have objections; but while adding this I came to the conclusion 
that it would be better to clarify the definition itself, and then only 
add a short notice wrt broken implementations.

I ended up with -- hopefully this is acceptable for everyone:

-- snip --  Deflate Coding

    The "deflate" format is defined as the "deflate" compression
    mechanism (described in [RFC1951]) used inside the "zlib" data format

       Note: Some incorrect implementations send the "deflate" compressed
       data without the zlib wrapper.
-- snip --

See <http://trac.tools.ietf.org/wg/httpbis/trac/changeset/801>.

Best regards, Julian

PS: thanks to all the feedback!
Received on Thursday, 1 April 2010 14:46:07 UTC

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