[ParameterValidator] Ignore cache-busting param [#1701] #1723
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.
This PR addresses #1701
Describe the bug
Some readers implement cache-busting logic in the form of appending a &_= query parameter to sequential requests. Appropriately, this is interpreted by the BridgeAbstract as a parameter to pass to the bridge. Unfortunately, this breaks some bridges.
To Reproduce
Steps to reproduce the behavior:
&_=123
to any bridge request.Expected behavior
The bridge abstract should ignore unexpected parameters. Or strip cache-busting earlier in the execution process.
Desktop (please complete the following information):