Adding PathSuffix-Bypass-4ProxyOrWAF #142
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
Adding PathSuffix-Bypass-4ProxyOrWAF
Michelle-PortSwigger
approved these changes
Nov 10, 2023
PortSwiggerWiener
approved these changes
Nov 10, 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.
Adding PathSuffix-Bypass-4ProxyOrWAF.
Accessing paths blocked by proxies or WAFs by adding special suffixes.
Things like
%A0for Nginx (https://book.hacktricks.xyz/pentesting-web/proxy-waf-protections-bypass) will not work with HTTP/2 -> I was not sure if this can be enforced by BChecks but it would be great to have this option.