[
https://issues.apache.org/jira/browse/SLING-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490071#comment-15490071
]
Ian Boston commented on SLING-6046:
-----------------------------------
Could you share a the request and response for the very first request for the
Video in IE please ?
In Chrome it loads the html file, and the very first response which doesnt know
anything about the server is:
{code}
Accept:*/*
Accept-Encoding:identity;q=1, *;q=0
Accept-Language:en-US,en;q=0.8,pt;q=0.6
Cache-Control:no-cache
Connection:keep-alive
Host:tautils.s3.amazonaws.com
Pragma:no-cache
Range:bytes=0-
User-Agent:Mozilla/5.0 ...
{code}
Then the response is
{code}
Accept-Ranges:bytes
Age:1
Connection:keep-alive
Content-Length:44811898
Content-Range:bytes 0-44811897/44811898
Content-Type:video/mp4
Date:Wed, 14 Sep 2016 10:12:10 GMT
ETag:"48217968ec2776736bc806334f3846a0"
Last-Modified:Tue, 06 Sep 2016 15:04:00 GMT
Server:AmazonS3
{code}
I am interested in what IE does as it won't have a Accept: bytes header when it
makes its first and only request to the S3 server. Using the Chrome request
saves as curl and dropping the range header indicates the S3 server will
respond with the full response leaving IE in a catch 22 situation. If it does a
GET first, with no range header it will get the whole file. It might be able to
send a HEAD first to check or it could drop the connection early and resubmit
with a range header. Which does it do ?
> 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)
