Stas Bekman wrote: >Geoffrey Young wrote: > > >>>Since when unescaped & in the QUERY_STRING part of the URL are not allowed? >>> >>> >>I dunno the specifics, but if you try using the w3c validator you end up >>with something like this >> >> reference not terminated by REFC delimiter >> >> <a href="http://example.com/foo.pl?foo=bar®=foobar";>is this valid?</a> >> >> If you meant to include an entity that starts with "&", then you should >> terminate it with ";". Another reason for this error message is that you >> inadvertently created an entity by failing to escape an "&" character just >> before this text. >> >>I swear last time I checked my own html there was a pointer to the >>appropriate rfc, but I guess not. >> >> > >OK, in which case it must be some relatively recent change, since an >unescaped & in the QUERY_STRING was a valid separator. A pointer to the >relevant RFC would be nice so we can add that to the URL that started this >thread. > Here?
http://www.w3.org/TR/1999/REC-html401-19991224/appendix/notes.html#h-B.2.2 ------------------------------------------------ Radan Computational Ltd. The information contained in this message and any files transmitted with it are confidential and intended for the addressee(s) only. If you have received this message in error or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Radan Computational Ltd. The recipient(s) of this message should check it and any attached files for viruses: Radan Computational will accept no liability for any damage caused by any virus transmitted by this email.
