Hollowport Lab / 500 Internal Server Error
h1-status-500
500 Internal Server Error
Responds 500 with a short known text body and a Retry-After header.
Run this test
Start capture, then open the test URL once.
https://hollowport.hevexa.net/lab/api/h1-status-500What the server actually does
| fact | value |
|---|---|
| status | 500 |
| Content-Type | text/plain; charset=utf-8 |
| Cache-Control | no-store |
| Retry-After | 10 |
| X-Lab-Test | h1-status-500 |
Response body, verbatim:
Deliberate 500 for this test. Nothing is actually broken.
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.
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.