Cloudflare

描述

此插件可以为您做什么

Automatic Platform Optimization (APO)

Speed up your WordPress site by up to 300% with Cloudflare’s Automatic Platform Optimization (APO) plugin. APO allows Cloudflare to serve your entire WordPress site from our edge network of over 250+ data centers worldwide ensuring fast & reliable performance for your visitors no matter where they are.

Optimizing your WordPress site with multiple plugins can be overwhelming. Take your WordPress site’s performance to the next level by switching to a single plugin for CDN, intelligent caching, and other key WordPress optimizations with Cloudflare (APO). Visit our announcement blog to learn more about APO.

What makes APO different from other caching plugins?

The key differentiating factor between Cloudflare APO and other traditional page caching and CDN solutions is its ability to directly cache static HTML at Cloudflare’s edge. Every other plugin and CDN will cache your static assets (images, javascript, CSS), but none help you cache the actual content on your site (the HTML) using a massive edge network like Cloudflare’s.

APO intelligently caches your HTML pages and will automatically purge content from the cache that you update, so users will always see the latest content without compromising the performance of pages that haven’t been recently updated

What you get with Cloudflare APO

APO is a $5 add-on with Cloudflare’s free plan and comes with an unlimited amount of subdomains. With APO you also get to leverage many of the other benefits of Cloudflare such as Free DNS, Free Automated SSL Certificates, Free DDoS Mitigation, and more. APO is free for all paid plan users so if you have Cloudflare Pro or Business already you can just turn it on. You can compare all our plans here.

Protect your WordPress site with Cloudflare’s Web Application Firewall (WAF)

Cloudflare’s WAF is available on all our paid plans and comes with built-in rulesets, specifically tailored to mitigate WordPress threats and vulnerabilities. These security rules are regularly updated by our team of experts. At the flip of a switch, you’ll have your WAF up and running without any difficult adjustments to your site. With over 26 million internet properties under our protection, you can sleep easy knowing Cloudflare has your back.

Additional features

  • 当 Cloudflare 的通用 SSL 被启用时,重写标头以防止重定向循环

  • 从插件本身更改 Cloudflare 设置,无需导航到 cloudflare.com 仪表盘。您可以更改缓存清除、安全级别、 Always Online 和图像优化等设置。

  • View analytics such as total visitors, bandwidth saved, and threats blocked

  • Support for HTTP2/Server Push

屏幕截图

安装

Prerequisite

Make sure your PHP version is 7.2 or higher.

Speed Up Your WordPress Site with Cloudflare APO

Getting Started

Setting up Cloudflare APO

If you’re currently utilizing Cloudflare’s free plan you can add APO to your plan for just $5/month. If you are on Cloudflare’s Pro Plan Cloudflare APO is already included in your subscription. We recommend you start with our APO developer documentation which includes all the information you need to get APO up and running.

How to check if APO is working
Using Uptrends you can verify if Cloudflare APO is working by checking to see if APO response headers are present. You can follow along in this video.

APO Support Resource can be found here

Get Started with Cloudflare SSL here

View our Cloudflare APO blog post here

常见问题

Do I need a Cloudflare account to use the plugin?

Yes, on install and activation of the plugin, first time users will be asked to enter their email address (used to sign-up for an account at cloudflare.com) and either an API Token or their API key. This is needed to support all the features offered by the plugin.

What settings are applied when I click “Apply Default Settings” in Cloudflare’s WordPress plugin?

You can review the recommended settings that are applied here.

What do I do if Cloudflare does not detect the WordPress plugin for use with APO (Automatic Platform Optimization)

APO works best when the WordPress plugin is used. We do not recommend using APO without the plugin installed. If you face issues with Cloudflare detecting the plugin then follow these steps:
1. Go to Cloudflare WordPress plugin
2. Disable APO in the card
3. Enable APO in the card (will set proper settings for APO feature)
4. Clear any server cache used via other plugins (WP Rocket being an example)
5. Verify that your origin starts serving response header “cf-edge-cache: cache,platform=wordpress”

You can read more about APO with WordPress here

Does the plugin work if I have Varnish enabled?

Yes, Cloudflare works with, and helps speed up your site even more, if you have Varnish enabled.

评价

Installed, used default settings, linked w/ our Cloudflare API token and all the necessary actions and settings appeared in wp-admin. Very nice for delegating access to these without needing to set up another Cloudflare account for additional users. Using this plugin improved our Google PageSpeed scores more than the previous caching plugin we were using, without any additional settings tweaks.
2021年8月7日
I am using aws lightsail instance. have to upgrade php7.4, so I move my site from one instance to another instance. everything is the same, ip address, host provider... The only change i have to make is to detach ip from old instance, attach the same ip to new instance. after that, it show server down when visiting site. Do I need to reconfigure my cloudflare ? Or just wait for up 24 hours ?
2021年6月2日
Hello, same problem after the update. I will switch to Stackpath. More reliable than Cloudflare. A service like Cloudflare should do a better job of maintaining your plugin. We pay Cloudflare Pro and get delivered crap that destroys the whole website? Horror club!
2021年5月25日
For those people who gives bad rating. They just don't know how to use this. If you don't know anything just use default setting, do not change anything. You will not have a problem.
阅读所有146条评价

