I often use a system that wants to block selective statements that I send out. Not sure why, but it's a work system, go figure... I've found that going to the site in HTTPS will prevent such filtering from occurring (I use my own devices so no custom root certificates installed). I tried to go to meta via HTTPS, and was told that it isn't allowed. Why is HTTPS allowed on the main site, but not on meta?
I'm retagging this since the main issue is tracked over on MSE.
The gist of the problem here is that to properly fix this, we need to change how meta URLs work. We do have a plan, but it's not a trivial change and we're having trouble finding the time while juggling all the other stuff. HTTP-everywhere-on-the-network is not abandoned, it just keeps losing the priority battle for the time being. Hopefully soon? But unfortunately I can't make any promises on the timeline here.