Ht access issue . I need some asap on this if anyone knows

1

A new site replacing an older one. the SSL from go daddy his taking days to sort out.
So I need to redirect https:// to http for now
Is this htaccess ok as it doesn’t seem to work. This was given was given to me this morning

RewriteEngine On
RewriteCond %{HTTPS} on
RewriteRule ^/?$ http://%{SERVER_NAME}/ [R=301,L]

This is the original one that takes the http to https

RewriteEngine On
RewriteCond %{HTTP_HOST} www.bigantgroup.co.uk
RewriteRule (.) https://bigantgroup.co.uk/$1 [R=301,L]
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^(.)$ https:/bigantgroup.co.uk/$1 [R=301,L]

Ive also added a 404 into the htaccess file and have been its wrong and it conflicts with itself but it does appear to work ok

ErrorDocument 404 /https://bigantgroup.co.uk

Access to Page Not Found

ErrorDocument 404 https://bigantgroup.co.uk

Access to Page Not Found

ErrorDocument 404 https://bigantgroup.co.uk/404/

2

Just remove the redirect completely?

The site is accessible if you remove the s from https:

http://bigantgroup.co.uk

If you’ve published the site with https:// in the settings, just remove the s and republish.

3

Hi sadly its not as easy as that .
The problem is that GoDaddy after 3 days have still not produced the SSL
so of course every link on google and the google business section is showing the older link https:// these bring bring up the google warning page when pressed.
So we are trying to make an htaccess code that will redirect from https to http , for now until the SSL is verified.
But its seems to be a little tricky

4

The real solution is to dump Godaddy. Probably the worst web host in the world. And who in their right mind pays for SSL certs these days?

4 Likes
5

Anyway, try this.

RewriteEngine On
RewriteCond %{HTTPS} on
RewriteRule (.*) http://%{HTTP_HOST}%{REQUEST_URI}
1 Like
6

Thank you for your help , we just found this
“However, if your website does not have a security certificate, it’s on a shared hosting environment, and you don’t want to get the “warning” when your website is being requested through https, you can’t redirect it using htaccess. The reason is that the warning message gets triggered before the request even goes through to the htaccess file, so you have to fix it on the server. Go to /etc/httpd/conf.d/ssl.conf and comment out the part about the virtual server 443. But the odds are that your hosting provider won’t give you that much control. So you would have to either move to a different host or buy the SSL just so the warning does not trigger before your htaccess has a chance to redirect.”

So it appears your first statement was the right one , dump Go daddy
The account is owned by the customer not us , so that’s not possible.

Cheers for your input , much appreciated. The customer has just been phoned by GoDaddy now so one would presume the ssl is close to completion. That’s 3 days now !!!