Closed GoogleCodeExporter closed 9 years ago
I thought I set it up to clear each time it was run, so yes thats a bug.
I'm actually in 2 minds about the spider - whether to keep fixing it or to
replace it.
I dont think its as effective as it should be, and I'd rather use a 3rd party
spider like Heritrix.
Views anyone?
Psiinon
Original comment by psii...@gmail.com
on 7 Feb 2011 at 12:29
Well seeing as I don't really know the state of the codebase, it seems to me
like there's only a few things that really need to be improved, so it might be
easier to just fix those as opposed to moving to a whole new spidering system.
I'm checking out heritrix though, so I'll let you know what I think about it!
Original comment by fitblip@gmail.com
on 7 Feb 2011 at 8:22
Alright, nevermind. This spider is totally awesome. It looks very very VERY
flexible, and it would be simple enough to come up with your own XML output
that it can then read and go from there.
Or someone can define a custom crawl using the web front-end and use that
within ZAP or something of that sort.
Nice find!
Original comment by fitblip@gmail.com
on 7 Feb 2011 at 8:26
Identified the place in the code which needs to clear the results when a new
session is opened.
But I've made some other changes to the file as well so I cant check it in
until those are tidied up ;)
Psiinon
Original comment by psii...@gmail.com
on 10 May 2011 at 1:51
This bug was fixed in the r564 changes :)
Original comment by psii...@gmail.com
on 15 May 2011 at 1:34
Fixed in release 1.3.0
Original comment by psii...@gmail.com
on 7 Jun 2011 at 5:19
Original issue reported on code.google.com by
fitblip@gmail.com
on 5 Feb 2011 at 11:11