Burp Suite User Forum

Create new post

API to update Requests as presented in UI in Proxy, Repeater, etc.

onmouseover | Last updated: Apr 21, 2015 09:06PM UTC

Hi, I have written some custom extensions using both the java API and jython. Typically, it is for things like setting custom headers. While they work (they do send the custom headers) it's hard to see exactly what was sent since the UI doesn't update after the message is set. The work around I'm using to get passed this is to chain 2 instances of burp together, with the custom extension running in the first instance. The second, obviously, shows the full edited message in proxy history, etc. It would be great if there was an API call to push the updated message into the history in the UI.

PortSwigger Agent | Last updated: Apr 22, 2015 08:29AM UTC

By design, extension-driven changes to requests via IHttpListener are applied just before the request hits the wire, and are not passed back to the invoking tool that made the request. The reason for this is that Burp tools generally need to have the request that they generated, prior to any changes made by extensions. For example, the Scanner needs to apply highlights to payloads in requests. If the Scanner's copy of its request was modified in arbitrary ways, then the highlights would be misapplied. In the case of the Proxy, the IProxyListener API does hook into messages as they are being processed within the Proxy interception engine, and the Proxy keeps separate copies of the original and modified messages. So if you are only interfering with Proxy traffic, you could use IProxyListener so as to see your changes in the UI.

You must be an existing, logged-in customer to reply to a thread. Please email us for additional support.