Ian Boston commented on SLING-6046:

a) thank you for the pointer to RFC 7233, although I can see some 
clarifications I can't see a significant rewrite of Range handling relative to 
RFC 2616 which iirc was the original http 1.1 spec. 
b) Won't MS say its the servers problem to deal with broken streams ? imho 
thats true, and we need to do that as well.
c) I agree, just looked at the definition of 206 which states "The request MUST 
have included a Range header field ..." so would probably not work.

Based on that Sling, the patch is Ok and we have to deal with the resource 
consumption caused by the broken stream.

> While Streaming Video to IE 11, StreamRendererServlet do not use Partial 
> Content Response [code 206]
> ----------------------------------------------------------------------------------------------------
>                 Key: SLING-6046
>                 URL: https://issues.apache.org/jira/browse/SLING-6046
>             Project: Sling
>          Issue Type: Bug
>          Components: Servlets
>    Affects Versions: Servlets Get 2.1.18
>            Reporter: Ashok Kumar
>         Attachments: Accept-Range Respone Header from S3.png, 
> NetworkDataS3VideoFromIE11.xml, S3video.html, StreamRendererServlet.java.patch
> Since IE 11 expects "Accept-Ranges" [0] response header to start making 
> requests with Range header, so sling lack in streaming of video content for 
> IE end users. We can add Accept-Ranges = bytes header to response , either 
> selectively only for video/mp4 mimetype ( video tag on IE looks for mp4 )  or 
> always.
> Without support of partial content response (206) for IE users, all large 
> video files are being downloaded in single chunk and user need to wait for 
> long to see video content playing. 
> [0] http://stackoverflow.com/questions/25654422/http-pseudo-streaming-in-ie11 

This message was sent by Atlassian JIRA

Reply via email to