No http #482
Closed
No http #482
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…that needs some work
You mean HTTP ? |
|
yes, of course |
Some people want to use normal http if for example the server is a localhost one. I would not interfere that. |
|
We also removed Latency Tests, and Unify. Thanks for pointing out about the w3.org though, I corrected them. |
ManeraKai
added a commit
that referenced
this pull request
Dec 10, 2022
CatCoder52
added a commit
to CatCoder52/extension_browser
that referenced
this pull request
Jun 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Minor refactor, but also includes the changes included in my previous PR. src/pages/options/widgets/services.ejs now should default to https for custom instance placeholders, as well as the resources fetched from w3.org. HTTP should be strictly avoided for clearnet.