Eric, You HAVE to use a complete path since you're also changing the request protocol (https) in that path. When you use relative links, the browser uses the current location and the current protocol to form the new request. Depending how you're server and certificate are set up, you'll also need to use a complete path to move back to your non-secure site. As for the live vs. test problem, global search and replace have always worked for me. Jim -----Original Message----- From: Eric Paynter <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Saturday, March 10, 2001 7:51 PM Subject: Switching to SSL with relative path >I can't for the life of me figure this one out. How do you change to ssl >using a relative path? Like, when it's time to move to a secure area, I >always seem to have to put in the full absolute path. This makes moving from >test to prod dangerous because I might miss one and shoot my customers over >to test by accident. > >For example, let's say we're at http://www.mydomain.com/reg_system.cgi. I >want to link to https://www.mydomain.com/manage.cgi without specifying >www.mydomain.com. > >Without the https, I just use /manage.cgi and the link works. But that >doesn't protect their pw etc. I want something like https:manage.cgi, but >that doesn't seem to work. > >It's bugging me right now because I'm just putting in the .tv code and I >just found myself on my live website signing up for a domain when I though I >was in test!!!! Anybody have any ideas? > >Thanks, > >-Eric > >------------------------------------------------------- >arctic bears - the internet - your way. >50000 domain names were reserved today. was yours? >domains from US$25/year, name resolution, mail hosting. >http://www.arcticbears.com > >
