Could it be that this is an innocent mistake or a bug in the way that Google servers are sending HTTP. Chrome wouldn't be affected as it will be using SPDY for all Google services. As soon as Chrome switched back to the Firefox user agent it started using HTTP again and the same bug was found. Besides, this just doesn't make sense. If this was an attempt to make Firefox look bad then it's a dreadful one. This just se…
Firefox has SPDY support as of a version or two ago and uses SPDY on Google sites. I seem to that feature being on by default, even.
Is Google Burying Firefox With User Agent Strings?
31–40 of 72 posts
Re: Is Google Burying Firefox With User Agent Strings?
#32Re: Is Google Burying Firefox With User Agent Strings?
#33Does this mean that Google has given up completely on net neutrality? This is a very bad notion.
This article has nothing to do with net neutrality.
Re: Is Google Burying Firefox With User Agent Strings?
#34I've been pretty consistent in my Firefox use the past few years (probably >80% of my browsing is in Firefox), and I've never encountered this. Ever. I'm doing nearly all of this from OSX, with occasional browsing from FF and IE in a Windows VM or FF in a Linux VM. Perhaps this is more to do with a Linux string being picked up vs the Firefox aspect?
Re: Is Google Burying Firefox With User Agent Strings?
#35AFAIK, the chrome user agent switcher extension only changes the agent on a JS level. You can't change what is being sent to the server due to limitations in the extension API. This explains the Adsense warning because the server-side part of the framework used (gwt) is seeing a different user agent than what the client part is seeing. Granted, UA sniffing is bad practice on either client or server side, but if you d…
Re: Is Google Burying Firefox With User Agent Strings?
#36Ubuntu Firefox is Mozilla's Firefox coupled with arbitrary modifications by the Ubuntu developers. In principle I respect Ubuntu's position and desire to make things right by their users.
But in practice, having been in the same relationship as an author of Chrome for Linux I can tell you that it's always dangerous to have people who aren't browser developers make modifications to a browser. More than once the Ubuntu Chromium packager made changes to Chrome that were harmful for users because they didn't understand the consequences of their changes.
Re: Is Google Burying Firefox With User Agent Strings?
#37I never get any errors with Firefox on Windows, so this was a interesting article. I will have to try it out some more on my Linux. However, I got loads of "Connection was reset" when trying to use the powerbase site where this article was. Server seems very very slow or something is wrong with it.
I get errors with Firefox on Ubuntu, but never on Windows... Off topic: the pagination with blogs/news sites articles is total nonsense...
Re: Is Google Burying Firefox With User Agent Strings?
#38AFAIK, the chrome user agent switcher extension only changes the agent on a JS level. You can't change what is being sent to the server due to limitations in the extension API. This explains the Adsense warning because the server-side part of the framework used (gwt) is seeing a different user agent than what the client part is seeing. Granted, UA sniffing is bad practice on either client or server side, but if you d…
Re: Is Google Burying Firefox With User Agent Strings?
#39AFAIK, the chrome user agent switcher extension only changes the agent on a JS level. You can't change what is being sent to the server due to limitations in the extension API. This explains the Adsense warning because the server-side part of the framework used (gwt) is seeing a different user agent than what the client part is seeing. Granted, UA sniffing is bad practice on either client or server side, but if you d…