Michael MD wrote:
>> not a third party on the planet that knows how to write a valid
>> script tag
>> or encode ampersands...
> I've sometimes had to modify existing php and perl scripts to handle
> encoded
> ampersands.
> It seems that neither php 4's $_GET or $_REQUEST nor perl's "param"
> handle
> encoded ampersands in query strings
> (you often end up with "amp;key" rather than just "key") so I often
> have to
> handle this in the script itself.
This sounds like an error in the URL, not in the parser.

In a URL, an & character as data should be represented as %26

In a URL, an & character as a query string part separator should be
represented as &

In HTML (including an HTML representation of a URL), an & character
should be represented as &

The user agent (e.g. browser, bot, etc) should decode the & in the
HTML to get & in the DOM, so when it requests the URL from the
webserver, it requests &.

It sounds like & is being requested. So the fault is in the tool
making the request, not in the tool parsing it.

David Dorward

List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm

Reply via email to