func (r Network_ContentDelivery_Account) PurgeCache(objectUrls []string) (resp []datatypes.Container_Network_ContentDelivery_PurgeService_Response, err error) {
	params := []interface{}{
		objectUrls,
	}
	err = r.Session.DoRequest("SoftLayer_Network_ContentDelivery_Account", "purgeCache", params, &r.Options, &resp)
	return
}
// CDN's cache mechanism works similar to that of web browsers. When CDN pulls a file from your origin server or from your CDN FTP directory for the first time, it creates a cache file on itself. CDN re-uses cache files to save trips to the origin server and thus it speeds up delivering content to visitors. This method removes cached objects on every server in the CDN network. If you see a stale content or a file that send an incorrect header, purging cache will correct the issue. CDN will pull a fresh content from your origin server or your CDN FTP.
//
// This method takes an array of URLs. A URL must be exact as it is being requested by clients. An example URLs may look like this:
// * http://<your CDN username>.http.cdn.softlayer.net/mycdnname/some_file.txt
//
//
// If you created a CNAME that points to CDN host, use your CNAME URL instead.
// * http://image.mydomain.com/some_file.txt
//
//
// It takes approximately 3-5 minutes for the system to delete the requested object on every CDN server from submission .
CDN's cache mechanism works similar to that of web browsers. When CDN pulls a file from your origin server or from your CDN FTP directory for the first time, it creates a cache file on itself. CDN re-uses cache files to save trips to the origin server and thus it speeds up delivering content to visitors. This method removes cached objects on every server in the CDN network. If you see a stale content or a file that send an incorrect header, purging cache will correct the issue. CDN will pull a fresh content from your origin server or your CDN FTP.

This method takes an array of URLs. A URL must be exact as it is being requested by clients.

If you created a CNAME that points to CDN host, use your CNAME URL instead.

It takes approximately 3-5 minutes for the system to delete the requested object on every CDN server from submission .
// CDN ' s cache mechanism works similar to that of web browsers . When CDN pulls a file from your origin server or from your CDN FTP directory for the first time it creates a cache file on itself . CDN re - uses cache files to save trips to the origin server and thus it speeds up delivering content to visitors . This method removes cached objects on every server in the CDN network . If you see a stale content or a file that send an incorrect header purging cache will correct the issue . CDN will pull a fresh content from your origin server or your CDN FTP . // // This method takes an array of URLs . A URL must be exact as it is being requested by clients . An example URLs may look like this : // * http : // <your CDN username > . http . cdn . softlayer . net / mycdnname / some_file . txt // // // If you created a CNAME that points to CDN host use your CNAME URL instead . // * http : // image . mydomain . com / some_file . txt // // // It takes approximately 3 - 5 minutes for the system to delete the requested object on every CDN server from submission .
func (r Network_ContentDelivery_Account) PurgeCache(objectUrls []string) (resp []datatypes.Container_Network_ContentDelivery_PurgeService_Response, err error) {
	params := []interface{}{
		objectUrls,
	}
	err = r.Session.DoRequest("SoftLayer_Network_ContentDelivery_Account", "purgeCache", params, &r.Options, &resp)
	return
}
func ( r Network_ContentDelivery_Account ) PurgeCache ( objectUrls [ ] string ) ( resp [ ] datatypes . Container_Network_ContentDelivery_PurgeService_Response , err error ) { params := [ ] interface { } { objectUrls , } err = r . Session . DoRequest ( " " , " " , params , & r . Options , & resp ) return }
CDN's cache mechanism works similar to that of web browsers.
CDN ' s cache mechanism works similar to that of web browsers .