At 15:37 16-08-01, Troels Arvin wrote:
>On Thu, 16 Aug 2001 14:26:09 +0200, "Zeev Suraski" <[EMAIL PROTECTED]> wrote:
> > Can anybody think of good reasons not to send the content-length header
> > in case we're performing output buffering?
I meant "in case we're performing output compression" :I
>Personally: No.
>
>- However, the docs for the output handling system seems to indicate
>that output buffering "filters" may be nested. I could imagine that this
>will pose troubles if Content-Length headers are sent along in each
>output buffering module(?):
>http://www.php.net/manual/en/function.ob-start.php
>
>Quoting:
>
> Output buffers are stackable, that is, you may call ob_start() while
> another ob_start() is active. Just make sure that you call
> ob_end_flush() the appropriate number of times. If multiple output
> callback functions are active, output is being filtered sequentially
> through each of them in nesting order.
Yeah, I know :) However, the way it works, you're already pretty much
screwed if you do anything with the compressed buffer anyway.
Zeev
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
