Some clients made the changes OK and worked happily, most did not. In an effort to give them more time for the respective IT department (quite a few are 3rd party support so no internal IT know-how) we have gone down this route.
Always a fun situation to be in. :-/
I now have my linux box listening on several internal IP addresses and passing the HTTP requests to a windows IIS server in the new data centre on a number of external IP addresses each with a holding page to mimic the respective web sites. I am in truth a bit chuffed that I sorted that bit.
Good stuff!
I am now trying to get the certificate bit sorted so I can do HTTPS. Any tips on this would be great. I have worked out I will have to convert the windows cert to a linux one (using pkcs12 ?) and I am just playing with that.
One thing to keep in mind is that pound does HTTPS offloading, which may be different than what you've got now. That means pound speaks https to the browser, but only HTTP to the backend webserver (unless you go through some gymnastics). Converting the cert should just be a matter of using the appropriate openssl commands, but I'm not familiar with the details of pkcs12 certs. Google surely can help there.
One note on pound's certs. They need to be in PEM format, so: == rsa private key, ideally w/o a passphrase == == site certificate == == intermediate certs, if any == Regards, -- Dave Steinberg http://www.geekisp.com/ http://www.steinbergcomputing.com/ -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
