RewriteCond %{HTTP_HOST} ^domain.com$
RewriteRule ^.*$ https:\/\/www.domain.com%{REQUEST_URI} [R=permanent,L]<\/p>\n\n\n\n
OR<\/strong><\/p>\n\n\n\n RewriteEngine On OR<\/strong><\/p>\n\n\n\n RewriteEngine On <\/p>\n\n\n\n <\/p>\n\n\n\n Here’s the reason: <\/strong>Network Solutions handles their shared hosting systems in a way that you don’t actually connect to a server, you connect to a proxy server so you are performing your HTTPS transaction with the proxy server, not your shared host. The proxy server translates your HTTPS connection to HTTP over port 80. When attempting to detect this with .htaccess, the server doesn’t see HTTPS because the connection between your hosting server and the proxy will always be HTTP on port 80. Because PHP pulls the HTTPS variable from Apache, it will have the identical outcome to detecting HTTP through .htaccess.<\/p>\n\n\n\n RewriteEngine on<\/p><\/blockquote>\n\n\n\n RewriteCond %{HTTP:X-Forwarded-Proto} !https Those who are using Network Solutions as a hosting provider with a UNIX hosting package must be facing issues while setting-up redirection from HTTP to HTTPS. There many few ways to setting-up redirection through htaccess such as: RewriteEngine OnRewriteCond %{HTTPS} offRewriteRule ^(.*)$ https:\/\/%{HTTP_HOST}%{REQUEST_URI} [L,R=301] OR RewriteCond %{HTTP_HOST} ^domain.com$RewriteRule ^.*$ https:\/\/www.domain.com%{REQUEST_URI} [R=permanent,L] OR RewriteEngine OnRewriteCond %{HTTP_HOST}… Read more »<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16,5],"tags":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/emarketinguide.com\/wp-json\/wp\/v2\/posts\/1138"}],"collection":[{"href":"https:\/\/emarketinguide.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/emarketinguide.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/emarketinguide.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/emarketinguide.com\/wp-json\/wp\/v2\/comments?post=1138"}],"version-history":[{"count":12,"href":"https:\/\/emarketinguide.com\/wp-json\/wp\/v2\/posts\/1138\/revisions"}],"predecessor-version":[{"id":1152,"href":"https:\/\/emarketinguide.com\/wp-json\/wp\/v2\/posts\/1138\/revisions\/1152"}],"wp:attachment":[{"href":"https:\/\/emarketinguide.com\/wp-json\/wp\/v2\/media?parent=1138"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/emarketinguide.com\/wp-json\/wp\/v2\/categories?post=1138"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/emarketinguide.com\/wp-json\/wp\/v2\/tags?post=1138"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
RewriteCond %{HTTP_HOST} ^yourdomain.com [NC]
RewriteRule ^(.*)$ https:\/\/www.yourdomain.com\/$1 [R,L]<\/p>\n\n\n\n
RewriteCond %{HTTP_HOST} ^example.com [NC]
RewriteRule ^(.*)$ https:\/\/www.example.com\/$1 [R=301,L]<\/p>\n\n\n\n
None of these will work on network solutions.com and your website will stuck in an infinite loop and show error page.<\/em><\/p>\n\n\n\n![\"SSL](\"https:\/\/emarketinguide.com\/wp-content\/uploads\/2020\/09\/http-https-redirection.jpg\")
<\/figure><\/div><\/center>\n\n\n\n
Enough about technicalities. Now, here’s the code that actually works on Network Solutions Shared Hosting<\/strong>:<\/p>\n\n\n\n
RewriteRule .* https:\/\/%{HTTP_HOST}%{REQUEST_URI} [R=301,L]<\/p><\/blockquote>
\n","protected":false},"excerpt":{"rendered":"