W3C home > Mailing lists > Public > public-media-fragment@w3.org > March 2010

Re: Percent encoding

From: Yves Lafon <ylafon@w3.org>
Date: Wed, 3 Mar 2010 08:31:06 -0500 (EST)
To: raphael.troncy@eurecom.fr
cc: Philip Jšgenstedt <philipj@opera.com>, Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Media Fragment <public-media-fragment@w3.org>, Jack Jansen <Jack.Jansen@cwi.nl>
Message-ID: <alpine.DEB.1.10.1003030829410.4238@wnl.j3.bet>
On Tue, 2 Mar 2010, RaphaŽl Troncy wrote:

> Dear Philip,
>
>> Perhaps YouTube decodes first and splits last, or perhaps they just use
>> a regexp to find v=XXXXX anywhere. Whatever is the case with YouTube, I
>> assume we want to match as closely as possible how query strings works
>> in e.g. ASP, PHP, JSP and Perl CGI, or there is no benefit in using
>> something that resembles query strings.
>> 
>> We can never be 100% compatible, for reasons listed in a note after
>> http://www.w3.org/2008/WebVideo/Fragments/WD-media-fragments-spec/#decode-a-percent-encoded-string
>
> Thanks, the note is indeed really useful. For all the following statements, 
> do you think it is possible to indicate a suitable reference?
>    *  "&" is the only primary separator for name-value pairs, but some 
> server-side languages also treat ";" as a separator.
>    * name-value pairs with invalid percent-encoding should be ignored, but 
> some server-side languages silently mask such errors.
>    * The "+" character should not be treated specially, but some server-side 
> languages replace it with a space (" ") character.

+ is in sub-delims, along with & ; and others
(cf rfc3986)

>    * Multiple occurrences of the same name must be preserved, but some 
> server-side languages only preserve the last occurrence.
>
> Best regards.
>
>  RaphaŽl
>
>

-- 
Baroula que barouleras, au tiťu toujou t'entourneras.

         ~~Yves
Received on Wednesday, 3 March 2010 13:31:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 21 September 2011 12:13:38 GMT