Burp Suite User Forum

Login to post

Content Discovery remove items from Queued Tasks

Wouter | Last updated: Mar 28, 2018 07:05PM UTC

Would be very nice if it is possible to remove items from the "Queued Tasks" in the content discovery to for example avoid unnecessary discovery tasks. Think this one is easy to implement ;)

PortSwigger Agent | Last updated: Mar 29, 2018 09:15AM UTC

Hi Wouter, Thanks for the suggestion. I agree, this would be a useful feature and could be implemented relatively easily. It is on the development plan, although unfortunately, the development team are busy with many other things at the moment. But next time we look at Content Discovery we'll do our best to incorporate this.

Burp User | Last updated: May 23, 2018 09:54AM UTC

Yes, it will be good feature. I`m have some troubles with it because i can`t remove some bad paths from Content Discovery scanning. For example, i put bad paths in scope exclude, but Content Distovery don`t see it. It take many time senselessly.

Liam, PortSwigger Agent | Last updated: May 23, 2018 10:03AM UTC

This is still logged in our development backlog. Unfortunately, we can't provide an ETA.

Burp User | Last updated: Jun 14, 2019 11:58AM UTC

Hi. Any update on this one?

Kopeć, | Last updated: May 14, 2020 07:44PM UTC

Hi, Yeah, it would be great to have this feature :) Is there any progress on this?

Liam, PortSwigger Agent | Last updated: May 15, 2020 09:16AM UTC

This is still logged in our development backlog. Unfortunately, we can't provide an ETA. I've added a note registering your interest in this feature.

Peter | Last updated: Jul 21, 2022 08:28PM UTC

Is there any update on this? Sometimes the lack of this feature makes the Content Discovery feature nearly unusable because there's 50 irrelevant tasks queued that are going to take days to finish before getting to the stuff that actually matters. For example, this is a small subset of the tasks that are currently queued in a content discovery session I have going right now: /assets//////images/ /assets/////images// /assets////images/// /assets///images//// /assets//images///// /assets/images////// /assets////////// /assets///////// /assets//////// /assets/////// /assets////// /assets///// /assets//// /assets/// /assets// /assets/ There's a lot more where that came from and that's with setting the recursion depth to 3, so what's with all the slashes? None of that is going to yield anything good and it would take forever to get to the rest of the application. I understand it's not a priority for the development team but from my perspective it's less of a feature request and more of a bug fix so that one can actually use the content discovery feature easily. It would also be nice to have an exclusion list for recursion as well, but that's another story...

Ben, PortSwigger Agent | Last updated: Jul 25, 2022 08:04AM UTC

Hi Peter, This is still, unfortunately, recorded in our development backlog. We can certainly add your interest to this generally and also pass on the feedback that you have provided to the team. We will also update this thread if we have any further news to share about it.

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