On Tue, Jul 7, 2015 at 10:41 PM, Jonas Sicking <[email protected]> wrote: > At the very least I'd like to see solid data on that CDNs most of the > time support updating the manifest in-place
I might be misreading the question, but I'll give it a try. >From both past work experience and vendor docs, CDN vendors typically allow a URL to cleared by both: * CDN TTL expiring, which is derived from an HTTP header (could be a vendor specific header) * Manual purge request for a URL, either via an API or management console Looking at a graph of CDN market share[1], the top 3 vendors used on Alexa top 1M sites are: * Amazon CloudFront * Akamai * MaxCDN Let's examine their updating abilities: # Amazon CloudFront * TTL control via Cache-Control or an Expires header, among others[2] * Invalidation request to purge an object[3] # Akamai * TTL control via headers (docs seem to require an Akamai account to view) * Purge specific files via API[4] # MaxCDN * TTL control via Cache-Control[5] * Purge specific files via management console[6] So, at least for all of these vendors, there are several options you can use to update the manifest without changing the URL. [1]: http://www.datanyze.com/market-share/CDN/ [2]: http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/RequestAndResponseBehaviorS3Origin.html#RequestS3Caching [3]: http://docs.aws.amazon.com/AmazonCloudFront/latest/APIReference/CreateInvalidation.html [4]: https://developer.akamai.com/api/purge/ccu/overview.html [5]: https://www.maxcdn.com/one/tutorial/using-cache-control-headers/ [6]: https://www.maxcdn.com/one/tutorial/purge-cache-on-cdn/ - Ryan _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
