I checked that before I posted my last message. Again, in my opinoin, a parser should not be too self-serving.
As we figure out a set of websites does not provide a content type information in the http header when they ships html content.
When they ships non html/ text content they need to set the http header since all browser by default use HTML parser to interpret content.
I'm interested what kind of alternatives you see to parse html content from a *.php source that has no content type header information.
Should we just ignore all sources that have no content type header informations?
The worst case of my suggestion is that the parser can not parse the content and only then we lost the content.
Stefan
------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ Nutch-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nutch-developers
