Many HTTP URLs that could/should be HTTPS #55

foolip · 2020-05-27T09:15:10Z

These URLs appear in the dataset and could probably all be HTTPS:

tidoust · 2020-05-27T13:28:22Z

First few ones (those that target Editor's Drafts) have been fixed upstream in W3C systems and released in v1.2.0.

The remaining ones cannot be fixed upstream today, because the same info is used to maintain the tr.rdf file where the HTTP URL appears (because these specs have been published before we switched to HTTPS everywhere). Switching a URL from HTTP to HTTPS in RDF means that you're no longer talking about the same subject, which could break tools that make use of that info.

I don't think we're tied to the same strict rules here, so perhaps we can just force the switch to HTTPS when we retrieve the info from the W3C API.

foolip · 2020-05-27T13:35:58Z

Simply normalizing all URLs and changing the protocol to HTTPS would work, right?

tidoust · 2020-05-27T14:14:52Z

Right, I don't even think that we need to parse strings as URLs in practice. Replacing http: by https: at the beginning of the string should be all it takes.

foolip · 2020-05-27T14:33:52Z

That would do the trick, yeah :)

This update contains the following changes: - HTTP URLs from the W3C API and Specref are now automatically switched to HTTPS URLs. Switches get reported as warnings to the console. See w3c#55. - CSS Forms Styling was dropped. See w3c#56. - W3C API redirect reponses generate a proper error message. See w3c#60. - A number of missing specs signaled in w3c#58 have been added.

This update contains the following changes: - HTTP URLs from the W3C API and Specref are now automatically switched to HTTPS URLs. Switches get reported as warnings to the console. See w3c#55. - CSS Forms Styling was dropped. See w3c#56. - W3C API redirect reponses generate a proper error message. See w3c#60. - A number of missing specs signaled in w3c#58 have been added. - A couple of tests were added to detect shortname collisions, and the presence of non-HTTPS URLs in index.json

* Force HTTPS URLs, drop CSS Forms, add specs This update contains the following changes: - HTTP URLs from the W3C API and Specref are now automatically switched to HTTPS URLs. Switches get reported as warnings to the console. See #55. - CSS Forms Styling was dropped. See #56. - W3C API redirect reponses generate a proper error message. See #60. - A number of missing specs signaled in #58 have been added. - A couple of tests were added to detect shortname collisions, and the presence of non-HTTPS URLs in index.json * Add index.json (needed to make tests pass) Previous commit changed the constraints on index.json so new file needs to be included in the PR.

tidoust · 2020-05-29T12:58:48Z

All HTTP URLs returned by the W3C API are now automatically converted to HTTPS, and a test ensures that there is no HTTP URL in index.json.

tidoust mentioned this issue May 27, 2020

Consider scanning for missing specs #50

Closed

tidoust mentioned this issue May 29, 2020

Force HTTPS URLs, drop CSS Forms, add specs #64

Merged

tidoust closed this as completed May 29, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Many HTTP URLs that could/should be HTTPS #55

Many HTTP URLs that could/should be HTTPS #55

foolip commented May 27, 2020 •

edited

Loading

tidoust commented May 27, 2020

foolip commented May 27, 2020

tidoust commented May 27, 2020

foolip commented May 27, 2020

tidoust commented May 29, 2020

Many HTTP URLs that could/should be HTTPS #55

Many HTTP URLs that could/should be HTTPS #55

Comments

foolip commented May 27, 2020 • edited Loading

tidoust commented May 27, 2020

foolip commented May 27, 2020

tidoust commented May 27, 2020

foolip commented May 27, 2020

tidoust commented May 29, 2020

foolip commented May 27, 2020 •

edited

Loading