search

w3c / validate-repos

Test whether W3C spec repos match a set of best practices
https://w3c.github.io/validate-repos/report.html
Other
15 stars 10 forks source link

Check specs are served over https #70

Closed dontcallmedom closed 4 years ago

dontcallmedom commented 4 years ago

https is not enforced as the scheme for github pages created before June 2016 and has to be manually set in the repo settings. We should ensure all relevant repos have that setting enabled.

foolip commented 4 years ago

I can't see this in https://developer.github.com/v3/repos/pages/ or the GraphQL API. Since it's just few hundred repos, maybe it'd be easiest to just open the right URLs in tabs and go through them all, checking the box where not checked?

dontcallmedom commented 4 years ago

looking a bit more into it, we have 431 repos that were created before the cut-off date according to report.json - that's beyond my motivation :)

I've wrote a little script that instead looks at the repos created before the date and with an homepageUrl set (reducing it to ~230 repos) and testing if the said URL responds with a 301 (which repos set to force-https do). The result is that at least the following repos needs fixing:

(there are probably more since some repos use a non github.io URL for their homepageUrl, and many repos don't set homepageUrl even if they use github pages)

dontcallmedom commented 4 years ago

A more exhaustive look at all repos created before June 2016 and testing if they have a matching github.io URL yields the following list that needs fixing:

dontcallmedom commented 4 years ago

Only one that I couldn't handle myself - raised an issue for it https://github.com/w3ctag/tagdocs/issues/1 ; closing this one.