First-parties

By default, Chromium will send two headers (sec-ch-ua and sec-ch-ua-mobile). If additional headers are required then the server must request them by sending an appropriately populated 'Accept-CH' header to the client.

This tells the browser that we would like it to send the additional UA-CH HTTP headers in future requests.

Below, you can modify the headers that are being requested using 'Accept-CH' and see the effect this has in the UA-CH headers that are visible to the server.

Please note: as UA-CH is currently only available in Chromium browsers, this test page will not work if you are using Firefox or Internet Explorer for example.

What about third-parties?

By default, UA-CH headers will not be sent to third-parties, even if they are requested using the Accept-CH header.

For example, this page makes a call to a 'third-party' server at 51degrees.tv, which will respond with the UA-CH headers that it is able to see.

Initially, this will be nothing. Once the 'set delegate-ch' check boxes have been selected, the page at 51degrees.com will set the delegate-ch directive with values that allow the browser to send UA-CH headers to 51degrees.tv. Therefore, the next request for 51degrees.tv will include the Client Hints, which will then appear in the list of values visible to the third-party below.

Can I use the UA-CH JavaScript API?

There is a client-side JavaScript API for obtaining UA-CH values.

Unfortunately, the values returned by this API are formatted differently to the values that appear in the UA-CH HTTP headers. You can read more about this and how to convert the values to match the header format in our documentation.

Note that some of the values shown here are string representations of JSON objects (converted using JSON.stringify) rather than the true values.

Further reading

We've shown you how User-Agent Client Hints work and what values can be returned. If you want to learn more about the history of Client Hints, click on the links below:

1. Input your User-Agent Client Hints into our HTTP header parser to see what we detect the device as. You can also input the User-Agent for a more accurate device detection.

2. User-Agent Client Hints developer documentation

3. Explore the history with Learn Client Hints

4. More blogs on the topic of Client Hints