https forwarding problem.

[MikeV1234]

I know Google is going to be making a major change soon to all websites without https and Muse needs to improve this process soon. When I saw Google, I also mean Google Chrome, the most popular browser!

I currently host with GoDaddy and after everytime I FTP a website with SSL I have to open Filezilla and update the htaccess file with the following code so it will redirect to the https version of the domain.

# Begin Muse Generated redirects

RewriteEngine On

RewriteCond %{HTTPS} off

RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

# End Muse Generated redirects

But I've had problems where this code was redirecting http to https, but NOT www.website.com to the https version. As well as SSL's from cloudflare that only forward certain domains to the https version.

Also it's annoying to have to do this.

Can there be an easier way???

[Neox99]

I host at GoDaddy so your mention of them interested me.

Requiring a manual tweak to an htaccess file for a domain that has SSL makes no sense to me.

So I called GoDaddy, read them your post, and they have NO idea why you have to do what you do.

They suggested that you call them with specific account info.

[MikeV1234]

When I first installed the SSL on a few Muse websites I noticed that all of them had the same problem.

The code in the htaccess file redirects the domains to a secure domain with https. If you upload a Muse website via FTP it will overwrite the htaccess to a blank file which allows a user to type in a website like www.website.com which will NOT be a secure site.

I called GoDaddy and they gave me the code I posted above to solve the problem and the person I spoke with seemed like this was a familiar problem, because having an SSL does not redirect what a user types in the address bar to the secure domain. These are the instructions AND the code that GoDaddy gave me.

If you're still not convinced then show me a Muse website with an SSL and if I type the www.version it will insecure.

In the next few months, after Google updates Chrome with this new standard, people with insecure websites are going to get a big warning every time a visitor tries to enter. Which is particularly bad if you consider that the owner of the website already has purchased an SSL.