You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/automatic-platform-optimization/get-started/verify-apo-works.mdx
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,23 @@ You can check whether or not APO is working by verifying APO headers are present
20
20
*`cf-edge-cache` | `cache, platform=wordpress`
21
21
* The `cf-edge-cache` headers confirms the WordPress plugin is installed and enabled.
22
22
23
+
In a terminal, use the following cURL. The header `'accept: text/html'` is important
24
+
25
+
```sh
26
+
curl -svo /dev/null -A "CF"'https://example.com/' -H 'accept: text/html'2>&1| grep 'cf-cache-status\|cf-edge\|cf-apo-via'
27
+
```
28
+
29
+
```sh output
30
+
< cf-cache-status: HIT
31
+
< cf-apo-via: cache
32
+
< cf-edge-cache: cache,platform=wordpress
33
+
```
34
+
35
+
As always, `cf-cache-status` displays if the asset hit the cache or was considered dynamic and served from the origin.
36
+
37
+
- The `cf-apo-via` header returns the APO status for the given request.
38
+
- The `cf-edge-cache` header means the WordPress plugin is installed and enabled.
39
+
23
40
## Verify the APO integration and WordPress integration work
24
41
25
42
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`
0 commit comments