Re: [PHP-DEV] Re: Output Compression Issues

2001-08-16 Thread Thies C. Arntzen
On 16 Aug 2001 21:37:11 +0300, Zeev Suraski wrote: > At 21:27 16-08-01, Thies C. Arntzen wrote: > >On 16 Aug 2001 15:26:09 +0300, Zeev Suraski wrote: > > > - Output compression should probably check that the content type is > > text/*, > > > and not perform compression otherwise > > > >that means

Re: [PHP-DEV] Re: Output Compression Issues

2001-08-16 Thread Zeev Suraski
At 21:27 16-08-01, Thies C. Arntzen wrote: >On 16 Aug 2001 15:26:09 +0300, Zeev Suraski wrote: > > - Output compression should probably check that the content type is > text/*, > > and not perform compression otherwise > >that means adding another sapi call - but i think it would make sense. Yep

Re: [PHP-DEV] Re: Output Compression Issues

2001-08-16 Thread Thies C. Arntzen
On 16 Aug 2001 15:26:09 +0300, Zeev Suraski wrote: > - Output compression should probably check that the content type is text/*, > and not perform compression otherwise that means adding another sapi call - but i think it would make sense. > - We can look into sending the content length header

Re: [PHP-DEV] Re: Output Compression Issues

2001-08-16 Thread John Donagher
On Thu, 16 Aug 2001, Zeev Suraski wrote: > So, to summarize: > > - Output compression should probably check that the content type is text/*, > and not perform compression otherwise I think I'd prefer to leave control of this in user-land, because this _is_ supported under HTTP/1.1, and write s

Re: [PHP-DEV] Re: Output Compression Issues

2001-08-16 Thread Zeev Suraski
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

Re: [PHP-DEV] Re: Output Compression Issues

2001-08-16 Thread Troels Arvin
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? Personally: No. - However, the docs for the output handling system seems to indicate that output bu

Re: [PHP-DEV] Re: Output Compression Issues

2001-08-16 Thread Zeev Suraski
At 14:55 16-08-01, Troels Arvin wrote: >On Thu, 16 Aug 2001 07:44:50 +0200, "John Donagher" <[EMAIL PROTECTED]> >wrote: > > > So, we really want to disable output compression when we are serving > > anything but HTML/text. > >I agree on that. I have heard that some older versions of both major >br

Re: [PHP-DEV] Re: Output Compression Issues

2001-08-16 Thread Joey Smith
On Thu, 16 Aug 2001, Troels Arvin wrote the following to [EMAIL PROTECTED] : > #if 0 > } else { > char lenbuf[64]; > > sprintf(lenbuf,"Content-Length: %d",Z_STRLEN_P(return_value)); > sapi_add_header(lenbuf,strlen(lenbuf), 1); > #endif > > What doe

Re: [PHP-DEV] Re: Output Compression Issues

2001-08-16 Thread Björn Schotte
Hi, * Troels Arvin wrote: > I agree on that. I have heard that some older versions of both major > browsers have trouble with compressed non-HTML content. Jep. Especially Netscape (tested with 4.61 @ Linux 2.2.14) can't display dynamic generated images which are gzipped by ob. Also, there's ano

[PHP-DEV] Re: Output Compression Issues

2001-08-16 Thread Troels Arvin
On Thu, 16 Aug 2001 07:44:50 +0200, "John Donagher" <[EMAIL PROTECTED]> wrote: > So, we really want to disable output compression when we are serving > anything but HTML/text. I agree on that. I have heard that some older versions of both major browsers have trouble with compressed non-HTML cont