Failed to find a suitable document parser.

andresriancho / w3af

w3af: web application attack and audit framework, the open source web vulnerability scanner.

http://w3af.org/

4.53k stars 1.21k forks source link

Failed to find a suitable document parser. #13277

Open lukaszbudnik opened 8 years ago

lukaszbudnik commented 8 years ago

Hi Andres,

I'm trying to crawl my website. I'm using 2 branches: master and develop (checkout today) I keep getting this error:

Failed to find a suitable document parser. Exception "There is no parser for "https://XXXXXX"."

Unfortunately the error message is not really helpful. Are there any 'hidden' dependencies? I'm running w3af on Ubuntu 12.04 server (all dependencies resolved using the generated w3af scripts).

Any hints most welcomed.

thanks, Lukasz

andresriancho commented 8 years ago

Well, if you have all the dependencies that shouldn't be the issue.

The code that generates the message is here. The reason for the message is that there is no parser that can parse the response. Root cause is:

The HTTP response doesn't have content type header, or the header is incorrect.
The lxml parser can't read the HTML: the HTML is very broken / or lxml has a bug that can't read it

You can analyze the issue yourself by debugging the code; and also I might be able to help if I have access to the target / or HTTP request response traffic.