-
Notifications
You must be signed in to change notification settings - Fork 10.4k
ack-cf/purge-for-all #21354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
ack-cf/purge-for-all #21354
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,17 @@ | ||
| --- | ||
| title: All Purge Methods Available for All Plans | ||
| description: All Cloudflare plans can purge by tag, prefix, url, host, or everything to invalidate cached content on the fly. | ||
| date: 2025-04-01T12:50:40Z | ||
nikitacano marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| --- | ||
|
|
||
| You can now use all purge methods available on Cloudflare, regardless of plan type. Previously, methods other than "purge by URL" and "purge everything" were exclusive to Enterprise customers. | ||
nikitacano marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| **Anyone on Cloudflare can now:** | ||
| 1. [Purge Everything](/cache/how-to/purge-cache/purge-everything/): Clears all cached content associated with a website. | ||
| 2. [Purge by Prefix](/cache/how-to/purge-cache/purge_by_prefix/): Targets URLs sharing a common prefix. | ||
| 3. [Purge by Hostname](/cache/how-to/purge-cache/purge-by-hostname/): Invalidates content by specific hostnames. | ||
| 4. [Purge by URL (single-file purge)](/cache/how-to/purge-cache/purge-by-single-file/): Precisely targets individual URLs. | ||
| 5. [Purge by Tag](/cache/how-to/purge-cache/purge-by-tags/): Uses Cache-Tag response headers to invalidate grouped assets, offering flexibility for complex cache management scenarios. | ||
|
|
||
| For additional information including how much you can purge please check out our [documentation](/cache/how-to/purge-cache/) and our [API Docs](https://developers.cloudflare.com/api/resources/cache/methods/purge/) | ||
nikitacano marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.