[vlc-devel] Broken Amazon S3 Streaming

[Laurent Aimar]

Hi,

On Mon, Jun 18, 2012 at 08:30:03PM +0200, Francois Cartegnie wrote:
> 
> Hi,
> 
> Here's an Amazon's CDN reply for its hosted streams:
> 
> HTTP/1.0 200 OK
>   x-amz-id-2:
> OAaIbl2xQtPYb19T/EbjE4+siG8DLLiSw+/JJ5uV1r6u0q+t/ffwxGPt21AtDn3O
>   x-amz-request-id: 86A37EFDA3FE5D4A
>   Date: Sun, 17 Jun 2012 15:48:01 GMT
>   Cache-Control: public
>   Expires: Sun, 08 Aug 2100 00:00:00 GMT
>   Last-Modified: Sun, 17 Jun 2012 03:20:02 GMT
>   ETag: "22bd79902b6b53aa5d301dfe0ae1f4e2"
>   Accept-Ranges: bytes
>   Content-Type:
>   Content-Length: 1317245
>   Server: AmazonS3
>   Age: 93466
>   X-Cache: Hit from cloudfront
>   X-Amz-Cf-Id:
> e99fI8jp1OBsnd_JSq17JkcvT6l2pgIDl8ecd-EydI_-dF9MFRc_Nw==,x4GaJlOMzYizeCH7NN2QuJJWrWM2vMQI5o01qPMsnkyHdF-LWQXs4w==
>   Via: 1.0 e87f79edaf51ca569912b13429de71d2.cloudfront.net (CloudFront)
>   Connection: keep-alive
> 
> 
> VLC discards such MP4 stream, that's an old known problem.
> http://trac.videolan.org/vlc/ticket/1275
> 
> Which is also due to an old Amazon S3 bug.
> https://forums.aws.amazon.com/message.jspa?messageID=162333
> 
> As mentioned they recently added the:
> "  Accept-Ranges: bytes" (see above)
> as a fix. Custome header then as this one is not part of the HTTP/1.0 spec.
> 
> Annoying, as S3 is a major CDN.
> Can't change things to flag the input as seekable when "Accept-Range" is
> replied ?
 The current http access shoud already do this (I have only check master).

Regards,

-- 
fenrir