Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

Improve flexibility of Proxy Match and Replace

Jon | Last updated: Dec 17, 2015 05:57PM UTC

There are already a couple of requests to handle specific use cases of conditional Match and Replace that were declined -- and I have my own use case as well -- but I'd like to suggest a couple of generic options that could be implemented in the existing interface to avoid the need to write extensions for less complicated cases. - Add a checkbox to apply the rule to only the in-scope domains, instead of everything that passes through the proxy. - Extend the regular expression support and input controls to handle multiple lines instead of just a single line (both the Match and the Replace, but mostly the Replace), possibly as a new Type of "Entire Request" or something to that effect that lets the match occur either in the headers or body.

PortSwigger Agent | Last updated: Dec 22, 2015 01:23PM UTC

Thanks for these ideas. We've captured them in our backlog. Next time we work on the Proxy match/replace features, we'll look at all the various requests we've received about it, and do our best to deliver as many of them as possible.

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