Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
recifbox Posted August 8, 2016 Posted August 8, 2016 Before switching from http to https we doing some test so, i want my Website to be accessible as well with http as https. Currently the Website is working fine with http://recifalnews.fr, but with https://recifalnews.fr the webpages are not fully with https. The ‘https’ page contains some menus and images url, for example, with the ‘http’ protocol. The page content is supposed to use the same protocol as the calling page : http when calling with http and https when calling with https. Another possibility is to have all the pages starting with / (without prococol or domain). How to do have http & https working properly?
opentype Posted August 8, 2016 Posted August 8, 2016 You don’t. You need to pick one protocol in your config settings (or http for default content and https for Login/ACP…). Delivering the whole content over two protocols at the same time is a terrible idea anyway.
Jim M Posted August 8, 2016 Posted August 8, 2016 You would set your conf_global.php URL to HTTPS and then on your server redirect HTTP traffic to HTTPS.
recifbox Posted August 24, 2016 Author Posted August 24, 2016 another question about "topic" on forum, when people post them there is link and this links from internal (http://) will stay on topics so it will give a mixed security on browser. his option will help for external link but for internal already present into forum post ?
opentype Posted August 25, 2016 Posted August 25, 2016 Links in posts aren't changed but that doesn't matter as long as the link itself will be resolved properly once clicked.
recifbox Posted August 25, 2016 Author Posted August 25, 2016 well, when we take time to take a look at this "guide line" we are far away to be really https "compliant " https://webmasters.googleblog.com/2015/12/indexing-https-pages-by-default.html
opentype Posted August 25, 2016 Posted August 25, 2016 This article is about when Google chooses to automatically index https pages over http pages when BOTH are delivered. It explains their behavior, it’s not a “guideline” about being “compliant” in any way.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.