Re: Percent encoding

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.
     * Multiple occurrences of the same name must be preserved, but some 
server-side languages only preserve the last occurrence.

Best regards.

   RaphaŽl

-- 
RaphaŽl Troncy
EURECOM, Multimedia Communications Department
2229, route des CrÍtes, 06560 Sophia Antipolis, France.
e-mail: raphael.troncy@eurecom.fr & raphael.troncy@gmail.com
Tel: +33 (0)4 - 9300 8242
Fax: +33 (0)4 - 9000 8200
Web: http://www.eurecom.fr/~troncy/

Received on Tuesday, 2 March 2010 10:40:41 UTC