Once it has been confirmed that there are no issues with HTTPS then we will begin redirecting users.
1 Like
HTTPS redirect has been enabled for javadoc, wiki, and hub.
hub still has an outstanding issue where user embeddable images can cause mixed content warning. Unfortunately the Discourse people have not provided any reliable solution or workaround except having the server download all images onto the server.
If all goes well, HTTPS will be enabled for the org page and updates.
When I view the HTTPs version in Chromium the icons are messed up similarly to how they are messed up in the former HTTP version in Firefox. CTRL+F5 does nothing and icons work fine in Firefox. I am running Ubuntu 14.04 LTS x64.
It has no effect.
It looks like some Font Awesome requests are getting cancelled for some reason:
Firefox is not blocking these requests.
Can you click one of those cancelled requests to see what the request headers is?
No idea, really…
There should be some info as to why its not going through, maybe in the console?
When it first switched to https automatically for me the icons also weren’t coming in… eventually they did as I see them now on this page… though my unreloaded main page doesn’t have them.