You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Devin Ben-Hur <db...@eMerchandise.com> on 2000/08/03 21:13:38 UTC

Naked & in URL (was Re: Templating System)

"Keith G. Murphy" wrote:
> Are there any browsers that do not actually handle the naked '&'
> correctly?  I confess that I also missed this, though I do understand
> the reason: the first one's invalid HTML.  It just seems to always work.

Think about this:
 <A HREF="/somehandler?email=a%40xyz.com&copy=b%40xyz.com">
vs:
 <A HREF="/somehandler?email=a%40xyz.com&amp;copy=b%40xyz.com">

Is the &copy in the first one the HTML entity for the copyright
c-in-circle character or the query string argument seperater followed by
an argument named 'copy'?

Different browsers will make different interpretations depending on how
well they adhere to the HTML spec, their known named entity list, and
how hard they try to "do the right thing" with the erroneous naked
ampersand.

-- 
Devin Ben-Hur     | President / CTO  | mailto:dbenhur@eMerchandise.com
The eMarket Group | eMerchandise.com | http://www.eMerchandise.com
503/944-5044 x228 | 
"The reasonable man adapts himself to the world; the unreasonable one
 persists in trying to adapt the world to himself. Therefore all 
 progress depends on the unreasonable man."  -- George Bernard Shaw