Bitpoke Geo Cache

Bitpoke Geo Cache is a powerful WordPress plugin designed to manage full-page caching with a CDN provider of your
choice. Currently, it supports BunnyCDN and Cloudflare, with more providers to be added in future updates.
This plugin helps improve your website’s performance by caching pages and serving them to your users from the nearest edge location.

Features:

• Full Page Caching: Cache your entire WordPress pages to improve load times.
• BunnyCDN Integration: Seamlessly integrate with BunnyCDN to manage your cache.
  • Edge Rules Management: Create and manage edge rules for caching policies.
  • Cache Purging: Purge specific URLs or cache zones as needed.
  • Settings Management: Easy-to-use settings interface for configuring your CDN provider.
• Cloudflare Integration: Seamlessly integrate with Cloudflare to manage your cache.
  • Cache Purging: Purge specific URLs or cache zones as needed.
  • Settings Management: Easy-to-use settings interface for configuring your CDN provider.

Usage

1. Go to the Bitpoke Geo Cache settings page.
2. Enter your BunnyCDN or Cloudflare API key and configure the cache zone.
3. Save the settings.
4. Synchronize predefined rules for common scenarios like skipping cache for authenticated users or setting long expiry for static resources.

Use Cases

• Improving Website Performance: By caching full pages, you can significantly reduce load times and server load, providing a better user experience.
• Geographical Distribution: Serve cached content from the nearest edge location to your users, reducing latency and improving load times.

1. Upload the plugin files to the /wp-content/plugins/bitpoke-geo-cache directory, or install the plugin directly through the WordPress plugins screen.
2. Activate the plugin through the Plugins screen in WordPress.
3. Navigate to the Bitpoke Geo Cache settings page to configure the plugin.

1. 

   Cache-control settings

2. 

   BunnyCDN settings

1.3.0

• Adds support for refetching purged articles
• Fixes an issue with determining the correct WordPress environment type.

1.2.1

• Start output buffering early to ensure Content-Length header is correctly set.

1.2.0

• Add support for setting Content-Length header.

1.1.1

• Added initial support for Cloudflare.
• This is a replublicated version of the 1.1.0 release, which was not properly tagged.

1.1.0

• Added initial support for Cloudflare.

1.0.0

• Initial release.