redirect www.* to secure.*

[ic]

I have a verisign cert for secure.domain.com installed on a fq account. Our client wants the verisign logo to show up on the homepage (www.domain.com) as well as at the checkout. As far as I know, verisign doesn't allow their security logo to be shown on any fqdn except on the fqdn the cert is for. Since we can't order a new cert we are stuck with secure.* So I'm trying to find out if there is a way for the site to reside at secure.* and point all www.* requests to secure.* Or at least have http://www.*.com/ (the standard web address) be directed to https://secure.*.com/ I don't know whether or not a DS-IRO will solve some of this problem. Since secure.* and www.* already exist is this the appropriate vas? The browser has to know its secure.* to match it with the cert's domain. I assume that rules out symlinks, if they were ever an option. The only other possible remedy I'm aware of is mod_rewrite, and any information regarding that or anything else would be appreciated.

Unless, of course, verisign has some option for displaying their logo on a related subdomain. That is the preferred solution.

[Randall]

So I'm trying to find out if there is a way for the site to reside at secure.* and point all www.* requests to secure.* You can probably do this with an .htaccess Redirect -- or maybe you'd need a mod_rewrite -- but running the entire site from SSL will slow it down. You may also trigger a browser warning during the transition from non-secure to secure.

And based on my experience with another (non-FQ) site, search bots that can't open a secure connection might get hung up because they don't know they're being redirected.

Randall

[ic]

I forgot about that particular warning. About the slow down from ssl, if and when it gets too slow we will have more leverage with the argument 'You have so many visitors the site is bogging down, we have to fix this properly.'