Hacker News new | ask | show | jobs
by xoebus 5152 days ago
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 serves to make Google services look faulty as Firefox will still work for everything else. Because of this I doubt there is any malice behind this and it is just a bug.
1 comments
padraigm 5152 days ago
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.
link
mbrubeck 5152 days ago
SPDY isn't enabled by default until Firefox 13 (currently on the beta channel, scheduled for release in four weeks).
link
frio 5152 days ago
I wonder if that's what this is though: Ubuntu LTS having modified the FF build they run to use SPDY by default (given the LTS is supposed to be out for 5 years now, they may have chosen to jump the gun on that feature), and the SPDY support in the bundled FF isn't complete?
link