Re: Docs error?

[prev] [thread] [next] [Date index for 2005/04/26]

Steve Hay wrote:
> 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&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.
>>
> 
> Here?
> 
> http://www.w3.org/TR/1999/REC-html401-19991224/appendix/notes.html#h-B.2.2

Thanks Steve,

So should we commit something like the following? Or should we just nuke 
the whole section altogether?

Index: src/docs/tutorials/client/browserbugs/browserbugs.pod
===================================================================
--- src/docs/tutorials/client/browserbugs/browserbugs.pod       (revision 
164401)
+++ src/docs/tutorials/client/browserbugs/browserbugs.pod       (working copy)
@@ -37,6 +37,12 @@

  =head1 Preventing QUERY_STRING from getting corrupted because of &entity 
key names

+This entry is now irrelevant since you must not use C<&> to separate
+fields in the C<QUERY_STRING> as explained here:
+http://www.w3.org/TR/1999/REC-html401-19991224/appendix/notes.html#h-B.2.2
+If for some reason, you still want to do that, then make sure to read
+the rest of this section.
+
  In a URL which contains a query string, if the string has multiple
  parts separated by ampersands and it contains a key named "reg", for
  example C<http://example.com/foo.pl?foo=bar&reg=foobar>;, then some


        -- 
        __________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@xxxxxx.xxx http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com