Open
Conversation
There can still be sensitive information in URLs, even after we strip out username, password, and fragment. This patch adds a recommendation for admins to run their own collectors if they have URLs like this.
Member
Author
|
@annevk, how do you feel about this language? |
Member
|
I think the main problem is that this section defines capability URLs as something they are typically not. Going through the examples of https://w3ctag.github.io/capability-urls/ the capability is almost always in the path. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
There can still be sensitive information in URLs, even after we strip out username, password, and fragment. This patch adds a recommendation for admins to run their own collectors if they have URLs like this.
cf #155
Preview | Diff