[ 
https://issues.apache.org/jira/browse/SLING-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490035#comment-15490035
 ] 

Ashok Kumar commented on SLING-6046:
------------------------------------

[~ianeboston] We should send this header for all requests if we do not find a 
reason not to send it with all responses. Large File download requires download 
managers to support resume able downloads , only possible if sling supports 
true Byte Serving. E.g. sites like dropbox, google drive always sends partial 
response for heavy content stored in cloud. 

As you rightly said chunk transfer encoding does not support fast forwarding 
and user always end up downloading entire mp4 file but in chunks. whereas byte 
serving is by definition is to support streaming of area of interests , which 
is more powerful feature in case of videos where user wants to skip timelines. 
I was not sure if sending Accept-Range header with all responses from sling 
would be conflicting with other response-headers or not, so I did a patch only 
for video/mp4 format which gets played on MS browsers. I am in agreement to 
Julian's suggestion of putting it for all "video/*" as an interim relief to 
video consumers. 

CC: [~shgupta] , [[email protected]]



> 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, 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
(v6.3.4#6332)

Reply via email to