Forwards the supplied list of URLs to the Scene7 CDN (Content Distribution Network) provider to invalidate their existing cache of HTTP responses.
CDN cache invalidation forces all HTTP requests for these URLs to be revalidated against the current published data on the Scene7 network once this invalidation request is processed through the CDN network. Any URLs that are not connected to the Scene7 service URL structure and directly matching the Scene7 company root ID assigned when the company is created will result in an API fault for the entire request. Any invalid URLs that the CDN does not support that it considers invalid will also result in an API fault for the entire request.
Frequency of Use: Rules
The rules governing the frequency of the use of this feature are controlled by Scene7's CDN partners. The CDN retains the discretion to degrade the responsiveness of these invalidations to maintain optimum performance of its service to its users. Should Scene7 be notified of overuse of this feature we will need to resort to disabling the feature on either a per company basis or entirely across the service.
Confirmation emails from the Scene7 CDN partner can be sent to the list's creator or up to 5 other email addresses. The API sends the confirmation when the entire CDN network has been notified that the URLs referenced in the email have been cleared. A single call to cdnCacheInvalidation can send multiple emails if the number of URLs supplied exceed the number that Scene7 can deliver to the CDN partner on a single notification. Currently, that would be if the request exceeds 100 URLs, but is subject to change based at the request of the CDN partner.
Authorized User Types
Input ( cdnCacheInvalidationParam )
The handle to the company connected with the URLs to invalidate.
List of up to 1000 URLs to invalidate from the CDN cache. All URLS must contain the Scene7 company root ID to be invalidated.
Output ( cdnCacheInvalidationReturn )
A handle referencing the purge request.
The cdnCacheInvalidation API now invalidates the cache almost immediately (~5 seconds). As such, polling for invalidation status is generally no longer required.
Estimated seconds to completion of the purge request. Clients should wait for this time before polling status.
This example requests four URLs to be invalidated in the CDN cache. The response contains summary counts of the success of the operations and a list of error details supplied directly from the CDN to assist the client in use of this feature.
<cdnCacheInvalidationParam xmlns="http://www.scene7.com/IpsApi/xsd/2012-02-14"> <companyHandle>c|6</companyHandle> <urlArray> <items>http://s7d7.scene7.com/is/image/JJEsquire/11008047?$thumbnail$</items> <items>http://s7d7.scene7.com/is/image/JJEsquire/11008047?$product$</items> <items>http://s7d7.scene7.com/is/image/JJEsquire/11008047?$large$</items> <items>http://s7d7.scene7.com/is/image/JJEsquire/ImageSetConfigDefaults?req=userdata</items> </urlArray> </cdnCacheInvalidationParam>
<cdnCacheInvalidationReturn xmlns="http://www.scene7.com/IpsApi/xsd/2012-02-14"> <successCount>4</successCount> <warningCount>0</warningCount> <errorCount>0</errorCount> </cdnCacheInvalidationReturn>