Improved filter option to also filter query
#433
Merged
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
|
Is that really sensitive information though? If it is, it probably shouldn't be on the query string. |
|
It's not sensitive but it's long, repetitive, and takes up storage/screen space Other usecase I can think of now can be to remove ?random=234234241324 or ?_utm (google analytics) I used the "remove" filter option on my side, but left "censor" to make it easier to grasp what's happening for new users |
arb
added a commit
that referenced
this pull request
Feb 10, 2016
Improved filter option to also filter `query`
|
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Filter option now filters
queryalsouse case:
access_tokeninqueryland