The edge terminates TLS for demo.cdn.test.rw with a Let's Encrypt certificate issued by FluxEdge through DNS-01, applies the zone's rules and answers from its cache when it can. Only misses and uncacheable requests continue to the origin.
| Content | Cache-Control from the origin |
|---|---|
| Pages | public, max-age=60, stale-while-revalidate=300 |
| /assets/, /images/ | public, max-age=31536000, immutable |
| /api/products.json | public, max-age=30 |
| /api/time | no-store |
curl -sI https://demo.cdn.test.rw/ | grep -i -E 'cache-status|age|cache-control'
Each resource on this page is requested again past your browser cache, so the answer below comes straight from the FluxEdge edge. FluxEdge; hit was served from the edge cache; fwd=… went to the origin.
| Resource | Status | Cache-Status | Age | Encoding | Protocol | Time | Cache-Control |
|---|
/api/time is marked no-store: every call reaches the origin.
FluxEdge Demo Store