-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Content-Length does not change when injecting tokens into request bodies #6
Content-Length does not change when injecting tokens into request bodies #6
Comments
The same is observed with this project's latest. |
This may cause the very first request(s) of Scan to lock up waiting on HTTP response where the HTTP request did not fill the claimed Content-Length size. https://forum.portswigger.net/thread/requests-showing-1-status-and-response-length-48aee98c As a work-around, I wrapped my head around this and "learned" to "turn on" the extractor's rules only after starting the scan and observing new token finds updating in the top of the Extractor tabs. |
Fixes NetSPI#6 of the original NetSPI/BurpExtractor project.
Content-Length does not change when injecting tokens into request bodies
I am using the version of BurpExtractor from PortSwigger which is currently 11 commits behind the upstream.
The text was updated successfully, but these errors were encountered: