Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DASH MPD file can not be retrieve from CDN due to added clock parameter in queryString &_=Date.now() #238

Closed
edouardbe opened this issue Nov 30, 2015 · 2 comments
Closed

DASH MPD file can not be retrieve from CDN due to added clock parameter in queryString &_=Date.now() #238

edouardbe opened this issue Nov 30, 2015 · 2 comments
Assignees
@joeyparrish
Labels
status: archived Archived and locked; will not be updated status: duplicate A duplicate of another issue; should be closed after linking to the original issue

Comments

@edouardbe
Copy link

DASH MPD file can not be retrieve from CDN due to added clock parameter in queryString &_=Date.now()

Hi,

When the player is requesting the MPD file through a CDN, the added on-the-fly clock-time parameter in the queryString throws an error.
I assume we have a specific configuration with the CDN which clearly rejects all calls with modified urls. We have to put secure tokens to protect our urls and the non-expected and added clock-time parameter is totally inconsistent with our requierements.

So I'm looking for a workaroud to not add the clock-time parameter.

I had a look on the source code :

  • ajax_request.js, lines 249-250
    if ((this.estimator && !this.estimator.supportsCaching()) ||
    this.parameters.synchronizeClock) {
  • and mpd_request.js, line 50, hard coded
    this.parameters_.synchronizeClock = true;

it seems there is no way to disable it programmatically.

Please, could you add a way to disable/enable the synchronizeClock o nthe mpd_request.js file?

By the way, we don only onDemand stream.

Thanks a lot

Regards,

Edouard
@joeyparrish joeyparrish self-assigned this Nov 30, 2015
@joeyparrish
Copy link
Member

Thanks, Edouard. This appears to be a duplicate of #235. Please see the discussion there.

@joeyparrish joeyparrish added the status: duplicate A duplicate of another issue; should be closed after linking to the original issue label Nov 30, 2015
@edouardbe
Copy link
Author

Hi Joey,
Yes, it's a duplicate. Thanks for your attention.
Regards,
Edouard

joeyparrish added a commit that referenced this issue Dec 14, 2015
@joeyparrish
Use configure to disable cache-busting
ef3e38a 
This does not mean that Shaka v1 is suddenly cache-friendly, but this
gives users the option to weigh the problems caused by caching in
Shaka v1 against the problems caused by the cache-buster for certain
CDNs or authentication schemes.  Previously, this would have required
local changes.  Now it can be done in a standard build.

The parameter name is extra long and wordy to make sure that it cannot
be used without acknowledging that there are trade-offs involved.

Closes #235, #238, #76

Change-Id: I934a5703183d31250458b80cb38d2b5deae410df
@shaka-project shaka-project locked and limited conversation to collaborators Mar 22, 2018
@shaka-bot shaka-bot added the status: archived Archived and locked; will not be updated label Apr 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@joeyparrish joeyparrish

Labels
status: archived Archived and locked; will not be updated status: duplicate A duplicate of another issue; should be closed after linking to the original issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@TheModMaker @joeyparrish @shaka-bot @edouardbe