IndieIndeed Posted January 18, 2015 Posted January 18, 2015 Using 4.0 I have force ssl for logins enabled. It works on the AdminCP page but the regular login page actually forces http:// instead of https://.Furthermore, many of the icons are attempting to load from https:// while the website remains http:// getting them blocked by Cross-Origin.I'm assuming this is not supposed to happen?
IndieIndeed Posted January 18, 2015 Author Posted January 18, 2015 Apparently editing (after a certain time) is disabled... that's annoying. Anyway - Figured out why the login page forced me out of https:// and that was because I had friendly url's enabled. Turned it off and the site doesn't force me to http:// from https:// anymore. Oddly enough I think IPB declined friendly url's being configured correctly- yet, when I looked back it was on with force friendly url's enabled. Not sure how that worked.As for the images/fonts breaking- if I'm not using https://... still happens. Even though all the buttons, links and other possible navigation point to http:// (including any login minus the admincp login...)
kysil Posted January 18, 2015 Posted January 18, 2015 Why do not you want to enable a secure connection for the entire site, not just for the login page?
IndieIndeed Posted January 19, 2015 Author Posted January 19, 2015 Why do not you want to enable a secure connection for the entire site, not just for the login page?I want it enabled for the login page (and it is enabled to do so) but it doesn't work. Any and all buttons (sign-in or otherwise) besides the admincp button goes to http://.Then the site for some reason receives theme images and fonts from https:// and gets blocked since it doesn't seem to know that I'm using http://. Which- I thought IPB auto-detected in that case.
d9nut Posted February 23, 2015 Posted February 23, 2015 I want it enabled for the login page (and it is enabled to do so) but it doesn't work. Any and all buttons (sign-in or otherwise) besides the admincp button goes to http://.Then the site for some reason receives theme images and fonts from https:// and gets blocked since it doesn't seem to know that I'm using http://. Which- I thought IPB auto-detected in that case.I'm also seeing this issue with a board upgraded from 3.4.7
Recommended Posts
Archived
This topic is now archived and is closed to further replies.