01 / YOUR BROWSER → EDGE
UnobservedMeasured by your browser’s Resource Timing API.
ONE APP. THREE HTTP VERSIONS.
HTTP, observed.
See how your browser reaches this app—and what Phoenix receives on the other side of the proxy.
H1TCPH2TCPH3QUIC
The connection path
Reading deployment…02 / CONNECTION INTO PHOENIX
UnobservedReported by the server’s connection adapter.
The browser-to-edge protocol and the connection received by Phoenix are measured separately.
SMALL REQUESTS. ACTUAL EVIDENCE.
Capability checks
Ready. The browser chooses the protocol; these checks do not force H1, H2, or H3.
| Check | Result | Browser → edge | Observation |
|---|---|---|---|
| Run the checks to collect a report for this deployment. | |||
A claim needs a connection.
An Alt-Svc header advertises H3. Only a negotiated h3 result confirms that a request used it. If timing data is unavailable, we show “unobserved.”
Check each version explicitly.
The command-line verifier requests H1, H2, and H3 separately and checks the negotiated version. H3 fallback never counts as a pass.
Open verification instructions ↗WebSockets are a separate check.
A successful Phoenix Channel echo verifies the socket path. It does not prove WebSockets over HTTP/3 or LiveView compatibility.