Research Academy
My account Customers About Blog Careers Legal Contact Resellers
The Burp Suite User Forum was discontinued on the 1st November 2024.

Burp Suite User Forum

For support requests, go to the Support Center. To discuss with other Burp users, head to our Discord page.

SUPPORT CENTER DISCORD

ISessionHandling - use toolflags to find out where the request comes from

NazarMedeiros | Last updated: Nov 02, 2016 01:22PM UTC

Hello, something really cool is, that the IHttpListener interface provides a method: " processHttpMessage(int toolFlag, boolean messageIsRequest, IHttpRequestResponse messageInfo) " where you can use the toolFlag variable to find out where the request comes from (Proxy,Repeater etc.) I was wondering if I could use this (toolFlags) somehow in the peformAction()-Method? Is it possible to analyze the request "source" maybe in another way? Best regards, Nazar

PortSwigger Agent | Last updated: Nov 04, 2016 02:27PM UTC

There isn't a way to identify the invoking tool when processing a session handling action, sorry.

Burp User | Last updated: Nov 07, 2016 07:54AM UTC

That is absolutely ok. I tried another way, which was to use the processHttpMessage()-method from the IHttpListener to manipulate each request. Using the toolFlag, it is an easy way to exclude the requests which come from the Proxy tool. So far so good.. The manipulation works in the same way using " messageInfo.setCurrentRequest()". The only thing whoch does not work, is to make the updated values visible in the Repeater tab. In my logs I can see that the request is updated ,but it is not visible. When I used currentRequest.setRequest() within the performAction()-method, I could see the updated values directly in the Repeater tab. Can I do something to solve this problem? Thanks in advance! Best regards, Nazar

PortSwigger Agent | Last updated: Nov 07, 2016 08:56AM UTC