Burp Suite User Forum

Create new post

Spider request queue not stopping.

Hello | Last updated: Jan 21, 2016 08:26PM UTC

Hi, I have stopped the spider from running and cleared the queues. This was roughly 30 minutes ago. However, more and more requests are still getting queued. Why is this happening and how do I stop it?

PortSwigger Agent | Last updated: Jan 22, 2016 09:05AM UTC

Items are added to the Spider queue automatically based on your configured target scope. This has no effect unless the Spider is running.

Burp User | Last updated: Jan 22, 2016 02:49PM UTC

That is why I find it odd. I have paused the spider, but hundreds and hundreds of requests are still getting piled onto the queue nonstop even after I have paused the spider and waiting for 30 minutes. Is it typical for requests to still enter the queue even after the spider has been paused?

PortSwigger Agent | Last updated: Jan 22, 2016 02:56PM UTC

Yes, this is expected behavior. The queue represents the work that will be done if the Spider is unpaused.

Burp User | Last updated: Jan 31, 2016 09:30AM UTC

After pausing the spider, how long does one need to wait for the queue to stop increasing?

PortSwigger Agent | Last updated: Feb 01, 2016 08:46AM UTC

The queue will keep increasing if Burp identifies any new in-scope links in responses. This might continue indefinitely if you are browsing via the Proxy.

Liam, PortSwigger Agent | Last updated: Feb 19, 2016 09:15AM UTC

If you are still browsing via the proxy then this is expected behaviour. Are you spidering an unusally large application?

Burp User | Last updated: May 11, 2017 06:56AM UTC

Hello, I got the same problem here. It took more than 16 hours just for spidering. And it still keep increasing the number of request queue. Is this an issue?

Burp User | Last updated: Aug 05, 2018 05:23PM UTC

Hi, There should be a way to stop the spidering. Especially, when we are talking about using the BURP extender APIs, IMHO, it becomes important to be able to stop the spidering. Also, especially when the current APIs do not support giving results of the spider status specific to a URL being spidered (unless I am unaware of it, in which case please educate me). Regards

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