Shawn, this does not make sense. In the new server design you want: ServerOld (https) ---- IP Address 1 ---- https://www.domain.com ServerNew (http) ---- IP Address 2 ---- http://www.domain.com So inorder for this to work, you will need to implement some kind of Route decision to route https://www.domain.com request to IP 1 and http://www.domain.com to IP 2. If this is possible and you have it working, then why/how will the secure traffic come to the unsecure server (ServerNew) in the first place and vice-versa !? Excuse me if I am missing something !? "Shawn Marchewka" <shawnm@xxxxxxxxxxx> 06/23/2005 08:42 AM Please respond to users@xxxxxxxxxxxxxxxx To <users@xxxxxxxxxxxxxxxx> cc Subject [users@httpd] https redirect I have a site. We'll say it's http://www.domain.com . On the same server, I have https://www.domain.com . Each site has different content. The none secure site is more of a "marketing" side of the server, while the secure site, is a site for customer login, etc. We now see the need to move the non-secure site to it's own server. So I need apache to redirect all the non-secure traffic from the old server to the new server, and all the secure traffic from the new server to the old server. I have accomplished the non-secure traffic of the old server to be redirected, but I can't get the new server secure traffic to be redirected. is this even possible? -Shawn Shawn Marchewka --------------------------------------------------------------------- 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 --------------------------------------------------------------------- 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
|