Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

Orchestrate Repeater Requests

Ron Kuper Apr 27, 2016 10:28AM UTC

It is often needed to orchestrate or time (as in timing) a sequence of requests in relation to one another.

Simple Examples:
1) Send Request '1'
2) Wait 1 second
3) Send Request '2'

This is hard to do manually since we get no indication of the different send stages (Req, Waiting for server, Res) so we can't determine when the request has reached the server to time request 2 afterward (necessary for race condition exploits)

-or-

1) Send Request '1'
2) Wait for Response
3) Send Request '2'


Furthermore this could evolve into a simple tokenizing system where we take a value from the previous response (using regex for instance) and use it in the next request.





Dafydd Stuttard Apr 28, 2016 07:55AM UTC Support Center agent

Thanks for this request. It’s possible you can do some tasks like this using Burp’s session handling rules and macros. If you need to completely control the timing of a request in relation to a prior request or response, you will probably need to create an extension for this purpose.


Post Your public answer

Your name
Your email address
Answer