Martin, thanks for pointing on this letter!
> I haven't looked at the code (is it checked in somewhere?), but an > alternative route that does not use regexps for context detection is to > base the parser on HTMLParser.HTMLParser, as was done in > http://www.mail-archive.com/w3af-develop@lists.sourceforge.net/msg00828.html Nice job! We have this talk in 2010 and only currently we are getting closer to solution! 2 years... :( > Would be interesting to see a comparison on performance between these > two approaches, also with regards to malformed html and stuff. Anyway, > good work! What I'm really afraid of is malformed html. For modern browser it is not problem but for HTMLparser it could. For example, handling such thing like <<aaaa>foo</aaaa> -- Taras http://oxdef.info GPG: C8D1F510 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ W3af-develop mailing list W3af-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/w3af-develop
