/dynamic

Bypass case for comparison. force-dynamic means vinext emits no-store headers, so neither the outer ctx.cache nor the inner CacheHandler retains anything. The timestamp updates on every reload — every probe should produce a fresh render-id.

2026-10-11T09:01:04.539Z

Render ID: 100f4722-4f76-408b-a5f0-4c7d4f4fe32b

Probe /dynamic

Issues a no-store fetch against the route. The route embeds a fresh render-id into every server-rendered response — comparing it across probes is the most reliable way to tell whether SSR actually happened or a cache served the same bytes again. cf-cache-status is shown alongside as the outer Workers Cache verdict.

HTTP status
—
render-id
—
render-time
—
cf-cache-status
not set — running locally, or the runtime doesn't expose it
Age
—
Cache-Control
—
CDN-Cache-Control
—
Cache-Tag
—
cf-ray
—
Probed at
—