This is related to: Cannot load static content

Now that your CSS are hosted on a server asking for HTTPS, the company where I work filters it (HTTPS is authorized by whitelist only). I think a lot of companies do the same... Could you please put back the statics on a HTTP server?


To be more precise, this is the link that causes our issue:

<link rel="stylesheet" type="text/css" href="https://cdn.sstatic.net/stackoverflow/all.css?v=8a7874f4f2dd">
  • 4
    that'll bring about mixed-mode content warnings – Sathyajith Bhat Jul 3 '13 at 18:04
  • Is this question related to this: meta.stackexchange.com/questions/187204/… why does meta work fine but stackoverflow doesnt work? – JonH Jul 3 '13 at 18:07
  • 2
    @JonH Meta's assets aren't served from the CDN – Tim Stone Jul 3 '13 at 18:08
  • Okay...I just don't understand the issue at hand, this was working just a week ago. What changed that caused this to break? – JonH Jul 3 '13 at 18:08
  • @JonH The CDN assets were all switched to be served over HTTPS as part of a plan to fully support HTTPS on the network, which will naturally cause problems if a firewall blocks those requests. – Tim Stone Jul 3 '13 at 18:12
  • @JohH: Your company firewall. – Martijn Pieters Jul 3 '13 at 18:17
  • @MartijnPieters - I will check with our network administrators if that is the case. – JonH Jul 3 '13 at 18:19
  • @JonH: A site access whitelist is commonly implemented by a firewall (perhaps in tandem with a proxy server). – Martijn Pieters Jul 3 '13 at 18:21
  • The CDN is temporarily not using HTTPS anymore. – Arjan Aug 3 '13 at 21:03

The issue here is something in your pipe blocking HTTPS requests - that's very bad. We will be switching the entire network to SSL in the coming months (first offering it, then kicking users over to it automatically).

You should speak with your network admin as to why this is blocked. Unless they are looking at your browsing (which this prevents, short of local certs), there's no reason it should be blocked.

| improve this answer | |
  • 8
    I forget off-hand, was "insane corporate IT policies" on your list of SSL migration worries? :P – Tim Stone Jul 3 '13 at 18:16
  • Tank you for your reply. Blocking untrusted HTTPS websites does seem sane to me, especially in certain work environments. I've asked our sysadmins to allow HTTPS for your statics' server, which will solve the issue if my request is accepted. Nevertheless I must tell I don't understand why you need a secured connection for statics like a CSS. This is a burden for both your users, and your server, and probably for no ROI. But I might be wrong and I'd like an explanation. – Noël Bardelot Jul 4 '13 at 8:43
  • After a little research, I understand that an website serving dynamic content via HTTPS, and static content via HTTP cannot be trusted by the browser who then complains. – Noël Bardelot Jul 4 '13 at 9:20

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .