Following the recent Google announcements about improved ranking for sites running on https we have a number of clients asking about this. Is it safe to just 301 redirect all pages to their SSL equivalent, for example in a common PHP include file:
if($_SERVER['HTTPS']!="on"){
$redirect= "https://".$_SERVER['HTTP_HOST'].$_SERVER['REQUEST_URI'];
header("Location:$redirect",true,301);
exit();
}
Obviously I'm aware this is also possible within a .htaccess file but that cannot be modified in our case.
Obviously all internal links would be switched to https://
links but obviously we need to sort out incoming links from Google and elsewhere.
Is this a sound approach? Are there any other gotchas to be aware of?
/url-path/
without http or https ensures protocal compatibility later on. You can adopt this method on images, css and js. I also recommend using//domain.com/path/
for external http/https. These changes should be done way before SSL is enforced.www.domain.com
anddomain.com
. If you ordered a SSL certificate for onlydomain.com
users will get a browser warning forhttps://www.domain.com/
.