Burp Suite User Forum

Login to post

Add HTTP Method as a value to the filter scope

Martin | Last updated: Nov 28, 2016 11:28PM UTC

The current scope dialog uses protocol, host/ip, port and file as a filter, however, there are times when it would be useful to filter on HTTP method too. For example when working with a RESTful interface that uses the same URI to read (GET) and delete (DELETE) resources, it would be handy to exclude DELETE from the scope.

PortSwigger Agent | Last updated: Nov 29, 2016 09:57AM UTC

Thanks for this feedback. We have this request captured in our backlog (no current ETA, sorry).

Burp User | Last updated: Jan 25, 2018 09:47PM UTC

Any ETA on this? Seeing OPTIONS requests drives me nuts.

PortSwigger Agent | Last updated: Jan 26, 2018 08:29AM UTC

Hi John, Unfortunately, there's not been any work on the feature request. However, I have created a simple extension which filters OPTIONS requests from the default view in Proxy History: - https://github.com/pajswigger/filter-options

Burp User | Last updated: Jan 29, 2018 08:14PM UTC

Thanks a lot for the awesome support!

Burp User | Last updated: Jul 12, 2019 10:57AM UTC

Thanks @Paul for your extension, these OPTIONS in the http history (and always ending up writing long regexps) are also driving me mad. Btw, I had a look at how your extension works: you tricked the engine into believing it's a response with binary content, which is filtered by default in the http history view. That's ingenious! (at least as long as we don't need to investigate binary responses ;)

Eric | Last updated: Nov 19, 2020 02:28PM UTC

I wanted to check and see if this feature was still on the product roadmap. There are numerous times where I would like to be able to filter responses by method. Right now, the most useful scenario would be to filter out OPTION requests, which I am doing via an extension right now.

Ben, PortSwigger Agent | Last updated: Nov 20, 2020 04:11PM UTC

Hi Eric, Unfortunately, no work was carried out for this particular feature due to a lack of demand for it from our users. I will discuss this with the product manager in order to determine whether we want to reopen this feature request and potentially implement it in the future.

Ben, PortSwigger Agent | Last updated: Nov 24, 2020 03:26PM UTC

Hi Eric, After having discussed this with the product manager, we are going to reopen this feature request so that we can start monitoring demand again. If we have any further news to share about the implementation of this feature then we will update this thread.

You need to Log in to post a reply. Or register here, for free.