X-Hcdn-Upstream-Rt
Hostinger's CDN exposes origin response time in the
unofficial X-Hcdn-Upstream-Rt response header.
The value counts the seconds the edge spent waiting
on the upstream origin, the readout nginx
deployments know as $upstream_response_time. The
header travels beside
X-Hcdn-Cache-Status and
X-Hcdn-Request-ID on
Hostinger-hosted sites.
Usage
The value separates edge latency from origin
latency without any tooling on the server. A slow
page with a small X-Hcdn-Upstream-Rt spent its
time in transit or rendering on the client, while a
large value points at the origin: PHP execution,
database queries, or an overloaded plan. Reading
the value across a session profiles the origin the
same way X-Runtime and
X-Envoy-Upstream-Service-Time
do on other stacks.
The header appears on origin-served responses, so a
cache HIT in the companion status leaves nothing
to time.
Values
A decimal number of seconds with millisecond
precision. Observed values run from 0.009 on
fast origins to fractions of a second on rendered
WordPress pages.
Example
An origin that took 119 milliseconds to answer the edge on a cache miss.
X-Hcdn-Cache-Status: MISS
X-Hcdn-Upstream-Rt: 0.119
See also
- X-Hcdn-Cache-Status
- X-Hcdn-Request-ID
- X-Runtime
- X-Envoy-Upstream-Service-Time
- Server-Timing
- HTTP headers