Re: Be carefull with apache 1.3.24

2002-04-02 Thread Pedro Melo Cunha
Did not tested with that one... I was having problems with cookies only... Or so I thought :) On Mon, Apr 01, 2002 at 11:22:10PM +0200, Eric Cholet wrote: --On lundi 1 avril 2002 17:12 +0100 Pedro Melo Cunha [EMAIL PROTECTED] wrote: It seems to be fixed in CVS Haven't tried it yet...

Re: Be carefull with apache 1.3.24

2002-04-01 Thread Eric Cholet
--On vendredi 29 mars 2002 13:26 -0500 John Siracusa [EMAIL PROTECTED] wrote: Anyway, now that I have patched, working versions, what's the status on apache.org fixing this bug in the real distribution? The Set-Cookie issue has been fixed in apache CVS, but the chunked response issue hasn't

Re: Be carefull with apache 1.3.24

2002-04-01 Thread Pedro Melo Cunha
It seems to be fixed in CVS Haven't tried it yet... Best regards, On Fri, Mar 29, 2002 at 01:26:43PM -0500, John Siracusa wrote: On 3/29/02 1:11 PM, John Siracusa wrote: On 3/23/02 8:01 PM, Pedro Melo Cunha wrote: Looking at the change log, they mention a bug that multiple set-cookie's

Re: Be carefull with apache 1.3.24

2002-04-01 Thread Eric Cholet
--On lundi 1 avril 2002 17:12 +0100 Pedro Melo Cunha [EMAIL PROTECTED] wrote: It seems to be fixed in CVS Haven't tried it yet... As far as I can tell the chunked response bug hasn't been fixed yet. Best regards, On Fri, Mar 29, 2002 at 01:26:43PM -0500, John Siracusa wrote: On

[slightly OT] Re: Be carefull with apache 1.3.24

2002-04-01 Thread Larry Leszczynski
On Mon, 1 Apr 2002, Eric Cholet wrote: The Set-Cookie issue has been fixed in apache CVS, but the chunked response issue hasn't yet. Forward any ideas/patches to the [EMAIL PROTECTED] or to mod_proxy's maintainer, minfrin at sharp dot fm. I have not yet been able to get 1.3.23 successfully

Re: [slightly OT] Re: Be carefull with apache 1.3.24

2002-04-01 Thread Eric Cholet
--On lundi 1 avril 2002 16:44 -0500 Larry Leszczynski [EMAIL PROTECTED] wrote: On Mon, 1 Apr 2002, Eric Cholet wrote: The Set-Cookie issue has been fixed in apache CVS, but the chunked response issue hasn't yet. Forward any ideas/patches to the [EMAIL PROTECTED] or to mod_proxy's

Re: Be carefull with apache 1.3.24

2002-03-29 Thread Larry Leszczynski
On 3/23/02 8:01 PM, Pedro Melo Cunha wrote: The problem is that 1.3.24 final also has that bug: only the last set-cookie will reach your browser. Another problem that bit me is that 1.3.24 mod_proxy is returning HTTP/1.1 chunked encoding responses to HTTP/1.0 clients:

Re: Be carefull with apache 1.3.24

2002-03-29 Thread John Siracusa
On 3/23/02 8:01 PM, Pedro Melo Cunha wrote: Looking at the change log, they mention a bug that multiple set-cookie's will fail (only the last one will be sent to the client, the proxy will eat the others). And it was true... The problem is that 1.3.24 final also has that bug: only the last

Re: Be carefull with apache 1.3.24

2002-03-29 Thread John Siracusa
On 3/29/02 1:11 PM, John Siracusa wrote: On 3/23/02 8:01 PM, Pedro Melo Cunha wrote: Looking at the change log, they mention a bug that multiple set-cookie's will fail (only the last one will be sent to the client, the proxy will eat the others). And it was true... The problem is that 1.3.24

Re: Be carefull with apache 1.3.24

2002-03-29 Thread John Siracusa
On 3/29/02 1:26 PM, John Siracusa wrote: Anyway, now that I have patched, working versions... Scratch that: the patch doesn't seem to work when I build a server with mod_ssl in it. Hrm... -John

Re: Be carefull with apache 1.3.24

2002-03-25 Thread John Siracusa
Does anyone know how I can put my ProxyIOBufferSize config line in a conditional that'll keep it from blowing up if I'm using a version of apache earlier than 1.3.24? -John

Re: Be carefull with apache 1.3.24

2002-03-25 Thread Hans Juergen von Lengerke
John Siracusa [EMAIL PROTECTED] on Mar 25, 2002: Does anyone know how I can put my ProxyIOBufferSize config line in a conditional that'll keep it from blowing up if I'm using a version of apache earlier than 1.3.24? You could use IfDefine but that would mean that the command that starts

Re: Be carefull with apache 1.3.24

2002-03-25 Thread Robert Landrum
At 11:14 AM -0500 3/25/02, John Siracusa wrote: Does anyone know how I can put my ProxyIOBufferSize config line in a conditional that'll keep it from blowing up if I'm using a version of apache earlier than 1.3.24? -John In /path/to/apache1.3.24/bin/apachectl add a -DAPACHE_1_3_24 to the httpd

Re: Be carefull with apache 1.3.24

2002-03-25 Thread Geoffrey Young
In /path/to/apache1.3.24/bin/apachectl add a -DAPACHE_1_3_24 to the httpd command. In your httpd.conf add IfDefined APACHE_1_3_24 ProxyIOBufferSize 10 /IfDefined I think that should work you could also do something hackish like this to avoid command line switches Perl

Re: Be carefull with apache 1.3.24

2002-03-25 Thread John Siracusa
On 3/25/02 11:39 AM, Geoffrey Young wrote: In /path/to/apache1.3.24/bin/apachectl add a -DAPACHE_1_3_24 to the httpd command. In your httpd.conf add IfDefined APACHE_1_3_24 ProxyIOBufferSize 10 /IfDefined I think that should work you could also do something hackish

Re: Be carefull with apache 1.3.24

2002-03-24 Thread Ged Haywood
Hi Pedro, On Sun, 24 Mar 2002, Pedro Melo Cunha wrote: [snip,snip] Looking at the change log, they mention a bug that multiple set-cookie's will fail (only the last one will be sent to the client, the proxy will eat the others). And it was true... The problem is that 1.3.24 final also has

Be carefull with apache 1.3.24

2002-03-23 Thread Pedro Melo Cunha
Hi, a bit of history: I read on the documentation the new mod_proxy feature called ProxyIOBufferSize which allows for even better handling of lasrge mod_perl httpd's. This babby, and another little patch that also made it (closing the backend connection as soon as possible) allows for me to have

Re: Be carefull with apache 1.3.24

2002-03-23 Thread Stas Bekman
Pedro Melo Cunha wrote: Hi, a bit of history: I read on the documentation the new mod_proxy feature called ProxyIOBufferSize which allows for even better handling of lasrge mod_perl httpd's. This babby, and another little patch that also made it (closing the backend connection as soon as