| ||
Wed 2024-04-24
Tue 2024-04-23
Fri 2024-04-19
Thu 2024-04-18
Mon 2024-04-15
Butterick’s Practical Typography Sat 2024-04-13
Fri 2024-04-12
Wed 2024-04-10
Boy Meets Boy Meets Boys’ Love Tue 2024-04-09
Search
Archives
2023
12 11 10 09 08 07 06 05 04 03 02 01
2022
2021
2020
2019
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
One good site
MDN
Nelson Minar
Blog licensed under a Creative Commons License
|
Every time you fetch a web page, your browser sends a special
User-Agent string to the server telling it what software it's running.
It's defined
in RFC 2616:
This is for statistical purposes, the tracing of protocol violations, and automated recognition of user agents for the sake of tailoring responses to avoid particular user agent limitations.Fast forward to 2009, and here's the User-Agent string you get from Google's fancy new Chrome browser:
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/525.19
(KHTML, like Gecko) Chrome/1.0.154.48 Safari/525.19
It's like a browser salad! But the Google guys aren't doing anything
wrong, this boneheadedness has to be there in order to satisfy the
"automated recognition" part of the spec. Chrome's just a little ol'
chameleon.
|
|
