As of now there are two immediate bugs 1) Fixing head_before_get to be default true and override (to false) during a '-i' reindex 2) Fixing allow_numbers bug
3) Fixing the 'Accept-Encoding' bug of the HTTP 1/1 protocol (see bug #594790). My solution, waiting to correctly handle gzipped contents (if you think it is reasonable doing it now, I could think about that) is just to send an empty 'Accept-Encoding' header, which lets the server know that our user agent is only able to manage document with the 'identity' encoding. Otherwise - the actual case - if no header is sent, the server assumes we can handle every kind of encoding.
Any comments?
Ciao ciao
-Gabriele
--
Gabriele Bartolini: Web Programmer, ht://Dig & IWA/HWG Member, ht://Check maintainer
Current Location: Melbourne, Victoria, Australia
[EMAIL PROTECTED] | http://www.prato.linux.it/~gbartolini | ICQ#129221447
> "Leave every hope, ye who enter!", Dante Alighieri, Divine Comedy, The Inferno
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ ht://Dig Developer mailing list: [EMAIL PROTECTED] List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
