-
Notifications
You must be signed in to change notification settings - Fork 40
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
Call Sequence after Request #45
Comments
Thank you for your comment, I appreciate it! :) There's not a way to achieve this at the moment, but is something I can definitely implement. Unfortunately though, the only way to view the output of the post-request sequence would be to manually navigate to the sequence once the request containing the |
Well if compared to not having that capability at all, I think it would def. be an option, when used in combination with repeater. I guess the perfect thing to happen would be for Portswigger to do the same as they did with Logger++/Flow: Recognize it is a missing feature and add it to the core of Burp based on the user experience you have created with Stepper :) Until that happens, the X-Stepper-Execute-After with the above caveats may be a good thing |
Would be nice to mention "X-Stepper-Execute-After" (and X-Stepper-Execute-Before) in the ReadMe. Anyways, thanks for your work, I really like it. |
First of: Thank you Corey for this great extension. Adding to Logger++ that's two missing features in Burp that you have provided great implementations for.
I was wondering if there is a way to call a sequence after a having made a request (similar to a post-request macro).
My use case: I would like to fuzz a specific step in a sequence. I can already execute the sequence of steps leading up to this one using the X-Stepper-Execute-Before Header, but as it is, I can only see the output of the submitted data in a final summary step of the sequence. So for detecting simple stuff like XSS I'd need to execute all steps up until step X and the all the following steps until the end.
Is there a way to do this with Stepper as it is now or would that require a new feature?
The text was updated successfully, but these errors were encountered: