3 ms·
AFAIK, 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 th
by pilif 15y ago
AFAIK, 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 do it and send content tailored for browser A and then see that, strangely, the client is actually browser B, then you are probably allowed to be confused and complain (better than failing in strange ways).
Also knowing that, it's unlikely that something on the server side is causing these connection reset issues because, as I just said: the server still sees a chrome user agent and producing a connection reset error (RST packet) requires connection level involvement (server or somewhere in between, but never the client browser, minus bugs).
In general: be very careful what error messages you see: the Adsense error is different from the gmail error which in turn is (likely) different from the connection reset issue.
Overall there is too much conflicting information to attribute malice or even just intent to Google here.
If I were in that users position, I'd check my firewall and/or proxy configuration (and try disabling HTTP pipelining if it's active in Firefox - it's disabled by default for a reason) as the problem is much more likely somewhere over there.
- rst 15y agoNote, however, that client-side UA sniffing could result in different requests getting sent to the server, from which subsequent wackiness might ensue...
- deleted 15y ago[deleted]
- simonbrown 15y agoIt's possible that it hasn't been updated yet, but extensions can now change the user agent sent to the server. http://code.google.com/chrome/extensions/webRequest.html http://code.google.com/chrome/extensions/webRequest.html
- Dylan16807 15y agoI would be surprised to have an internet company as big as google screw up pipelining. How likely is that?
- pilif 15y agoNot likely. But any proxy server in between might very well have. Including a transparent proxy on the ISPs side that the original poster knows nothing about
- mh- 15y agopretty likely. http://code.google.com/p/chromium/issues/detail?id=93409 http://code.google.com/p/chromium/issues/detail?id=93409
- eneveu 15y agoHaving used GWT in the past, the GWT error makes sense. When loading a GWT application, GWT first sniffs the user agent and locale. It then downloads a different javascript file, optimized for the given user agent and locale. For example, the javascript file served to a French user using Firefox will contain only French labels, and won't contain any code to deal with IE, Chrome... User agent sniffing is not always good practice, but, in this case, it results in a nice performance improvement :) You can even use it to have a "production" and a "debug" version of your app. By adding "?debug=true" to your URL, GWT would load the "debug" version, which could for example contain code to log information. https://developers.google.com/web-toolkit/doc/latest/FAQ_DebuggingAndCompiling https://developers.google.com/web-toolkit/doc/latest/FAQ_Deb...