If you are not using Dataweavers Arc, revalidating by tag or content tag is dependent on your application serving tags to Cloudflare under the "Cache-Tag" HTTP Header.
The Cloudflare Provider screen manages Cloudflare-specific settings for an environment, used to purge the Cloudflare cache as part of the post-regeneration actions. A status badge (Configured / Not Configured) indicates whether an API Key is currently stored. The fields below describe every option on the page, including their purpose and defaults.
| Field | Description | Default |
|---|---|---|
| Name | Display name for this provider. | |
| Zone Id | The Cloudflare zone identifier, taken from the Cloudflare zone overview page. | |
| Purge Type | Whether to purge either; ByUrl : this will purge pages by the url of each page - relies on the host configuration being accurate in the Site configuration. ByTag : this will purge pages by the tag that is configured on the site configuration. This effectively purges the cloudflare cache for the whole site for each publish. ByContentTag (only for AppRouter with Tag-based Revalidation) : this will purge the cache by tag, however the tag is based on each page's Item ID. Requires additional setup in the NextJS App - see <link to content tagging article> | ByTag |
| Cache Tag (default/fallback) | The default Cache-Tag used when Purge Type is ByTag. Tags can also be specified per site (see site configuration); this value is used as a fallback if a site tag is not supplied for all sites in the payload. | |
| Batch Size | The maximum number of paths/tags for each Cloudflare purge | 500 |
| Retry Attempts | The number of retry attempts when a purge fails. Minimum 0. | 0 |
| API Key | The Cloudflare API Key used to authenticate purge requests. |
Actions
- Save - Saves the Cloudflare provider settings.
- Cancel - Discards changes and returns to the Providers list.