Issue in ./help/assets/invalidate-cdn-cache-dynamic-media.md
A customer asked how to invalidate all renditions of an asset in DynamicMedia/Scene7 using SmartCrop, where the number of renditions are dynamic (dynamically generated by the client based on screen/browser-size).
This seems possible , but only on "custom domains" (see below).
This information should be added to the public documentation.
Please add:
Cache-key and cache invalidation works differently depending on what delivery domain you are using.
If you are using a generic domain, e.g. s7g10.scene7.com, then each and every URL needs to be individually invalidated.
If you however are making use of a customer specific domain setup on one of the SmartImaging CDN configs, then only the part of the URL before the question mark needs to be submitted for invalidation (asset-path without parameters), and that removes any and all variations of the query-string from cache as part of that invalidation request.
(see: E-000750746)
which alternative prove here:
If customer is on SmartImaging BFC2 (e.g. .scene7.com or some custom domain), then the cache-key is configured differently, where submitting an asset URL up to the “?”, will purge all query strings of that URL as well. This means one would need to invalidate each SmartCrop (https://.scene7.com/is/image//image:smartcrop1 , https://.scene7.com/is/image//image:smartcrop2 ), and that would invalidate any query-strings the customer might use to these URLs, such as https://.scene7.com/is/image//image:smartcrop1?wid=300&croppathE=path1
Issue in ./help/assets/invalidate-cdn-cache-dynamic-media.md
A customer asked how to invalidate all renditions of an asset in DynamicMedia/Scene7 using SmartCrop, where the number of renditions are dynamic (dynamically generated by the client based on screen/browser-size). This seems possible , but only on "custom domains" (see below). This information should be added to the public documentation.
Please add:
which alternative prove here: