Forum Moderators: phranque
<link rel="stylesheet" href="//www.example.com/styles.css">
(for example, sub-domains refer to css file in root directory with full url pass).
use relative paths for local files
Switching to SSLBTW - SSL is no longer used. It was replaced with TLS by the Internet Engineering Task Force [en.wikipedia.org]
Do I need to manually change all these urls to https on all my pages one at a time, or there is a smarter way (say, through htaccess)?
RewriteEngine on
RewriteCond %{HTTPS} off
RewriteCond %{REQUEST_URI} .(css|js|jpg|jpeg|png|gif)$
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
this might workI think the problem is that some browsers simply won't send in the request in the first place. If no request is received, no redirect can be sent.
between domainsThis is the rare case where host is what matters, not domain. The locations blog.example.com/ and assets.example.com/ may be the same domain, but they're different hosts--heck, they might even live on different servers--and as such can't be reached by relative links from one to another.
@csdude55 - file paths using HTTP will still display an error in the browser.
I think the problem is that some browsers simply won't send in the request in the first place. If no request is received, no redirect can be sent.
Can you use // with a hostname, though? I thought it was a subcategory of relative link: “match the hostname and also the protocol”.
RewriteEngine on
RewriteCond %{HTTPS} off
RewriteCond %{REQUEST_URI} .(css|js|jpg|jpeg|png|gif)$
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
[edited by: phranque at 1:29 pm (utc) on Dec 4, 2018]
[edit reason] unlinked url [/edit]
// in variables.php or header.php
<?php
$home = 'https://www.example.com';
?>
// at the top of every page, assuming it's in PHP
<?php
include '/path/to/variables.php';
echo <<<EOF
<a href='$home/page.php'>Click</a>
EOF;
?>
it is possible the browser (now or in the future) will simply not request them.
I haven't tested it, so I don't knowSo that's the problem. You are recommending code to members that you have not tested, nor do you have an understanding of how major browsers negotiate protocol for secure documents.
editing the code on all the pages is your best solution
editing the code on all the pages is your ONLY solution
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]http://subdomain.mysite.comhttps://subdomain.mysite.com
Read all info at your host concerning certificates & switching to HTTPS and when applicable, follow those instructionsYou will likely need to do everything for each subdomain, including a cert & the redirect code... but your host will be the one to ask.
https://%{HTTP_HOST}
# Replace 'www.example.com' with your domain name (as it appears on your SSL certificate)
RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://www.example.com/$1 [R=301,L]
Go through site, page by page & make sure all file paths are relative
but it also makes job easier for scrapers
