Sec-CH-UA-Full-Version header

Deprecated: This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see thecompatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.

Secure context: This feature is available only insecure contexts (HTTPS), in some or allsupporting browsers.

Note:This is being replaced by theSec-CH-UA-Full-Version-List.

The HTTPSec-CH-UA-Full-Versionrequest header is auser agent client hint which provides the user-agent's full version string.

Header type	Request header,Client hint
Forbidden request header	Yes (`Sec-` prefix)

Syntax

http

Sec-CH-UA-Full-Version: <version>

Directives

<version>: A string containing the full version number, like "96.0.4664.93".

Examples

Using Sec-CH-UA-Full-Version

A server requests theSec-CH-UA-Full-Version header by including theAccept-CH in aresponse to any request from the client, using the name of the desired header as a token:

http

HTTP/1.1 200 OKAccept-CH: Sec-CH-UA-Full-Version

The client may choose to provide the hint, and add theSec-CH-UA-Full-Version header to subsequent requests.For example, the client might add the header as shown:

http

GET /my/page HTTP/1.1Host: example.siteSec-CH-UA: " Not A;Brand";v="99", "Chromium";v="96", "Google Chrome";v="96"Sec-CH-UA-Mobile: ?0Sec-CH-UA-Full-Version: "96.0.4664.110"Sec-CH-UA-Platform: "Windows"