Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a situation where we would like to redirect to I know this is very simple with http endpoints, but I'm not too sure about https.

We have some legacy windows application web service clients that will not be updating their software version soon, and we cannot update their web references to

Is there any way to leave these web service clients pointing to, but have their requests forwarded to (and responded to by)

The old server is running IIS 6.0. The new server is running IIS 7.0. We could probably upgrade it to 7.5 if needed, but I'm not certain.

We could also probably make a seamless transition of the old web service to a new server using public DNS, but we cannot change the DNS name of ""

Thanks ServerFault!

share|improve this question
up vote 2 down vote accepted

As long as the servers at both endpoints are responding with a valid certificate for their name (old server's certificate should be, new server's should be, matching the DNS name that the client's accessing for each), then a 30x redirect from the old SSL'd site to the new one is no problem at all.

share|improve this answer

I'm not sure this is the most efficient approach, but you can set up a reverse proxy in IIS 7 -- in this case requests to would be forwarded by IIS to and replied to, but to the clients it would seem like pure traffic to --

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.