You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
I don't quite understand the ruleset above, but it looks like it is using HTTP instead of the {newly|recently|?} supported HTTPS. It is also using the wrong domain for HTTPS.
Please consider enabling HTTPS for MathJax requests, and please consider using the new CDN.
By the way, when you say "Can you edit your issue to add this", you might consider being more prescriptive. I was not sure if you wanted it in the title or the body. I also was not sure if you wanted the extra markup, like the [//]. I added field and the extra markup in the body assuming you use it to parse the field.
This is not a HTTPS Everywhere issue. I can reproduce with HTTPS Everywhere disabled in Firefox and I can't reproduce with HTTPS Everywhere enabled in Chromium.
I'm not sure I am seeing the same test results as you. I go into the "unrendered" stated and then look at the HTML source. There are no references to azureedge.net. I searched the page for just azure and there were no hits.
Is it possible it is a browser configuration difference? A regional thing? Or maybe something else?
Activity
https-everywhere-bot commentedon Feb 17, 2018
Hey, I couldn't find the type of issue in your description. Can you edit your issue to add this (perhaps referring to the issue template?)
[-]mathjax.org may need updating[/-][+]mathjax.org may ruleset need updating[/+][-]mathjax.org may ruleset need updating[/-][+]mathjax.org may need ruleset updated[/+]noloader commentedon Feb 17, 2018
@https-everywhere-bot,
Thanks, done.
By the way, when you say "Can you edit your issue to add this", you might consider being more prescriptive. I was not sure if you wanted it in the title or the body. I also was not sure if you wanted the extra markup, like the
[//]. I added field and the extra markup in the body assuming you use it to parse the field.Bisaloo commentedon Feb 17, 2018
When @https-everywhere-bot says "this" in this context, it refers to the issue type.
In this case, it would be
Type: ruleset issue.cc @strugee
Bisaloo commentedon Feb 17, 2018
This is not a HTTPS Everywhere issue. I can reproduce with HTTPS Everywhere disabled in Firefox and I can't reproduce with HTTPS Everywhere enabled in Chromium.
Firefox finds active mixed content from http://csp.azureedge.net/cdn/widget/fonts/icomoon.woff?-4tk0iu. Maybe, you should start here.
noloader commentedon Feb 17, 2018
Thanks @Bisaloo.
I'm not sure I am seeing the same test results as you. I go into the "unrendered" stated and then look at the HTML source. There are no references to
azureedge.net. I searched the page for justazureand there were no hits.Is it possible it is a browser configuration difference? A regional thing? Or maybe something else?
Bisaloo commentedon Feb 17, 2018
You are right. I don't see requests to azureedge.net anymore. Weird. I have no idea what could be causing the issue on your website.
noloader commentedon Feb 17, 2018
@Bisaloo ,
Ack, thanks. Thanks for the help in ruling out HTTPS Everywhere.
I love the tool. I've been using it for years. Keep up the great work.
Have the bot ask for more specific fixes