- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Thu, 4 Mar 2010 12:25:48 +1100
- To: raphael.troncy@eurecom.fr
- Cc: Media Fragment <public-media-fragment@w3.org>
On Thu, Mar 4, 2010 at 12:00 AM, Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote: > 2010/3/3 Raphaël Troncy <raphael.troncy@cwi.nl>: > >> Another problem is how should we express that when 2 tracks have been >> requested? > > The background here is that using a comma as in track=audio,subtitle > will not work in the HTTP headers, since the comma is used to separate > headers from each other. As such, something like: > Content-Range: track audio,subtitle/653.791 > would be parsed to > Content-Range: track audio > Content-Range: subtitle/653.791 > which is obviously incorrect. Incidentally, I just checked on the idea of the "comma" being a header separator. I found this implementation by Microsoft of a Content-Range with a different unit range: http://msdn.microsoft.com/en-us/library/ee159574%28EXCHG.80%29.aspx It uses the comma to separate multiple ranges. Also, I checked the HTTP specification and wasn't able to find anywhere that the comma is indeed used for such header separation. According to http://www.cs.columbia.edu/sip/syntax/rfc2068.html the characters in tspecials are explicitly allowed as field-content. Yves, can you provide a link to where that use of comma in HTTP header fields is forbidden? Thanks, Silvia.
Received on Thursday, 4 March 2010 01:26:40 UTC