David Adams wrote:
> The second is when a page's author has mistakenly marked up a bare '&' in
> the URL as '&'. This is - of course - wrong, and htdig does not
> find the page. For example:
Encoding bare ampersand characters as HTML entities in URLs is not only
correct,
but also required by HTML 4.01 specification as issued by W3C.
You will need Ht://Dig >= v3.1.4 to process entity encodings in URLs
correctly.
The first problem seems mainly to be related to the shell handling the
ampersand
character as a special character.. I suspect "parsedoc.pl" not to
shell-escape the
command string correctly, thus trying to have the shell execute
"line.ps" as a
command itself. This could also be a security issue if there is such an
executa-
ble on the system that could be run.
Maybe it can be fixed by shell-escaping "$parsecmd" in "parsedoc.pl"?
hth,
Torsten
--
InWise - Wirtschaftlich-Wissenschaftlicher Internet Service GmbH
Waldhofstra�e 14 Tel: +49-4101-403605
D-25474 Ellerbek Fax: +49-4101-403606
E-Mail: [EMAIL PROTECTED] Internet: http://www.inwise.de
------------------------------------
To unsubscribe from the htdig mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
