Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get spider status #35

Closed
0xdevalias opened this issue Mar 15, 2018 · 3 comments
Closed

Get spider status #35

0xdevalias opened this issue Mar 15, 2018 · 3 comments

Comments

@0xdevalias
Copy link

There is currently an endpoint that allows the current scan status to be retrieved, but not an equivalent for the spider.

It would be cool to be able to check when it has 'finished spidering', or how many items are left in it's queue (similar to what is shown in the burp UI)

@0xdevalias
Copy link
Author

0xdevalias commented Mar 16, 2018

Having a bit of a deeper look into this, it seems that the burp interface may not expose this information:

Submitted request to Burp support:

Hi,

I realise that it appears to probably not currently be possible, but I was wanting to get access to the current 'spider status' from an extension.

Details I would be interested in access to include basically all of the details we can access through the UI:

  • Pause/Unpause/Status of pause
  • Clear Queues
  • Requests Made
  • Bytes Transferred
  • Requests Queued
  • Forms Queued

It would also be really good if it was possible to gain access to the spider queues in some form.

This would be to make the following feasible to implement: #35

The current alternatives I see are trying to figure out how to access these areas without using the extender API callbacks, or looking into products other than burp that could suite our needs. Neither of which are obviously ideal choices.

Would love to discuss more.

Thanks

There are also some community posts from 2016 about this:

@ikkisoft
Copy link
Collaborator

Despite Burp not exposing this value in the extender APIs, I've implemented an experimental workaround. It's currently available in the PR #41 (and it will be hopefully merged to master soon).

@gangelino
Copy link
Contributor

Thanks for submitting this PR @ikkisoft!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants