it would be useful to add one property $app
a value that can be filled from
$_SERVER['HTTP_X_REQUESTED_WITH']

even anonymous browsers can be identified by ID
example id https://play.google.com/store/apps/details?id=com.MaxSecureBrowse

useragent Mozilla/5.0 (Linux; Android 11; M2102J20SG Build/RKQ1.200826.002; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/90.0.4430.210 Mobile Safari/537.36

@sanchezzzhak If you have some time free, feel free to push some adjustments & tests to this branch. I'm not yet sure if I will find much time this week to go on with this....

@sanchezzzhak if $_SERVER['HTTP_X_REQUESTED_WITH'] is going to be added, I will suggest to be added also those:

$_SERVER['HTTP_DEVICE_STOCK_UA']
$_SERVER['HTTP_X_OPERAMINI_PHONE_UA']
$_SERVER['HTTP_X_UCBROWSER_UA']

Examples:

$_SERVER['HTTP_X_UCBROWSER_UA']
it looks interesting, it will be possible to make some hints of the screen size.
baidu, instagram - also contain something similar in useragent string

@sanchezzzhak I wouldn't start adding detection for screen sizes or similar for now. Guess there are also client hints for such stuff. Let's focus on bringing the client hints detection for the already detected stuff on the road. We can also consider parsing other header fields later...

@sanchezzzhak I have added improved some more code. Now also the browser should be detected with client hints if possible.
Maybe you can have a quick look if everything makes sense so far. If you have some more real test data for client hints, feel free to extend the clienthints.yml fixture.

Can you try the code exactly as it is here https://github.com/matomo-org/device-detector#usage and addheader('Accept-CH: Sec-CH-UA-Full-Version, Sec-CH-UA-Platform, Sec-CH-UA-Platform-Version, Sec-CH-UA-Model, Sec-CH-UA-Arc', true); at the top?

It should work.

<?php

header('Accept-CH: Sec-CH-UA-Full-Version, Sec-CH-UA-Platform, Sec-CH-UA-Platform-Version, Sec-CH-UA-Model, Sec-CH-UA-Arc', true);

use DeviceDetector\ClientHints;
use DeviceDetector\DeviceDetector;
use DeviceDetector\Parser\Device\AbstractDeviceParser;

require __DIR__ . "/../../vendor/autoload.php";

#AbstractDeviceParser::setVersionTruncation(AbstractDeviceParser::VERSION_TRUNCATION_NONE);

$userAgent = $_SERVER['HTTP_USER_AGENT'];
$clientHints = ClientHints::factory($_SERVER);
$dd = new DeviceDetector($userAgent, $clientHints);

$dd->parse();
$osInfo = $dd->getOs();
print_r($osInfo);


die();

Output: Array ( [name] => Windows [short_name] => WIN [version] => 10 [platform] => x64 [family] => Windows )
But why D:?

I'm pretty sure that's the same issue I also had when updating devicedetector.lw1.at:

DeviceDetector\ClientHints::factory looks at the $_SERVER variables, but they are named differently on my setup (nginx) than what the factory expects. Therefore it doesn't detect any of the client hints (you can also see it above in

  "clientHints": {
    "architecture": "",
    "bitness": "",
    "mobile": false,
    "model": "",
    "platform": "",
    "platformVersion": "",
    "uaFullVersion": "",
    "fullVersionList": {}
  },
```)

Interesting.
So as web server I use Apache2 with PHP8.1-FPM
Maybe this is the reason.

(And Cloudflare with Proxy)

I assume that's FPM-related.
I'll look into fixing that.

Sometimes, the platform version is not sent on the first request, it needs a refresh. At least this is how Chrome behaves for example.

I assume that's FPM-related. I'll look into fixing that.

i have disabled fpm, but it is still the same.

and the headers are set, so very weird.

It turns out @sgiehl was faster and already fixed the issue yesterdays:
eae6791

So make sure you are on the latest master branch.

And when in doubt do a var_dump($clientHints); and compare it with a var_dump($_SERVER); to see if the headers are correctly detected.

example with the last commit dev-master
https://phpsandbox.io/e/x/mfnke?layout=EditorPreview&defaultPath=%2F&theme=dark&showExplorer=no&openedFiles=
I don't have windows11 to check

It turns out @sgiehl was faster and already fixed the issue yesterdays: eae6791

So make sure you are on the latest master branch.

And when in doubt do a var_dump($clientHints); and compare it with a var_dump($_SERVER); to see if the headers are correctly detected.

It is recognized correctly, but still only gives out windows 10.
the current commit is pulled (the latest specified and saved in Composer.json )

object(DeviceDetector\ClientHints)#3 (8) {
--
  | ["architecture":protected]=>
  | string(0) ""
  | ["bitness":protected]=>
  | string(0) ""
  | ["mobile":protected]=>
  | bool(false)
  | ["model":protected]=>
  | string(2) """"
  | ["platform":protected]=>
  | string(9) ""Windows""
  | ["platformVersion":protected]=>
  | string(8) ""14.0.0""
  | ["uaFullVersion":protected]=>
  | string(14) ""99.0.4844.51""
  | ["fullVersionList":protected]=>
  | array(3) {
  | [0]=>
  | array(2) {
  | ["brand"]=>
  | string(12) " Not A;Brand"
  | ["version"]=>
  | string(2) "99"
  | }
  | [1]=>
  | array(2) {
  | ["brand"]=>
  | string(8) "Chromium"
  | ["version"]=>
  | string(2) "99"
  | }
  | [2]=>
  | array(2) {
  | ["brand"]=>
  | string(13) "Google Chrome"
  | ["version"]=>
  | string(2) "99"
  | }
  | }
  | }

example with the last commit dev-master https://phpsandbox.io/e/x/mfnke?layout=EditorPreview&defaultPath=%2F&theme=dark&showExplorer=no&openedFiles= I don't have windows11 to check

same.

@Nevercold Can you refresh phpsandbox page? Chrome sends the platform version on a second request. So this is the issue.

@Nevercold Can you refresh phpsandbox page? Chrome sends the platform version on a second request. So this is the issue.

I already have a few times.
Its the same.

On first request:

On second request (page refresh)

But also funny that it first says x64 and then x86.
Oh i see, first, he dont get the header.

But also funny that it first says x64 and then x86.

@sgiehl Can you check this when you have time? It should get the platform from bitness.

and in general, it does not work properly either. xD

and in general, it does not work properly either. xD

This is a browser issue. Headers aren't sent by the browser on the first request. Probably to avoid fingerprinting or cloaking on the first attempt.

and in general, it does not work properly either. xD

This is a browser issue. Headers aren't sent by the browser on the first request. Probably to avoid fingerprinting or cloaking on the first attempt.

Tricky! Private browsing or in general?

and in general, it does not work properly either. xD

This is a browser issue. Headers aren't sent by the browser on the first request. Probably to avoid fingerprinting or cloaking on the first attempt.

But I have reloaded it many times, so it should be there then.
The version he does get. (14.0.0.)

additional quotes are present, most likely, this does not allow determine the version

need fix

true, it takes "14.0.0" as version.
outputs at least $clientHints.

Fixed. #7050

Works now for me.

Client Hints are actually designed in a way that by default only some basic data (Sec-CH-UA, Sec-CH-UA-Mobile, Sec-CH-UA-Platform) is provided in the request headers. If the server requests more details by sending a header to the client the next request will contain all information. So the first request can never detect windows 11 actually, as the platform version isn't available.

Client Hints are actually designed in a way that by default only some basic data (Sec-CH-UA, Sec-CH-UA-Mobile, Sec-CH-UA-Platform) is provided in the request headers. If the server requests more details by sending a header to the client the next request will contain all information. So the first request can never detect windows 11 actually, as the platform version isn't available.

Thanks for the explanation :)

Hey - Thanks very much for this.
Just realized this isn't included in 5.0.5

Any estimate date of when will the next version be released? :)
Thank you very much.

We are currently preparing the implementation in Matomo to see if any further changes are required here. Once that is done we will release a new major version of device detector. Guess within one or two weeks