It's very likely that something about a firewall you're behind is reacting to the fact that you requested a page via HTTP, but some elements are being pulled in via HTTPS. This may or may not mean:
The firewall doesn't like mixed content (even though the requested page was HTTP, and just a few elements are fetched via HTTPS, not the reverse which throws a browser warning)
The firewall permits HTTPS only for certain sites that the admins of the firewall trust
A mix of the two.
This has been an issue for more than a trivial number of folks since we started rolling out SSL accross the network, an undertaking that is anything but small.
The good news is they're making a ton of progress on it, and hopefully it will be wrapped up in the very near future. Unfortunately, if this is indeed the case, the only thing you can do is talk to the people that control the firewall, and see if an exception can be made.
I'm pretty sure what you're experiencing is related to this, and not a state controlled firewall, although I don't have a way to practically rule it out.
- What business is looking for retired teachers
- How does Windows Task Manager work
- What is calibration software
- Do your kids go to daycare
- Why did Saturday morning cartoons disappear
- What are security cameras at a chateau
- Should I invest in gold
- Why do US sanctions matter
- How can I study for AP chemistry?no_redirect=1
- Is obsession addiction
- Is bleeding to death relatively peaceful
- What is the melting point of obsidian
- How is ragging at BIT Sindri
- What should I do before an interview
- How can I make money while disabled