Re: Content-Encoding vs. Transfer-Encoding in gzip

We should give it a try - if it works with most browsers, then we can switch... At 13:24 25/11/2001, Stanislav Malyshev wrote:

gzip encoding module now uses Content-Encoding header to sign that the page uses gzip encoding. Mozilla doesn't handle this 100% good (it saves it as zipped, which is not exactly expected behaviour) and they claim Transfer-Encoding is the right header to use for in-transfer encoding. See: http://bugzilla.mozilla.org/show_bug.cgi?id=51852 So, the question is: shouldn't PHP indeed use Transfer-Encoding instead of Content-Encoding? -- Stanislav Malyshev, Zend Products Engineer stas@zend.com http://www.zend.com/ +972-3-6139665 ext.115 -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net