Open l7123222l7 opened 1 year ago
Hello and thanks for submitting this issue!
It indeed seems that the header-generator
gave you an inconsistent header set - while the user-agent
and the sec-ch-ua
headers refer to a MacOS device running Chrome, the sec-ch-ua-platform
says "Linux". The rest of the values seem to be in line.
Any additional information about your setup would be of great help - what version of header-generator
did you encounter this issue on? Every new patch (x.x.1, x.x.2
, ...) version of header-generator
comes with a new ML model for generating the HTTP headers. Because these models are generated automatically from real world collected values, it is possible that some of the inconsistencies might exist "in the wild" as well.
Either way, thank you for bringing this up - and looking forward to some extra info :)
Using the latest version 2.1.8 , this is my setup, Linux is not called in operatingSystems
browsers: [{
name: "chrome",
minVersion: 96
}, ],
devices: [
"mobile",
"desktop"
],
operatingSystems: [
"android",
"windows",
"macos",
"ios"
],
Also noticed that sec-ch-ua-platform in some macOS will show "" "macOS" is not displayed There are not many problems in testing Android IOS Windows Hope it helps you
sec-ch-ua-platform, sec-ch-ua, user-agent
Header mismatch when testing output Not sure if there is anything else
{ 'sec-ch-ua': '"Google Chrome";v="107", "Chromium";v="107", "Not=A?Brand";v="24"', 'sec-ch-ua-mobile': '?0', 'sec-ch-ua-platform': '"Linux"', 'upgrade-insecure-requests': '1', 'user-agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.0.0 Safari/537.36', accept: 'text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,/;q=0.8,application/signed-exchange;v=b3;q=0.9', 'sec-fetch-site': 'same-site', 'sec-fetch-mode': 'navigate', 'sec-fetch-user': '?1', 'sec-fetch-dest': 'document', 'accept-encoding': 'gzip, deflate, br', 'accept-language': 'en-US,en;q=0.9' }