On Wed, 15 Aug 2001, Rasmus Lerdorf wrote:
But a second call to Header(Content-Encoding:) will replace the first
one. If no content has gone out yet, overwriting a previous
Content-Encoding header is trivial. I am not sure what you mean when you
say that this doesn't do the job for some
We've run into some trouble with output compression, specifically when using
PHP to generate PDF's, and send them directly to the browser with an overridden
mime-type. It appears as though the browser support for this is rather lame;
even recent versions of Netscape hand Acrobat the compressed
ob_end_{clean,flush} will stop the output buffering and compression, but the
header 'Content-Encoding: gzip' is already sent, at that point. Since we can't
(to my knowledge, please correct me if this is the case) remove the header, the
best we can do is replace it with the second header()
