GitHub user ngorchilov opened a pull request:
https://github.com/apache/trafficserver/pull/330
Fix Akamai Live streaming
Akamai live streaming uses If-Modified-Since/Last-Modified headers to
synchronise position between client and server, thus If-Modified-Since
request will always get same timestamp as Last-Modified in response.
ATS discards the 200 OK result and returns 304 Not Modified instead
which freezes the video at the second requested chunk.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ngorchilov/trafficserver master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/330.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #330
----
commit df4cf6b5e112202296efcbd3b7960cacb58a4053
Author: Nikolai Gorchilov <n...@gorchilov.com>
Date: 2015-11-09T21:47:13Z
minor speed optimisation: swap order of if conditions
commit 153e847e339d1b32789875891e6bd34213f8a2b9
Author: Nikolai Gorchilov <n...@gorchilov.com>
Date: 2015-11-09T21:59:24Z
Fix Akamai live streaming: consider response too recent if Last-Modified is
equal to If-Modified-Since
Akamai live streaming uses If-Modified-Since/Last-Modified headers to
synchronise position between client and server, thus If-Modified-Since
request will always get same timestamp as Last-Modified in response.
ATS discards the 200 OK result and returns 304 Not Modified instead
which freezes the video at the second requested chunk.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
