W3C home > Mailing lists > Public > www-amaya@w3.org > July to September 1999

Re: Amaya mishandling HREF values that contain ampersand

From: Malcolm Austen <malcolm.austen@computing-services.oxford.ac.uk>
Date: Tue, 6 Jul 1999 12:20:47 +0100 (BST)
To: "Alan J. Flavell" <flavell@a5.ph.gla.ac.uk>
cc: Amaya List <www-amaya@w3.org>
Message-ID: <Pine.OSF.4.10.9907061208310.32094-100000@ermine.ox.ac.uk> 
On Tue, 6 Jul 1999, Alan J. Flavell wrote:

+ The archive contains a message
+ http://lists.w3.org/Archives/Public/www-amaya/1999AprJun/0082.html

I don't recall the message and the archive has just timed out on me ...

+ I recently got involved elsewhere in a discussion of this issue, i.e
+ when forming an HREF to a URL that contains an ampersand, the need to
+ represent the ampersand as &amp; .  In general, omitting to do so will
+ result in failure of HTML syntax validation (on the grounds of an
+ undefined entity), as I'm sure is well known.  But after writing &amp;
+ the HREF no longer works correctly in Amaya.

Surely, in a URL an ampersand is escaped as %26 ?

&amp; is the escape in html and the (quoted) string value in an href isn't
html. Does it need to be escaped in the URL? - I haven't checked the rules
but don't the quotes protect it from the (html) "&" escape mechanism?

 ... but maybe I missed something obvious and am talking rubbish 8-)

regards,
	Malcolm.

 Malcolm.Austen@OUCS.ox.ac.uk     http://users.ox.ac.uk/~malcolm/
Received on Tuesday, 6 July 1999 08:45:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 20 September 2007 14:24:25 GMT