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

Access to requests in Repeater tabs #10

Open
takeshixx opened this issue Nov 10, 2022 · 5 comments
Open

Access to requests in Repeater tabs #10

takeshixx opened this issue Nov 10, 2022 · 5 comments
Labels
enhancement New feature or request

Comments

@takeshixx
Copy link

takeshixx commented Nov 10, 2022

Currently, the site map and proxy history are accessible via:

It would be nice to have something similar that allows to access requests/responses in all Repeater tabs. AFAIK to only way to extract them at the moment is to manually add each requests in Repeater to the site map.

The Repeater requests are available in the Logger tool as well. However, I have not found any way to access this via the API. This might also be a great way to allow access to all requests in Burp Suite via extensions.

Additionally, something similar for Intruder would be great.

@SeanBurnsUK SeanBurnsUK added the enhancement New feature or request label Nov 17, 2022
@SeanBurnsUK
Copy link
Collaborator

Thanks for the feedback.

We do have plans to add functionality that exposes data in the burp tools. So keep an eye out for that.

@nollium
Copy link

nollium commented Mar 22, 2023

I guess one way you could do this right now would be adding a disabled ExtensionProvidedEditor and storing all the request being passed to isEnabledFor(HttpRequestResponse requestResponse) ?

@takeshixx
Copy link
Author

Thanks for the hint. I played around with that but the problem is, this will only catch requests as they are sent, right? I'm looking for a way to get these out of a project file.

@nollium
Copy link

nollium commented May 30, 2023

No, my solution should catch all HttpRequestResponse that are opened in an editor, the isEnabledFor method is used by ExtensionProvidedEditor-s to choose when to display the extension's editor, and it will be called when the editor constructs (i.e., at startup or tab creation)

You are thinking of a Proxy intercept, which operates at the Proxy level while my trick operates at the editor level.

Obviously this is super hacky and a real feature would be best.

@jamoski3112
Copy link

String invocationType = event.invocationType().toString();
   if (invocationType == "MESSAGE_EDITOR_REQUEST") {
                    api.logging().raiseInfoEvent("Invocation Type: " + invocationType);
                    event.messageEditorRequestResponse().ifPresent(requestResponse -> {
                    HttpRequestResponse httpRequestResponse = requestResponse.requestResponse();
                    HttpRequest selectedRequest = httpRequestResponse.request();
                    HttpResponse selectedResponse = httpRequestResponse.response();
                    Main.this.getDatafromRepeater(selectedRequest, selectedResponse);

Here is a cheapfix i did hope it helps
burp.api.montoya.ui.contextmenu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

4 participants