Sec-CH-UA-Arch
Experimental: This is an experimental technology
Check the Browser compatibility table carefully before using this in production.
Secure context: This feature is available only in secure contexts (HTTPS), in some or all supporting browsers.
The Sec-CH-UA-Arch user agent client hint request header provides the user-agent's underlying CPU architecture, such as ARM or x86.
This might be used by a server, for example, to select and offer the correct binary format of an executable for a user to download.
| Header type | Request header, Client hint |
|---|---|
| Forbidden header name | yes |
Syntax
http
Sec-CH-UA-Arch: <arch>
Directives
<arch>-
A string indicating the underlying platform architecture, such as:
"x86","ARM","[arm64-v8a, armeabi-v7a, armeabi]".
Examples
A server requests the Sec-CH-UA-Arch header by including the Accept-CH in a response to some request from the client, using the name of the desired header as a token:
http
HTTP/1.1 200 OK
Accept-CH: Sec-CH-UA-Arch
The client may choose to provide the hint, and add the Sec-CH-UA-Arch header to subsequent requests.
For example, on a Windows X86 based computer, the client might add the header as shown:
http
GET /GET /my/page HTTP/1.1
Host: example.site
Sec-CH-UA: " Not A;Brand";v="99", "Chromium";v="96", "Google Chrome";v="96"
Sec-CH-UA-Mobile: ?0
Sec-CH-UA-Platform: "Windows"
Sec-CH-UA-Arch: "x86"
Note above that the low entropy headers are added to the request even though not specified in the server response.
Specifications
| Specification |
|---|
| User-Agent Client Hints # sec-ch-ua-arch |
Browser compatibility
BCD tables only load in the browser