RE: [PATCH] Apache 2.2.x: Implicit creation of new proxy_workers

2007-09-17 Thread Axel-Stéphane SMORGRAV
-Message d'origine- De : Plüm, Rüdiger, VF-Group [mailto:[EMAIL PROTECTED] Envoyé : lundi 10 septembre 2007 12:02 À : dev@httpd.apache.org Objet : Re: [PATCH] Apache 2.2.x: Implicit creation of new proxy_workers -Ursprüngliche Nachricht- Von: Nick Kew Gesendet: Montag, 10.

RE: [PATCH] Apache 2.2.x: Implicit creation of new proxy_workers

2007-09-17 Thread Axel-Stéphane SMORGRAV
-Message d'origine- De : Nick Kew [mailto:[EMAIL PROTECTED] Envoyé : lundi 17 septembre 2007 12:59 À : dev@httpd.apache.org Objet : Re: [PATCH] Apache 2.2.x: Implicit creation of new proxy_workers On Mon, 17 Sep 2007 11:33:16 +0200 Axel-Stéphane SMORGRAV [EMAIL PROTECTED] wrote

RE: [PATCH] Apache 2.2.x: Implicit creation of new proxy_workers

2007-09-12 Thread Axel-Stéphane SMORGRAV
-Message d'origine- De : Jim Jagielski [mailto:[EMAIL PROTECTED] Envoyé : lundi 10 septembre 2007 14:00 À : dev@httpd.apache.org Objet : Re: [PATCH] Apache 2.2.x: Implicit creation of new proxy_workers On Sep 10, 2007, at 6:01 AM, Plüm, Rüdiger, VF-Group wrote: Also the scoreboard is

RE: mod_proxy: Is smax=0 allowed ?

2007-09-05 Thread Axel-Stéphane SMORGRAV
Seems like you are right about the smax=0. Luckily for you, according to the documentation you may control the persistency of the backend connection with the environment variable proxy-nokeepalive just like you can control the persistency of client connections with the environment variable

[PATCH] Apache 2.2.x: Implicit creation of new proxy_workers

2007-09-04 Thread Axel-Stéphane SMORGRAV
-Message d'origine- De : Jim Jagielski [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 septembre 2007 14:56 À : dev@httpd.apache.org Objet : Re: Apache 2.2.x: Implicit creation of new proxy_workers That's right. You can't really have a connection pool if the endpoint is unknown or changing

RE: Apache 2.2.x: Implicit creation of new proxy_workers

2007-09-03 Thread Axel-Stéphane SMORGRAV
18:20 À : dev@httpd.apache.org Objet : Re: Apache 2.2.x: Implicit creation of new proxy_workers -Ursprüngliche Nachricht- Von: Axel-Stéphane SMORGRAV [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 31. August 2007 16:02 An: dev@httpd.apache.org Betreff: Apache 2.2.x: Implicit creation

RE: Apache 2.2.x: Implicit creation of new proxy_workers

2007-09-03 Thread Axel-Stéphane SMORGRAV
-Message d'origine- De : Plüm, Rüdiger, VF-Group [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 septembre 2007 10:35 À : dev@httpd.apache.org Objet : Re: Apache 2.2.x: Implicit creation of new proxy_workers -Ursprüngliche Nachricht- Von: Axel-Stéphane SMORGRAV Gesendet: Montag

Apache 2.2.x: Implicit creation of new proxy_workers

2007-08-31 Thread Axel-Stéphane SMORGRAV
Hi, In order for URLs proxied using RewriteRule with the P-flag to benefit from proxy worker connection pools, I have experimented a modification of mod_proxy that implicitly creates a new worker whenever no worker is found for a request. The patch below is against proxy_util.c of Apache

PATCH 19441: mod_cache RFC2616 violation

2007-07-31 Thread Axel-Stéphane SMORGRAV
Hi, I submitted a simple patch that fixes the above mentioned PR, and then some. 1. All of the Cache-Control request directives are ignored. As a consequence, end-to-end reload is for example not possible. Originally ap_cache_check_freshness() read the Cache-Control header from