贡献者及开发者

“Cloudflare” 是开源软件。 以下人员对此插件做出了贡献。

贡献者

将“Cloudflare”翻译成您的语言。

对开发感兴趣吗?

您可以浏览代码,查看SVN仓库,或通过RSS订阅开发日志

更新日志

4.7.0 – 2021-10-28

  • Merge cloudflare-plugin-backend into Cloudflare-WordPress repository

4.6.0 – 2021-10-11

  • Make frontend use native await/async
  • Purge cache on mobile if APO Cache By Device Type

4.5.1 – 2021-06-03

  • Rewrite PHP 8 bootstrap files for symfony/polyfill to be PHP 7 compatible

4.5.0 – 2021-06-02

  • Document unintuitive transition_post_status WP hook behavior
  • Only purge public taxonomies while clearing any empty values from the list
  • Better handling of cases where wp_get_attachment_image_src is false and not a usable array
  • Support activation of IDN domains
  • Improve development experience by shipping a Docker Compose file with more tooling and documentation

4.4.0 – 2021-03-23

  • Purge posts when transitioning to or from the ‘published’ state
  • Remove conditional logic for subdomain, allow to activate APO feature on the subdomain
  • Further work to autocorrect APO settings

4.3.0 – 2021-03-19

  • Sanitise sensitive HTTP header logs
  • Stop sending cfCRSFToken to remote API
  • Add warnings for incorrectly configured Automatic Platform Optimization
  • Purge posts that go from public to private
  • Purge pagination for first 3 pages

4.2.2 – 2021-03-08

  • Fix warning for file_get_contents of composer.json

4.2.1 – 2021-03-05

  • Deprecate REST dashboard analytics

4.2.0 – 2021-03-02

  • Allow configuration of Cloudflare credentials via environment variables
  • Prevent purging of cache before comments have been moderated
  • Remove unnecessary symfony/yaml dependency

4.1.0 – 2021-02-11

  • Removed development dependencies from vendor directory
  • Update CLOUDFLARE_MIN_PHP_VERSION to match the plugin requirements

4.0.0 – 2021-02-09

  • Drop support for PHP 5.6, 7.0 and 7.1

3.8.10 – 2021-01-29

  • Add Jacob to maintainers list

3.8.9 – 2021-01-14

  • Revert Add pagination purging

3.8.8 – 2021-01-13

  • Add pagination purging

3.8.7 – 2020-12-07

  • Purge taxonomy feed URLs
  • Fix changing APO settings (cf, wordpress, plugin) when running on subdomain
  • Fix setting hostname override

3.8.6 – 2020-11-19

  • Add subdomain support for APO card

3.8.5 – 2020-10-15

  • Added automatic purge cache on new comment

3.8.4 – 2020-10-13

  • Added composer’s type=wordpress-plugin for Bedrock users
  • Fixed typo in readme.txt
  • Fix modify header exception thrown during wp-cron
  1. Cloudflare Plugin= 3.8.3 – 2020-10-05 =
  • Fixed setting all APO values properly for correct dashboard rendering

3.8.2 – 2020-10-02

  • re-relase broken version, no changes

3.8.1 – 2020-10-02

  • Fixed typo in config.js(on) that resulted in warning #292
  • Check for array indicies are set before using #278

3.8.0 – 2020-10-01

  • Added APO support
  • Renamed Automatic Cache Management card to Auto Purge Content On Update

3.7.0 – 2020-09-25

  • Bump cloudflare-plugin-backend v2.3.0 and cloudflare-plugin-frontend v3.1.0 #283

3.6.0 – 2020-09-17

  • Bump cloudflare-plugin-backend #276

3.5.1 – 2020-07-02

Fixed

  • Fixed Cache Purges failing #266

3.5.0 – 2020-06-26

Fixed

  • Disable HTTP/2 Push on wp-admin pages #214
  • Fix PHP 7.4 notice #256

Added

  • Purge attachment URLs #208
  • Purge URLs on page/post update #206
  • Turn on IPv6 by default #229
  • Add constants for better control HTTP/2 Server Push #213
  • Allow custom actions for purge url and purge everything actions #212

3.4.1 – 2019-08-29

Fixed

  • Updated list of contributors.
  • Updated tested WordPress version to latest (5.2.2).

3.4.0 – 2019-08-29

Added

  • Added support for API Token authentication.

3.3.2 – 2017-12-12

Fixed

  • Bug in cf-ip-rewrite

Added

  • Added a new filter cloudflare_purge_by_url allowing users to have better control on automatically purged urls.

