Why does htdig 3.1.3 mangle URL parameters that contain bare “&” characters?
This is a known bug in 3.1.3, and is fixed with this patch. You can apply the patch by entering into the main source directory for htdig-3.1.3, and using the command “patch -p0 < /path/to/HTML.cc.0". This is also fixed as of version 3.1.4.5.16. When I run htmerge, it stops with an "Unable to open word list file '.../db.wordlist'" message.The most common cause of this error is that htdig did not manage to index any documents, and so it did not create a word list. You should repeat the htdig or rundig command with the -vvv option to see where and why it is failing. See question 4.1.5.17. When using Netscape, htsearch always returns the "No match" page.Check your search form. Chances are there is a hidden input field with no value defined. For example, one user had in his search form, instead of The problem is that Netscape sets the missing value to a default of ” ” (two spaces), rather than an empty string.
This is a known bug in 3.1.3, and is fixed with this patch. You can apply the patch by entering into the main source directory for htdig-3.1.3, and using the command “patch -p0 < /path/to/HTML.cc.0". This is also fixed as of version 3.1.4. 5.16. When I run htmerge, it stops with an "Unable to open word list file '.../db.wordlist'" message. The most common cause of this error is that htdig did not manage to index any documents, and so it did not create a word list. You should repeat the htdig or rundig command with the -vvv option to see where and why it is failing. See question 4.1. 5.17. When using Netscape, htsearch always returns the "No match" page. Check your search form. Chances are there is a hidden input field with no value defined. For example, one user had in his search form, instead of The problem is that Netscape sets the missing value to a default of ” ” (two spaces), rather than an empty string.
