Comments on: Running a Reverse Proxy in Apache http://www.askapache.com/htaccess/reverse-proxy-apache.html Web Development Wed, 09 Jul 2008 05:47:43 +0000 http://wordpress.org/?v=2.5.1 By: Chris http://www.askapache.com/htaccess/reverse-proxy-apache.html#comment-25529 Chris Tue, 23 Oct 2007 21:12:29 +0000 http://www.askapache.com.com/htaccess/56.html#comment-25529 Could you possibly post the "simplified" example that you mentioned if vhosts were used? We use virtual hosts extensively, and I'm curious as to how this would be simplified... Thanks, this is a great read! Could you possibly post the "simplified" example that you mentioned if vhosts were used?

We use virtual hosts extensively, and I’m curious as to how this would be simplified…

Thanks, this is a great read!

]]> By: Des http://www.askapache.com/htaccess/reverse-proxy-apache.html#comment-16492 Des Mon, 17 Sep 2007 00:12:30 +0000 http://www.askapache.com.com/htaccess/56.html#comment-16492 If backend server returns 302 redirect response can this be "trapped" by proxy and redirected internally without sending response back to client? If backend server returns 302 redirect response can this be “trapped” by proxy and redirected internally without sending response back to client?

]]> By: dumbo http://www.askapache.com/htaccess/reverse-proxy-apache.html#comment-8030 dumbo Thu, 28 Jun 2007 06:00:30 +0000 http://www.askapache.com.com/htaccess/56.html#comment-8030 Hi, I have slightly different scenario then the reverse proxy examples given.i have to redirect the incoming requests (http:/)to secured site (https://) and get the data back. Also there is user authentication. how can that be acompished in reverse proxy. Hi,
I have slightly different scenario then the reverse proxy examples given.i have to redirect the incoming requests (http:/)to secured site (https://) and get the data back.
Also there is user authentication.
how can that be acompished in reverse proxy.

]]> By: Cd-MaN http://www.askapache.com/htaccess/reverse-proxy-apache.html#comment-223 Cd-MaN Thu, 11 Jan 2007 06:51:11 +0000 http://www.askapache.com.com/htaccess/56.html#comment-223 Hello. I have an issue with mod_proxy I blogged about (http://hype-free.blogspot.com/2006/09/apache-and-modproxy.html). Basically the scenario is the following: -one internal server with CentOS running an old(er) version of Apache (some 2.0.x) with mod proxy -the target server out on the web with Windows and a new Apache 2.2 -connections from the proxy to the target server are made through SSL for security reasons -if keep-alive connections are enabled at every 2-3 requests the proxy says something similar to: "I received an invalid response from an upstream server". With keep-alive connections disabled everything works fine, but the performance penalty is big, because the encryption has to be renegotiated for every query. Any ideas what could be the problem? I tried to google it by came up with no useful info. Hello. I have an issue with mod_proxy I blogged about (http://hype-free.blogspot.com/2006/09/apache-and-modproxy.html). Basically the scenario is the following:
-one internal server with CentOS running an old(er) version of Apache (some 2.0.x) with mod proxy
-the target server out on the web with Windows and a new Apache 2.2
-connections from the proxy to the target server are made through SSL for security reasons
-if keep-alive connections are enabled at every 2-3 requests the proxy says something similar to: “I received an invalid response from an upstream server”. With keep-alive connections disabled everything works fine, but the performance penalty is big, because the encryption has to be renegotiated for every query. Any ideas what could be the problem? I tried to google it by came up with no useful info.

]]> By: LonerVamp http://www.askapache.com/htaccess/reverse-proxy-apache.html#comment-161 LonerVamp Wed, 03 Jan 2007 21:14:10 +0000 http://www.askapache.com.com/htaccess/56.html#comment-161 This is just FYI. The article says: "At the time of writing, the reason most commonly cited for not upgrading is difficulties running PHP on Apache 2. I cannot speak from personal experience, but several well-informed sources tell me the difficulty lies with non-thread-safe code in PHP, and that it works well with Apache 2 if it is built with the non-threaded Prefork MPM." This was true in Ocftober 2006 when this was updated, but is no longer the issue with the latest Apache and PHP installs. This is just FYI. The article says:

“At the time of writing, the reason most commonly cited for not upgrading is difficulties running PHP on Apache 2. I cannot speak from personal experience, but several well-informed sources tell me the difficulty lies with non-thread-safe code in PHP, and that it works well with Apache 2 if it is built with the non-threaded Prefork MPM.”

This was true in Ocftober 2006 when this was updated, but is no longer the issue with the latest Apache and PHP installs.

]]>