Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Message-Id: <5.1.0.14.2.20050418112542.024daa90@molly.iii.com>
Date: Mon, 18 Apr 2005 11:36:13 -0700
To: users@httpd.apache.org
From: Richard Paladino <paladino@iii.com>
In-Reply-To: <200504181933.19942.chitta@iitkgp.ac.in>
References: <4263BB9C.7020501@videotron.ca>
 <4263BB9C.7020501@videotron.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [users@httpd] Reverse Proxy and Rewrite.

Hi Users,

I would like to 2nd the request that Chitta notes below.  Here is my 
specific situation:

I need to be able to accommodate a back-end server with reverse proxy 
rewrite rules.  My back-end servers run on multiple ports and the URLs are 
widely variable.

I have created rewrite rules to cover most of the "normal" activity:

RewriteCond %{HTTP_HOST} 
^([0-9]{1,5}-[.a-zA-Z0-9-]*\.)?frontend\.server\.com(:[0-9]+)?$
RewriteRule ^/(.*) http://%1backend.server.com%2/$1 [P,L]


My problem is that the backend server redirects to SSL ports at various 
times.  I have a list of URLs that I need to catch to do this, but I can't 
find any way to transfer the connection internally in Apache to another 
virtual host (an SSL port) when the backend server sends one of its redirects.

Here is an example URL:

http://backend.server.com/verification
...redirects the user to:
https://backend.server.com/verification/~S8

I have successfully created an SSL virtual host that itself contains all 
the rewrite rules noted above, it's this explicit redirect that I have no 
idea how to handle.  What happens at redirect is that I "pop out of" the 
reverse proxy connection and end up at the backend server.

If a creative User can help with this, you will have earned my un-dying 
respect and gratitude...

Thanks in advance,
Richard


At 07:03 AM 4/18/2005, Chittaranjan Mandal wrote:
>Reverse proxy is so useful.
>
>It would be nice to have a complete example covering
>+ main web server reverse proxying HTTP requests to internal web servers
>+ main web server reverse proxying HTTPS requests to internal web servers
>+ Dealing with the situation when the internal web server rewrites a
>    HTTP request to a HTTPS request
>+ Dealing with the situation when the internal web server rewrites a
>    HTTPS request to a HTTP request
>
>-Chitta
>
>---------------------------------------------------------------------
>The official User-To-User support forum of the Apache HTTP Server Project.
>See <URL:http://httpd.apache.org/userslist.html> for more info.
>To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>    "   from the digest: users-digest-unsubscribe@httpd.apache.org
>For additional commands, e-mail: users-help@httpd.apache.org


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org