Subject: Re: [htdig] Ampersand in URL
From: Torsten Neuer (email@example.com)
Date: Mon Jan 17 2000 - 09:46:11 PST
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
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
The first problem seems mainly to be related to the shell handling the
character as a special character.. I suspect "parsedoc.pl" not to
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
ble on the system that could be run.
Maybe it can be fixed by shell-escaping "$parsecmd" in "parsedoc.pl"?
-- InWise - Wirtschaftlich-Wissenschaftlicher Internet Service GmbH Waldhofstraße 14 Tel: +49-4101-403605 D-25474 Ellerbek Fax: +49-4101-403606 E-Mail: firstname.lastname@example.org Internet: http://www.inwise.de
------------------------------------ To unsubscribe from the htdig mailing list, send a message to email@example.com You will receive a message to confirm this.
This archive was generated by hypermail 2b28 : Mon Jan 17 2000 - 09:47:03 PST