You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2012/04/22 13:29:19 UTC

DO NOT REPLY [Bug 53121] Confusing documentation, gzip and deflate

https://issues.apache.org/bugzilla/show_bug.cgi?id=53121

Eric Covener <co...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         OS/Version|                            |All

--- Comment #1 from Eric Covener <co...@gmail.com> 2012-04-22 11:29:19 UTC ---
some background:

http://www.gzip.org/zlib/zlib_faq.html#faq38

 What's the difference between the "gzip" and "deflate" HTTP 1.1 encodings?
"gzip" is the gzip format, and "deflate" is the zlib format. They should
probably have called the second one "zlib" instead to avoid confusion with the
raw deflate compressed data format. While the HTTP 1.1 RFC 2616 correctly
points to the zlib specification in RFC 1950 for the "deflate" transfer
encoding, there have been reports of servers and browsers that incorrectly
produce or expect raw deflate data per the deflate specficiation in RFC 1951,
most notably Microsoft. So even though the "deflate" transfer encoding using
the zlib format would be the more efficient approach (and in fact exactly what
the zlib format was designed for), using the "gzip" transfer encoding is
probably more reliable due to an unfortunate choice of name on the part of the
HTTP 1.1 authors.
Bottom line: use the gzip format for HTTP 1.1 encoding.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org