News for hackers. Stuff that matters.
Re:The long and sordid history of the user-agent HTTP header... by mbrubeck on Sunday July 15, 2012 @12:27PM (#4247281)
When we actually do this, it does not necessarily convince publishers to fix things. For example: for several months Mozilla has been testing one tiny reduction to the User-Agent string in Firefox Nightly builds (replacing "Gecko/20100101" with "Gecko/16.0"). Zillow.com is the highest-profile site that is broken by this change, and after five months they still haven't even responded to any of our attempts to contact them: http://bugzil.la/754680

It's much better to resist adding things to the UA in the first place, since removing anything later on is a huge pain and inevitably breaks things for users. Mozilla has managed to keep the UA relatively minimal (and successfully reduced it a bit in Firefox 4): https://developer.mozilla.org/en/Gecko_user_agent_string_ref...

Re:The long and sordid history of the user-agent HTTP header... by jonburs on Sunday July 15, 2012 @11:35PM (#4249196)
I forwarded this on to one of my zillow friends (I used to work there) -- he'll look into it.
Re:The long and sordid history of the user-agent HTTP header... by mbrubeck on Monday July 16, 2012 @05:53PM (#4252887)
Thanks! It looks like it worked. I had even tried contacting @zillow on Twitter, but I hadn't quite reached the point of emailing random engineers. :)
Re:The long and sordid history of the user-agent HTTP header... by decklin on Sunday July 15, 2012 @08:04PM (#4248660)
Interesting! I wasn't sure if anything like this had been done. I guess it shows that there's nothing good that can come from change here.