You can check whether or not APO is working by verifying APO headers are present. When APO is working, three headers are present: CF-Cache-Status, cf-apo-via, cf-edge-cache.
- Visit Uptrends.com ↗︎.
- In the text field, enter the URL for your WordPress homepage including the
https://www.. - Select Start test. The Response Headers table displays.
- Locate the three header responses and their description. APO is working correctly when the headers exactly match the headers below.
CF-Cache-Status|HIT- The
cf-cache-statusheader displays if the asset is served from the cache or was considered dynamic and served from the origin.
- The
cf-apo-via|tcache- The
cf-apo-viaheader returns the APO status for the given request.
- The
cf-edge-cache|cache, platform=wordpress- The
cf-edge-cacheheaders confirms the WordPress plugin is installed and enabled.
- The
In a terminal, use the following cURL. Include the 'accept: text/html' header so the request is treated as a browser-like HTML request. This makes the test result deterministic. APO can also cache requests that omit the header, depending on the URL path. For more information, refer to FAQ on cf-cache-status results.
curl -svo /dev/null -A "CF" 'https://example.com/' -H 'accept: text/html' 2>&1 | grep 'cf-cache-status\|cf-edge\|cf-apo-via'< cf-cache-status: HIT
< cf-apo-via: cache
< cf-edge-cache: cache,platform=wordpressAs always, cf-cache-status displays if the asset hit the cache or was considered dynamic and served from the origin.
cf-apo-via|tcache- The
cf-apo-viaheader returns the APO status for the given request.
- The
cf-edge-cache|cache, platform=wordpress- The
cf-edge-cacheheaders confirms the WordPress plugin is installed and enabled.
- The
Open your WordPress site and publish a change. When the integration is working, the page is cached with cf-cache-status: HIT and cf-apo-via: tcache.