Spider tab

The Spider tab shows you the set of unique URIs found by the Spider during the scans.

The ‘New Scan’ button launches the Spider dialog which allows you to specify exactly what should be scanned.
The Spider can be run on multiple Sites in parallel and the results for each scan are shown by selecting the scan via the ‘Progress’ pull-down.

The toolbar shows information about a scan and allows to control it. It provides a set of buttons which allows to:

  • pause button Pause (and resume button resume) the selected Spider scan;
  • stop button Stop the selected Spider scan;
  • clean scans button Clean completed scans;
  • Spider options button Open the Spider Options screen.

The progress bar shows how far the selected Spider scan has progressed. It is also shown the number of active Spider scans and the number of URIs found for the selected scan.

For each URI found you can see:

  • Processed - Whether the URI was processed by the Spider or was skipped from fetching because of a rule (e.g. it was out of scope)
  • Method - The HTTP method, e.g. GET or POST, through which the resource should be accessed
  • URI - the resource found
  • Flags - any information about the URI (e.g. if it’s a seed or why was it not processed)

For each Spider message, shown under the Messages tab, you can see details of the request sent and response received. The Processed column, indicates whether:

  • successful parseSuccessfully - the response was successfully received and parsed
  • no parseEmpty Message - the response was not parsed because it was empty
  • no parseI/O Error - an input/output error occurred while fetching the response
  • no parseMax Children - the response was not parsed because the corresponding parent Sites node already has more child nodes than the maximum allowed
  • no parseMax Depth - the response was not parsed because it passed the maximum depth allowed
  • no parseMax Size - the response was not parsed because its size is not under the maximum allowed
  • no parseNot Text - the response was not parsed because it’s not text, for example, an image
  • no parseSpider Stopped - the response was not fetched or parsed because the Spider was already stopped

See also

Spider for an overview of the Spider
Spider Options screen for an overview of the Spider Options