301 redirect Issues

[datoshway]

Here is the issue i'm having

 

I used a 301 redirect in htaccess to redirect a site that previously was a https.  Links from google point to https. The problem is users are getting a warning message when clicking on https links from google before the 301 kicks in because the old domain is not longer ssl'ed.  What to do?

 

Thanks in advance

 

[datoshway]

Anyone?  I think all that needs to happen is we need to take users from https to http.  However we already have a 301 redirect happening.  Below is what I have

 

 

Redirect 301 / http://www.newwebsite.com/

 

I tried the following:

Options +FollowSymlinks
RewriteEngine on
RewriteCond %{SERVER_PORT} ^443$
RewriteRule ^(.*)$ http://www.oldwebsite.com/$1 [R=301,L]

 

The redirect works fine but still getting a error when visiting the https version.  Please help!

[geudrik]

Why not re-ssl the old server?  startssl.com gives out free class 1 certs...

[cags]

Do you have access to edit the VirtualHost? It's certainly not going to be possible to do anything using .htaccess, but theoretically it may be possible to redirect from the vhost. Information in the request is encrypted so you won't have access to it until a certificate is loaded, but it must know what port the connection came in on, it may therefore be theoretically possible to redirect at that point.