Downloadurl cache

I assume this token is embedded in the pre-authenticated downloadUrl. Further, I theorize that this token is either single-use or it expires relatively quickly How do I ensure that the service is sending me back a "fresh" downloadUrl?

Are there some no-cache headers or something I should explicitly include in my DriveItem request? As mentioned, even though I have the DriveItem object local, I am explicitly re-fetching it from the service to ensure I have the latest properties, and a new downloadUrl. But this is not working. Using the Request object without any extra Headers or other odata parameters is apparently not enough to trigger the generation of a new URL.

This does not happen every test. I believe it happens when re-running a test with the same DriveItem in a short time-window. Again, I'm not sure if the JWT token is single-use or time-expired, but if it's expired in any case, I think the service should automatically generate a new one. If that's not practical, just understanding how to explicitly ask for a new one is certainly effective too! Continuing to debug and try different things, I believe I have found the answer to my question Sending a known-false ETag in the request for the DriveItem seems to force the service to send me a new copy.

Example code as follows:. By implementing their own image download and cache interface a developer can:. Get Code. Check your inbox and click the link to get access. You've successfully subscribed to Advanced Swift!

This cache whose path can be configured in the conan. The cache computes a sha checksum of the download URL and the file checksum whenever is available. As not always the file checksums are available, the download cache will not be able to correctly cache artifacts with revisions enabled if a proxy suddenly and transparently changes a existing server and moves it to a new location, without the clients changing the URL too.

The download cache is activated and configured in the conan. And, as the conan. The downloads cache implements exclusive locks for concurrency, so it can be shared among different concurrent Conan instances. Already on GitHub? Sign in to your account. I used to have in my app Exoplayer version 2. In this app we play HLS videos. I realised one difference in directory where. The text was updated successfully, but these errors were encountered:.

Could you provide more details where this problem occurs? The code snippets above look sensible on a cursory inspection, but it's not possible to say if there is any ExoPlayer problem, an app problem or some missing documentation.