Hello,
How can I redirect https to http on my website. This is because my site doesn't have an SSL certificate nor does it need one. So if someone (even by accident) tries accessing my site via https:// it will say "No site is setup here" and redirect to NFO's website which is obviously bad and taking at least some traffic away.
So im looking for a solution.
Thanks
HTTPS -> HTTP redirect
-
- A semi-regular
- Posts: 23
- https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
- Joined: Tue Sep 27, 2011 7:16 am
Re: HTTPS -> HTTP redirect
You should be able to do this using .htaccess.
Make a file called .htaccess in your public folder, and put this in it:
Found on: http://stackoverflow.com/questions/1299 ... g-htaccess
Make a file called .htaccess in your public folder, and put this in it:
Code: Select all
RewriteEngine On
RewriteCond %{HTTPS} on
RewriteRule (.*) http://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
Not a NFO employee
Re: HTTPS -> HTTP redirect
What soja described won't work for a general account with us (that does not have SSL enabled). In the case of someone using https:// in that circumstance, the system can't tell that your account is the one they are attempting to view, so there isn't a setting on your side that would work to redirect the client.
This is something that I will have to investigate further.
This is something that I will have to investigate further.
Re: HTTPS -> HTTP redirect
Please do. It really kind of sucks it can't be done right now.Edge100x wrote:What soja described won't work for a general account with us (that does not have SSL enabled). In the case of someone using https:// in that circumstance, the system can't tell that your account is the one they are attempting to view, so there isn't a setting on your side that would work to redirect the client.
This is something that I will have to investigate further.
Thanks
Re: HTTPS -> HTTP redirect
A redirect will likely never be possible here, due to the way that SSL works. The best that we could do is to disable HTTPS on the default server IP, which would make it so that clients who mistakenly type https:// would see a timeout.
Re: HTTPS -> HTTP redirect
I'll throw in my 2 cents. In order for this to work, you'd need a SSL certificate installed to the server and configured, or a self signed one which would produce errors that ward off anyone that doesn't know exactly what the error/warning means. Therefore, in order to add a redirect that would even be worth it, it'd require paying/giving the certificate to NFO, which is possible, just not feasible if you've never used SSL on the site before which would've added links/actual reason for users to believe the SSL version of the site is the correct one.
Here's the warning that Chrome would show for a self signed certificate.
In order to proceed, the user would have to click the 'advanced' button and choose to proceed.
Here's the warning that Chrome would show for a self signed certificate.
In order to proceed, the user would have to click the 'advanced' button and choose to proceed.
Re: HTTPS -> HTTP redirect
rymax99, the complication is that SSL is IP-specific. For the redirect to work, a customer would need to have a site running on its own IP address. Due to the IP and administration overhead, we only currently support SSL for "Pro" plans.