[
https://issues.apache.org/jira/browse/SLING-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732181#comment-15732181
]
Felix Meschberger commented on SLING-6046:
------------------------------------------
I think we should not apply the patch as is. But as discussed along the thread,
adding the {{Accept-Range: bytes}} header if the content passes a certain
size-threshold such as 1MB or so (may more) sounds reasonable to me.
In any case, we should not make sending the header contingent on some content
type, because that is very brittle: It sounds easy for _video/*_ content types
but there may be vendor content types out there which would fail setting the
header.
> 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
> Fix For: Servlets Get 2.1.20
>
> 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
(v6.3.4#6332)
