RTT header
Limited availability
This feature is not Baseline because it does not work in some of the most widely-used browsers.
Experimental:This is anexperimental technology
Check theBrowser compatibility table carefully before using this in production.
The HTTPRTTrequest header is anetwork client hint which provides the approximate round trip time on the application layer, in milliseconds.The RTT hint includes server processing time, unlike transport layer RTT.
The RTT value is rounded to the nearest 25 milliseconds to preventfingerprinting, although there are many other mechanisms an attacker might use to obtain similar round-trip information.
The hint allows a server to choose what information is sent based on the network responsiveness/latency. For example, it might choose to send fewer resources.
Note:TheVary header is used in responses to indicate that a different resource is sent for every different value of the header (seeHTTP Caching Vary). Even ifRTT is used to configure what resources are sent consider omitting it in theVary header — it is likely to change often, which effectively makes the resource uncacheable.
| Header type | Request header,Client hint |
|---|---|
| Forbidden request header | No |
In this article
Syntax
RTT: <number>Directives
<number>The approximate round trip time in milliseconds, rounded to the nearest 25 milliseconds.
Examples
>Using RTT client hints
A server first needs to opt in to receive theRTT header by sending theAccept-CH response header containingRTT.
Accept-CH: RTTThen on subsequent requests the client might send anRTT header back:
RTT: 125Specifications
| Specification |
|---|
| Network Information API> # rtt-request-header-field> |
Browser compatibility
See also
Downlink,ECT,Save-Datanetwork client hintsAccept-CH- HTTP Caching: Vary and
Vary NetworkInformation.effectiveType- Improving user privacy and developer experience with User-Agent Client Hints (developer.chrome.com)