- From: Tom James <tom.james@digitext.com>
- Date: Thu, 3 Oct 2002 17:21:15 +0100
- To: "'w3c-wai-ig@w3.org'" <w3c-wai-ig@w3.org>
- Cc: "'jonathan chetwynd'" <j.chetwynd@btinternet.com>
Jonathan Chetwynd wrote ... > this works > > http://www.live365.com/cgi-bin/mini.cgi?membername=tuluum&url= > http%3A//www.l > ive365.com/cgi-bin/mini.cgi%3Fmembername%3Dtuluum&tm=1033561327384 > > this does not > http://www.live365.com/cgi-bin/mini.cgi?membername=tuluum& > url=http%3A//w > ww.live365.com/cgi-bin/mini.cgi%3Fmembername%3Dtuluum&tm=1 > 033561327384 I'm assuming that you cut this from the browser location field. What is important (from a validator point of view) is writing the entity correctly in the HTML code, not what is displayed by the browser. Thus, to get a URL like: http://example.com/script.cgi?parameter1=value1¶meter2=value2 ... you would code it: <a href="http://example.com/script.cgi?parameter1=value1&parameter2=value2" >link text</a> (note that the "&" separator is coded as "&" in the raw code but displays as "&" in the browser). You wouldn't expect http://example.com/script.cgi?parameter1=value1&parameter2=value2 to work if pasted directly into a browser location field. My guess is that when trying to execute, the script would assigne "value1" to a variable called "parameter1", but would then try and assign "value2" to a variable called "amp;parameter2". Different scripts and scripting langugaes would probably fail in different ways with this. Tom Dr Tom James Senior Consultant =============================================================== Digitext - Online Information at Work Telephone: +44 (0)1844 214690 Fax: +44 (0)1844 213434 Email: tom.james@digitext.com Web: http://www.digitext.com/
Received on Thursday, 3 October 2002 12:20:36 UTC