Burp Suite User Forum

Login to post

Request and Response threads

Nick | Last updated: May 28, 2020 02:41PM UTC

Hi I'm the author of the request timer extension and a user has an issue when using using intruder with multiple threads in that request/responses are getting lost. I'm guessing (since I don't have a pro version any more to test) is that since the request url is the same on each thread and the extension keys on the url they are being overwritten/removed in the hashtable. So my question is can I uniquely identify a request/response using a combo of url + thread id? Do all request/responses happen on the same thread? Thanks

Hannah, PortSwigger Agent | Last updated: Jun 02, 2020 08:17AM UTC

Hi If you have a work email, you can request a free trial of Burp Suite Professional here: https://portswigger.net/requestfreetrial/pro In Burp Suite Professional, you can configure the number of threads that are being used. Given that Intruder can send hundreds of requests, you will likely encounter the same issue of overwritten hashtable values. You may need to change how you uniquely identify requests. Have you had a look at other extensions that can record intruder interactions, like Flow or Logger++ to see how they identify unique requests? You can find source code for all BApp Store extensions on our public GitHub: https://github.com/portswigger

You need to Log in to post a reply. Or register here, for free.