Acquia recommends the following best practices for using Acquia Edge:
Acquia recommends the following defaults for page caching rules in Edge CDN:
EdgeRespect Existing HeadersYou should also configure Page Cache Maximum Age (the amount of time Varnish® and Drupal take to cache your assets) to your desired value—typically 30 minutes to one day. Edge CDN will contact Varnish once per minute for updated copies of an asset.
For more information on caching with Acquia Edge, see Caching recommendations for Acquia Edge.
The cache size limit is 2 GB per file. You can increase the size to 20 GB for an extra cost per gigabyte. Contact your Account Manager for more information.
If your content or assets change at origin in your Drupal website, and you must update the cached copies of the assets before the Page Cache Maximum Age expiration date, Acquia recommends you use the Acquia Purge module.
After you configure the Acquia Purge module, content updates will purge selected portions of Varnish cache. The next time Edge CDN requests the asset from Varnish, Edge CDN will receive the newly-updated content.
Due to API limitations preventing website visitors from viewing updates to content, Acquia does not recommend using the CloudFlare Purge (cfpurge) module.
When purging caches on Edge CDN using the API or the dashboard, the Cache-Tag Header (including whitespace and commas) must not exceed 255 bytes in total length after the header field name. If the supplied Cache-Tag header exceeds 255 bytes in length, Acquia Edge will purge only the tags in the first 255 bytes.
Acquia Edge provides subscribers with access to web log data on a per-domain basis. You can forward the web logs for aggregation and analysis using Enterprise Log Sharing.
Acquia Edge retains audit logs for 18 months and access logs for three days. You may access the logs using the Cloudflare API.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Acquia recommends the following best practices for using Acquia Edge:
Acquia recommends the following defaults for page caching rules in Edge CDN:
Respect Existing HeadersYou should also configure Page Cache Maximum Age (the amount of time Varnish® and Drupal take to cache your assets) to your desired value—typically 30 minutes to one day. Edge CDN will contact Varnish once per minute for updated copies of an asset.
For more information on caching with Acquia Edge, see Caching recommendations for Acquia Edge.
The cache size limit is 2 GB per file. You can increase the size to 20 GB for an extra cost per gigabyte. Contact your Account Manager for more information.
If your content or assets change at origin in your Drupal website, and you must update the cached copies of the assets before the Page Cache Maximum Age expiration date, Acquia recommends you use the Acquia Purge module.
After you configure the Acquia Purge module, content updates will purge selected portions of Varnish cache. The next time Edge CDN requests the asset from Varnish, Edge CDN will receive the newly-updated content.
Due to API limitations preventing website visitors from viewing updates to content, Acquia does not recommend using the CloudFlare Purge (cfpurge) module.
When purging caches on Edge CDN using the API or the dashboard, the Cache-Tag Header (including whitespace and commas) must not exceed 255 bytes in total length after the header field name. If the supplied Cache-Tag header exceeds 255 bytes in length, Acquia Edge will purge only the tags in the first 255 bytes.
Acquia Edge provides subscribers with access to web log data on a per-domain basis. You can forward the web logs for aggregation and analysis using Enterprise Log Sharing.
Acquia Edge retains audit logs for 18 months and access logs for three days. You may access the logs using the Cloudflare API.
If this content did not answer your questions, try searching or contacting our support team for further assistance.