Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat(global): link to HTTPS urls (closes #749) #782

Merged
merged 1 commit into from Jul 29, 2016

Conversation

marcoscaceres
Copy link
Member

@marcoscaceres marcoscaceres commented May 24, 2016

@plehegar r?


This change is Reviewable

@marcoscaceres
Copy link
Member Author

Fixed tests

@marcoscaceres
Copy link
Member Author

All the links appear to work fine

@marcoscaceres
Copy link
Member Author

@plehegar, @dontcallmedom is it ok to merge and release this? Or do we need to wait for some particular date?

@marcoscaceres
Copy link
Member Author

Rebased

@plehegar
Copy link
Member

plehegar commented Jun 8, 2016

Until we make the switch official, you shouldn't release this, otherwise it's going to break publications. And we can't make the switch until we get an ok on the specref side :(

@marcoscaceres
Copy link
Member Author

@plehegar, maybe we can land this in pieces? Like we could start with some of the URLs that don't relate to the publication (e.g., boilerplate ones). Can pubrules handle those?

@marcoscaceres
Copy link
Member Author

@plehegar ping

@marcoscaceres
Copy link
Member Author

Rebased... blocked on #792

@halindrome
Copy link
Contributor

halindrome commented Jul 25, 2016

@deniak pointed out that the patentURI reference is http:. this URI and some others are supplied by the spec. If any of these URIs point into w3.org I imagine we should just change them to https - right?

And maybe add checks into the "linter" that warn if URIs into w3.org are not secure.

@marcoscaceres
Copy link
Member Author

Correct. The linter should already catch these and ask the editor to change them.

We could auto-fix these on spec generation, however.

On 25 Jul 2016, at 11:07 PM, Shane McCarron notifications@github.com wrote:

@deniak pointed out that the patentURI reference is http:. this URI and some others are supplied by the spec. If any of these URIs point into w3.org I imagine we should just change them to https - right?


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@marcoscaceres
Copy link
Member Author

@deniak pointed out that the patentURI reference is http:.

to be clear, that was a mistake in my spec, not a mistake with ReSpec.

@marcoscaceres marcoscaceres merged commit 1726510 into develop Jul 29, 2016
@marcoscaceres marcoscaceres deleted the Bug_749_transition_to_tls branch July 29, 2016 04:36
marcoscaceres added a commit that referenced this pull request Aug 1, 2016
* develop:
  v4.3.0
  style(release): fix typo
  chore(package): update karma-mocha-reporter to version 2.1.0 (#895)
  chore(package): update snyk to version 1.17.5 (#894)
  Feat(global): link to HTTPS urls (closes #749) (#782)
  chore(package): update karma-mocha-reporter to version 2.0.5 (#892)
  chore(package): update snyk to version 1.17.4 (#891)
  chore(package): update karma to version 1.1.2 (#889)
  chore(package): update snyk to version 1.17.3 (#890)
  chore(package): update snyk to version 1.17.2 (#888)
  fix(headless): skip webidl-contiguous.html
  style(make-test-file-build): style code a little better
  feat(save-html): Add meta tag generator (closes #805) (#887)
  test(headless): filter out contiguous.html
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants