ID: 10070
Updated by: avsm
Old-Status: Closed
Status: Feedback
Bug Type: Zlib Related
Assigned To: 

Just to clarify a bit more, and see if a workaround is

Currently, if both gzip and deflate are present in the
Accept-Encoding, we will prefer the gzip.

The only good reason for a workaround in the code is if
a widespread browser presents deflate only, and then
proceeds to break.  Do these broken versions of IE present
Accept-Encoding: deflate _only_ ?  And which versions are


Previous Comments:

[2001-03-30 14:59:49] [EMAIL PROTECTED]
If a browser breaks RFCs -> not our problem. 



[2001-03-30 13:07:42] [EMAIL PROTECTED]
Applied a patch to add Vary: headers if we add a Content-Encoding: header.

Regarding the browser compatibility with Deflate, I think we should just leave it like 
it is.  _They_ break the RFC; encourage people to upgrade to modern, non-broken 
browsers instead ?


[2001-03-29 21:21:53] [EMAIL PROTECTED]
ob_gzhandler doesn't appear to set a Vary: header on
responses, which means that proxy caches could store a
compressed version of the resource and serve it to clients
which can't handle the encoding. This is very difficult to
debug for Web sites, and should be fixed ASAP.

For an example of the proper headers to send, see the PHP at:

Also, in my experience, some versions of MSIE don't handle
deflate compession correctly, even though their
Accept-Encoding claims they do. It might be better to avoid
deflate altogether, as gzip support is pretty much the
unwritten standard.



ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at

PHP Development Mailing List <>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to