We have some SSL websites that proxy through to non-SSL websites on the inside. Here's a sample of how they are configured. <VirtualHost outside1.mysite.com:443> ProxyRequests Off ProxyPreserveHost On ProxyPass / http://inside:8000/subdirectory1/ ProxyPassReverse / http://inside:8000/subdirectory1/ ProxyPassReverseCookiePath /subdirectory1 / RewriteEngine On RewriteCond %{REQUEST_URI} ^/subdirectory1/(.*) RewriteRule ^/subdirectory1/(.*) /$1 [P] </VirtualHost> Internal websites that redirect by path (see below) work perfect, no problems. HTTP/1.1 302 Moved Temporarily Location: /subdirectory1/someotherpage.html Internal websites that redirect by full path (see below) cause a client timeout, because we don't allow port 80 from the outside. HTTP/1.1 302 Moved Temporarily Location: http://outside1.mysite.com/subdirectory2/someotherpage.html Obviously on an inbound non-SSL request, should I allow non-SSL, I could redirect to HTTPS. Is there anything I can do to rewrite the URL provided in the 302 request on its way out? Or is there nothing that Apache can do about that? Thanks, Scott --------------------------------------------------------------------- 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@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx