Up to Chrome 84, when the Request Desktop Site feature is enabled, the Desktop Safari UA is sent: Mozilla/5.0 (Macintosh Intel Mac OS X 10_10_4) Here's an example of the Chrome UA on iPhone: Mozilla/5.0 (iPhone CPU iPhone OS 10_3 like Mac OS X)ĪppleWebKit/602.1.50 (KHTML, like Gecko) CriOS/.75įor comparison, the Mobile Safari UA: Mozilla/5.0 (iPhone CPU iPhone OS 10_3 like Mac OS X)
The UA in Chrome for iOS is the same as the Mobile Safari user agent, with CriOS/ instead of Version/. Tablet pattern: 'Android' + 'Chrome/* (?!Mobile)'.Phone pattern: 'Android' + 'Chrome/* Mobile'.If you are parsing user agent strings using regular expressions, the following can be used to check against Chrome on Android phones and tablets: Here's an example of the Chrome user agent string on a Galaxy Nexus: Mozilla/5.0 (Linux Android 4.0.4 Galaxy Nexus Build/IMM76B) Phone UA: Mozilla/5.0 (Linux (KHTML, like Gecko) # Chrome for AndroidĬhrome for Android reports its UA in the following formats, depending on whether the device is a phone or a tablet. It's also available in the client through JavaScript using the erAgent call. Like all other browsers, Chrome for Android sends this information in the User-Agent HTTP header every time it makes a request to any site. When feature detection APIs are not available, use the UA to customize behavior or content to specific browser versions. With Privacy Sandbox, an origin trial is in progress for reduced User-Agent strings, designed to remove sensitive information which may be used for fingerprinting.Ī browser's User-Agent string (UA) helps identify which browser is being used, what version, and on which operating system.
0 kommentar(er)