3.3.1 – 2017-6-29

Fixed

  • Potential bug by using $_GET.

3.3.0 – 2017-6-29

Added

  • Added a new Splash Screen
  • Added userConfig.js file allowing custom configurations.
  • Added logs in debug mode for Automatic Cache Purge.
  • Added logs for oversized Server Push HTTP headers.

Changed

  • Automatic Cache Purge now purges Autoptimize by everything rather than by URL.
  • Updated IP Ranges

Fixed

  • Bug where domains which had capital letters not working.
  • Bug where Automatic Cache Purge couldn’t purge front page.
  • Bug related to work with IWP.
  • Bug where if PHP is compiled with ipv6-disable flag, it crashed the site.

3.2.1 – 2017-3-14

Fixed

  • Bug where accounts which had more than 20 zones would not show up correctly.

3.2.0 – 2017-3-1

Added

  • Bypass Cache By Cookie functionality.
  • HTTP/2 Server Push functionality (disabled by default).

Changed

  • Lowered the plugin size.
  • Automatic Cache Management feature includes purging taxonomies.
  • Automatic Cache Management feature supports sites which use both HTTP and HTTPS.

Fixed

  • Admin bar disappearing from the plugin.
  • Bug where spinner was loading forever.
  • Bug where the backend errors where not being shown in the frontend.
  • Issues where IE11 was not working properly.

3.1.1 – 2016-11-17

Changed

  • Moved Admin Bar behind Automatic Cache Purge toggle.

3.1.0 – 2016-11-17

Added

  • Added ability to automatically purge cache when a post is published, edited or deleted. (Thanks to brandomeniconi and mike503)
  • Added ability to work with WordPress MU Domain Mapping plugin. (Thanks to brandomeniconi)

Changed

  • Changed the UI to look more like cloudflare.com dashboard.
  • Changed plugin description.
  • Disabled showing WordPress Admin Bar and Edit Post Link to avoid caching problems for users using HTML Caching.

Fixed

  • Fixed bug where require vendor folders was not working.
  • Fixed bug where static files were cached which caused issues updating the plugin.
  • Fixed dependencies which caused issues with PHP Compatibility Checker plugin.

3.0.6 – 2016-10-6

Added

  • Added ability to toggle Development Mode.

Fixed

  • Fixed bug where active zone dropdown was not working properly.

Changed

  • Compressed resources to lower plugin size.
  • Updated Cloudflare logo.

3.0.5 – 2016-09-28

Fixed

  • Fixed bug where refactored Flexible SSL fix was causing the settings page hook not to load.

3.0.4 – 2016-09-27

Added

  • Ability for users to toggle Automatic HTTPS Rewrites (enabled by default, solves for most mixed content errors).

Fixed

  • Fixed an issue where low PHP version where getting syntax error.
  • Fixed issue where some users using Flexible SSL where not able to login to wp-admin .
  • Fixed a bug where the active zone selector was not paginating through the whole zone list.
  • Fixed an issue where the setting for Image Optimization was being displayed incorrectly.
  • Fixed a bug in Analytics where the  Uniques Visitors data was not displaying accurately.

Changed

  • Compressed assets to lower plugin size.
  • Hooks loading logic refactored to make it more simple and readable.

3.0.3 – 2016-09-21

Fixed

  • Fixed an issue where some domains were being incorrectly propagated to the domain selector dropdown
  • Fixed an issue where the Web Application Firewall was accidentally triggering RFI Attack Rules
  • Fixed an issue where image optimization was not being enabled for Pro and higher Cloudflare plans

3.0.2 – 2016-09-16

Fixed

  • Disabled HTTP/2 Server Push which was leading to 520 and 502 errors for some websites.

3.0.1 – 2016-09-16

Fixed

  • Fixed HTTP/2 Server Push exceeding the header limit Cloudflare has which caused 520 errors.
  • Fixed warning message in HTTP/2 Server Push.

3.0.0 – 2016-09-15

Added

  • Added one-click application oft WordPress specific recommended settings
  • Added ability to purge the Cloudflare cache
  • Integrated with WordPress cache management to automatically clear the Cloudflare cache on updating site appearance
  • Added ability to change Cloudflare settings (Always Online mode, I’m Under Attack, Image Optimization, Security Level, Web Application Firewall)
  • Added Analytics showing Cached Requests, bandwidth used, unique visitors, threats blocked
  • Added Header rewrite to prevent a redirect loop when Cloudflare’s Universal SSL is enabled
  • Added HTTP/2 Server Push support
  • Added Support for PHP 5.3+

Removed

  • Removed HTTPS Protocol Rewriting
  • Removed submission of spam comments
  • Removed ability to toggle Development Mode On/Off

Changed

  • Updated user interface
  • Started to support WordPress 3.4+ instead of 2.8+ because we depend on the WordPress Options API