".
Last I knew, back-end persistent connections over SSL did not work
correctly in Apache 2.2.x.
JB
On Tue, Jan 27, 2009 at 7:33 PM, Eric Covener wrote:
> On Tue, Jan 27, 2009 at 6:43 PM, Jeff Ambrosino wrote:
>> I'm using Apache as a reverse proxy to a back-end (origin
I'm using Apache as a reverse proxy to a back-end (origin) web server,
handling SSL traffic. I have SSLSessionCache enabled, which lets the
Apache server cache the client's public key to prevent the need to
renegotiate subsequent connections. But my question is whether this
also helps when Apache
We implemented a workaround to fix this problem. Basically it
involves modifying modules/proxy/proxy_util.c to remove the comma from
the list of characters in each "allowed" variable declaration (~lines
136-145). I'm not sure if this is likely to break anything else
(aside from the RFC 1738 spec
We have a mod_proxy (2.0.54) front-end proxying to a back-end MS IIS
server. One type of URL that we use is causing problems because
mod_proxy is decoding an encoded comma in the URL as it proxies the
request to the back-end (we determined this with a packet sniffer):
between browser and mod_pro
I'm using Apache 2.0.54 and mod_disk_cache, and wondering if
htcacheclean (http://httpd.apache.org/docs/2.2/programs/htcacheclean.html)
will work?
thanks
Jeff
-
The official User-To-User support forum of the Apache HTTP Server Pr
