On 2/21/12 10:10 PM, Paul B. Gallagher wrote: > 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. >
In that case: 1. A browser is not handling percent-encoded separation characters; a script is handling them. 2. The script must convert the percent-encoded separation characters back into the actual separation characters before sending the URI to a Web server. -- David E. Ross <http://www.rossde.com/>. Anyone who thinks government owns a monopoly on inefficient, obstructive bureaucracy has obviously never worked for a large corporation. © 1997 by David E. Ross _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
