Skip to content
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

Open
ilatypov opened this issue Oct 5, 2020 · 2 comments · May be fixed by #7 or PortSwigger/token-extractor#3
Open

Comments

@ilatypov
Copy link

ilatypov commented Oct 5, 2020

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.

@ilatypov
Copy link
Author

ilatypov commented Nov 2, 2020

The same is observed with this project's latest.

@ilatypov
Copy link
Author

ilatypov commented Dec 26, 2020

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.

ilatypov added a commit to ilatypov/BurpExtractor that referenced this issue Dec 27, 2020
@ilatypov ilatypov linked a pull request Dec 27, 2020 that will close this issue
ilatypov added a commit to ilatypov/BurpExtractor that referenced this issue Dec 27, 2020
ilatypov added a commit to ilatypov/BurpExtractor that referenced this issue Jan 5, 2021
Fixes NetSPI#6 of the original NetSPI/BurpExtractor project.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant