Persistent backend connection when proxying using RewriteRule is exactly what I am trying to do.
AFAIU there is no way to achieve persistent connections with the default worker because (correct me if I am wrong) a worker is associated with a single proxy_conn_pool and the proxy_conn_pool is associated with a single address, and in the case of the default worker the address may be different each time the worker is used. This means that the only way to make these backend connections persistent is to create at least one worker per backend. Right? BR -ascs -----Message d'origine----- De : Plüm, Rüdiger, VF-Group [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 septembre 2007 09:23 À : [email protected] Objet : Re: Apache 2.2.x: Implicit creation of new proxy_workers > -----Ursprüngliche Nachricht----- > Von: Axel-Stéphane SMORGRAV > > Gesendet: Montag, 3. September 2007 08:15 > An: [email protected] > Betreff: RE: Apache 2.2.x: Implicit creation of new proxy_workers > > > What if the backend address is not known in the configuration because > computed dynamically using for example RewriteMap ? I do not get the point in this case. There is always a default reverse proxy worker that is used when no other worker is there. It has the limititation that you cannot adjust its parameters and that it does not support keepalives. But if you create workers dynamically this would not be very different (except for the keepalive issue). Regards Rüdiger
