Geoffrey Young wrote:
Oh, I see, I thought you were talking a bug in the docs building system.

But if you write:

 'http://example.com/foo.pl?foo=bar&reg=foobar'.

There is no problem whatsover. Since there is no &reg here.


exactly :)


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&reg=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.


--
__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

Reply via email to