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.
Heads up: nih.gov, etc. moving to https by default #7125
It's great the (U.S.) government is making this initiative, but it's super unlikely that every single .gov site will be HTTPS by the end of 2016. Even if they are, they'll still have various mixed content issues etc. Take a look at #5265 (comment) and understand that some of those subdomains are probably managed by some small group of scientists with not enough funding. It'll take a while.
Also it's my understanding, though I don't have a reference, that the president doesn't have authority over Federal .gov sites managed by Congress and the Supreme Court due to separation of powers, so the White House memo requiring HTTPS has no force over them. Issue #2596 discusses senate.gov and describes how https://www.senate.gov weirdly returns a simple page advising the user to use the HTTP version of the site. There are also state .gov sites like https://www.nysenate.gov and I doubt the president's memo affects those either.
Anyway I don't think there's a specific takeaway or to-do here, other than that we will probably be able to add more .gov rulesets going forward.
Activity
numismatika commentedon Sep 25, 2016
It could have, if they enable HSTS and get pre-seeded in firefox&Chrome all related rules could be removed.
jeremyn commentedon Sep 28, 2016
Some thoughts:
The first link says only that:
So this is just referring to a subgroup of NIH, not all of NIH. For reference: there are two rulesets for NIH:
National-Institutes-of-Health.xmlandNIH.gov-falsemixed.xml.Issue #5047 is also about .gov.
It's great the (U.S.) government is making this initiative, but it's super unlikely that every single .gov site will be HTTPS by the end of 2016. Even if they are, they'll still have various mixed content issues etc. Take a look at #5265 (comment) and understand that some of those subdomains are probably managed by some small group of scientists with not enough funding. It'll take a while.
Also it's my understanding, though I don't have a reference, that the president doesn't have authority over Federal .gov sites managed by Congress and the Supreme Court due to separation of powers, so the White House memo requiring HTTPS has no force over them. Issue #2596 discusses
senate.govand describes how https://www.senate.gov weirdly returns a simple page advising the user to use the HTTP version of the site. There are also state .gov sites like https://www.nysenate.gov and I doubt the president's memo affects those either.Anyway I don't think there's a specific takeaway or to-do here, other than that we will probably be able to add more .gov rulesets going forward.
jeremyn commentedon Oct 5, 2016
It looks like the discussion is done so I'm closing this issue. Thanks for starting the discussion, @terrorist96 .