Hollowport Lab / Deliberately slow response (~2.4 s)

h1-slow-2400ms

Deliberately slow response (~2.4 s)

Holds the response for ~2400 ms after receiving the request, then responds 200 with a short known body. The delay is a fixed server-side wait, not network variance.

CLASS 2 — proves status / body / header semantics only. Does not prove origin transport, ALPN, or HTTP/2 multiplexing. This request terminates at a CDN edge, not at an origin server the Lab controls.

Run this test

Start capture, then open the test URL and wait for it to finish (about 2.4 seconds).

https://hollowport.hevexa.net/lab/api/h1-slow-2400ms

What the server actually does

factvalue
status200
Content-Typetext/plain; charset=utf-8
Cache-Controlno-store
X-Lab-Testh1-slow-2400ms
X-Lab-Intended-Delay-Ms2400

Response body, verbatim:

Slow but deliberate. The server waited ~2.4 s before sending this.

intendedDelayMs: 2400
delaySource: "fixed server-side wait before first byte"

About intermediaries. This request also passes through Cloudflare's edge, which adds headers of its own — cf-ray, server: cloudflare, sometimes cf-cache-status. Those belong to the intermediary, not the origin. Seeing them in your observer's capture is expected; they are not a mismatch against the ground truth above. The Lab is teaching three separate things: what the authoritative server did, what your observer actually saw, and what an intermediary added or changed along the way.

Classify what your observer showed

For each fact above, pick the category that matches what your traffic tool actually displayed. This stays on your device — nothing is submitted.

Captured & represented — The observer got this right — captured, retained, and shown correctly.
Captured, not shown — The observer has the data but exposes no field or view for it.
Partial / lossy — Present but incomplete — e.g. a body kept only up to a cap, headers reconstructed rather than verbatim.
Not observed — Nothing in the observer's evidence corresponds to this.
Mismatch — The observer's value contradicts what the server actually did.
Unknown — Not enough visible in the observer to decide either way.

Worth noting

  • Timing an observer reports is only as precise as its own clocks and where in the exchange it measures — treat a value a few tens of ms off from 2400 as agreement, not a mismatch.

The ground truth above is what the server does, independent of any observer. If your tool showed less than this, that is a finding — not a problem with the test.