3 ms·
"By analogy: right now, you can tell your browser to change its User-Agent string to anything you want." You can also choose not to send this header. By defau
by 1vuio0pswjnm7 3y ago
"By analogy: right now, you can tell your browser to change its User-Agent string to anything you want."
You can also choose not to send this header. By default I do not send it. The RFCs do not require it^1 and very rarely do I find sites that do. When I do find such sites,^2 I just add them to the proxy config so that a UA is added on the way out. Almost invariably these sites will accept a made-up UA, so long as it is well-formed, which is interesting.^3 It suggests no one knows what new UA strings will appear.
The origin of changing the User-Agent header dates back to one of the earliest browsers, written in part by a well-known Silicon Valley VC.^4 It was always possible for the user to control HTTP headers such as UA and the designers knew it. Later in the "browser wars" Microsoft changed its UA header to match Mozilla's.^5
1.
https://towardsdatascience.com/the-user-agent-that-crazy-string-underpinning-a-bunch-of-analytics-86507ef632f0?gi=e30981d0139f https://towardsdatascience.com/the-user-agent-that-crazy-str...
2.
For example, www.federalregister.com and sec.gov.
3.
Many users want to "blend in" and use common strings so perhaps use of made-up strings remains largely untested.
4.
https://raw.githubusercontent.com/alandipert/ncsa-mosaic/master/mosaic-spoof-agents https://raw.githubusercontent.com/alandipert/ncsa-mosaic/mas...
5.
https://webaim.org/blog/user-agent-string-history/comment-page-1/ https://webaim.org/blog/user-agent-string-history/comment-pa...
https://humanwhocodes.com/blog/2010/01/12/history-of-the-user-agent-string/ https://humanwhocodes.com/blog/2010/01/12/history-of-the-use...
As for WEI, I'm inclined to think that the terms "abuse" and "fraud" in the spec may actually refer to ad fraud, including potential fraud by Google itself in marketing its ad services because it hides the true extent of ad fraud from its customers.
People who like to access the web with uncommon TCP/HTTP clients may not be a significant problem. There are no details given in the spec about this alleged "fraud"; perhaps that's intentional. Although by being vague in the spec, real humans that prefer not to use popular browsers may jump to conclusions.^6
It could be that we're on the cusp of exposing the true extent of ad fraud with respect to Google, and the ultimate unworkability of Google's core "business" (selling ad services). Perhaps Google believes its advertiser customers could begin to lose trust; maybe direct more ad spend to Apple.
6.
Some pre-spec discussion: https://groups.google.com/a/chromium.org/g/blink-dev/c/Ux5h_kGO22g/m/XCAIgPtxAQAJ https://groups.google.com/a/chromium.org/g/blink-dev/c/Ux5h_...