Hey everyone, On 09/13/2011 08:17 AM, Andres Riancho wrote: > List, Javier, > > I'm trying to fix a couple of common errors [0][1][2][3][4] that > appear when the initial phase of w3afCore fails, more specifically > w3afCore.py:520 . My initial analysis suggests that I change the > exception handling for w3afMustStopException, which now is "raise" to > something different (similar to the one of w3afMustStopOnUrlError). > Before doing something like that, I thought that there had to be a > reason for this error handler to be "raise". Do we know?
After taking a deeper look into the code I don't see a reason to not doing what you suggest. At that point of the scan execution it seems it makes no sense to let the exception to continue. Logging the error message would be the right fix to avoid that error. Regards, Javier > [0] https://sourceforge.net/apps/trac/w3af/ticket/167938 > [1] https://sourceforge.net/apps/trac/w3af/ticket/167981 > [2] https://sourceforge.net/apps/trac/w3af/ticket/168003 > [3] https://sourceforge.net/apps/trac/w3af/ticket/168005 > [4] https://sourceforge.net/apps/trac/w3af/ticket/168062 > > Regards, ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA Learn about the latest advances in developing for the BlackBerry® mobile platform with sessions, labs & more. See new tools and technologies. Register for BlackBerry® DevCon today! http://p.sf.net/sfu/rim-devcon-copy1 _______________________________________________ W3af-develop mailing list W3af-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/w3af-develop
