Skip to main content
edited tags
Link
Nick Craver Mod
  • 125.5k
  • 25
  • 432
  • 571
Post Closed as "Duplicate" by jscs, Rory Alsop, Nathan Tuggy, Ward - Trying Codidact, GlorfindelMod
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link

Every once in a while, someone comes to Meta to report a bug about something not working and it turns out that person is visiting one of the network sites over HTTPS/SSL. The problem has been growing since browsers started to outright block mixed content instead of showing a warning.

The usual answer is that HTTPS is not yet fully supported, and the person should try again using HTTP. Sometimes things get fixed, improving the situation a bit.

Is there a roadmap for full support? Partial support has been there for more than two yearsmore than two years now.

Is this actively being worked on? If not, what are the reasons to partially support it instead of disabling it completely to avoid these problems?

Every once in a while, someone comes to Meta to report a bug about something not working and it turns out that person is visiting one of the network sites over HTTPS/SSL. The problem has been growing since browsers started to outright block mixed content instead of showing a warning.

The usual answer is that HTTPS is not yet fully supported, and the person should try again using HTTP. Sometimes things get fixed, improving the situation a bit.

Is there a roadmap for full support? Partial support has been there for more than two years now.

Is this actively being worked on? If not, what are the reasons to partially support it instead of disabling it completely to avoid these problems?

Every once in a while, someone comes to Meta to report a bug about something not working and it turns out that person is visiting one of the network sites over HTTPS/SSL. The problem has been growing since browsers started to outright block mixed content instead of showing a warning.

The usual answer is that HTTPS is not yet fully supported, and the person should try again using HTTP. Sometimes things get fixed, improving the situation a bit.

Is there a roadmap for full support? Partial support has been there for more than two years now.

Is this actively being worked on? If not, what are the reasons to partially support it instead of disabling it completely to avoid these problems?

Notice removed Authoritative reference needed by CommunityBot
Bounty Ended with no winning answer by CommunityBot
Notice added Authoritative reference needed by Deer Hunter
Bounty Started worth 50 reputation by Deer Hunter
Migration of MSO links to MSE links
Source Link
Migration of MSO links to MSE links
Source Link
Loading
Source Link
Stijn
  • 8k
  • 3
  • 33
  • 69
Loading