David E. Ross wrote:
I previously referred to RFC 3986. Please read it.
Note that& is a special character in HTML. Since RFC 3986 specifies
its use as the separation character before a query in a URI, HTML
provides for& in place of& in a URI. Browsers translate&
into& when ever it is found, in a URI or in plain text content. I do
not think browsers support %26 for that purpose within a URI.
Actually, it's not hard to find places on the web where a link passes a
URL to a script that does something before redirecting, so you get
something like this:
<a
href="http://www.originaldomain.com/cgi-bin/a2/out.cgi?u=http://targetdomain.com/specificpage.html";>display
text</a>
In such a context, it's not unusual for the embedded URL to be
percent-encoded for benefit of the script that will read it.
--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
