HTTP Headers

Sec CH UA Full Version

HTTP Header

Deprecated: This feature is no longer recommended. Although some browsers may still support it, it might have been removed from current web standards, is in the process of being deprecated, or is maintained solely for backward compatibility. It’s advisable to refrain from using this feature and update existing code when possible. For guidance, refer to the compatibility table provided at the bottom of this page. Keep in mind that this feature may stop working at any time.

Secure context: This feature is accessible only within secure contexts, specifically in HTTPS connections, and supported browsers that implement this security model.

Note: This functionality is being replaced by the Sec-CH-UA-Full-Version-List header.

The HTTP Sec-CH-UA-Full-Version request header is a user agent client hint which provides the complete version string of the user agent.

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

Syntax

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

Directives

<version>

This directive accepts a string that specifies the complete version number, such as “96.0.4664.93”.

Example

Examples

A server can request the Sec-CH-UA-Full-Version header by including the Accept-CH header in its response to any client request. This is done by specifying the desired header name as a token in the Accept-CH header:

For example:

HTTP/1.1 200 OK
Accept-CH: Sec-CH-UA-Full-Version

The client has the option to provide this hint by including the Sec-CH-UA-Full-Version header in subsequent requests. An example of the client adding this header is:

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-Full-Version: "96.0.4664.110"
Sec-CH-UA-Platform: "Windows"

How to Modify Header using Requestly

Requestly is a handy Chrome extension that lets you modify HTTP headers, including the Sec-CH-UA-Full-Version header. This can help you test how websites or applications behave when they receive different browser version information, which is useful for debugging or development. Steps to Modify the Sec-CH-UA-Full-Version Header:

Install and open the Requestly Chrome extension. You can find it on the Chrome Web Store.
Create a new rule: Click on “Create Rule” and choose “Modify Headers” from the list of available rule types.
Add a new header modification:
- Under “Action”, select “Add” or “Override”.
- In the “Header Name” field, enter Sec-CH-UA-Full-Version.
- In the “Header Value” field, enter the desired full version string (e.g., 105.0.5195.125).
Set the URL condition: Specify the URL or pattern where this header change should apply (e.g., https://your-website.com/*).
Save the rule.

Once configured, Requestly will modify the Sec-CH-UA-Full-Version header on matching requests, helping you simulate different browser versions and check if your application handles them correctly.