1. How this page was delivered
Raw headers of a GET to this page. Several values in x-served-by and x-cache mean the request crossed more than one cache layer (for example an edge cache and a shield cache).
| Header | Value |
|---|
| Check | Result |
|---|
2. Security headers added at the edge
These headers are not sent by the origin. They are added by the delivery layer.
| Header | Present |
|---|
3. Live watcher (purge, soft purge, origin failure)
Polls /data/version.json every second, skipping the browser cache.
Edit the version, upload it, purge, and watch when the new value appears.
If the origin goes down, watch whether answers keep coming from cache.
Not running.
| Time | HTTP | Cache | Age | Edge | Version | Latency |
|---|
Stops by itself after 10 minutes.
4. Traffic generator (for a live statistics dashboard)
Sends a fixed number of requests for the same small file, so the statistics screen has something to show. Bounded on purpose.
| Result | Value |
|---|
5. Compression and protocol
| Item | Value |
|---|
HTTP/3 usually shows up from the second visit, after the browser learns it is available.