OMG!!! this is so important in a charter invite to a clan i need to be in the accept button isnt working it doesnt take me anywhere it just stays in that message
I'm experiencing the same issue as others: GameSpot works fine in IE9 (and possibly other versions), but not Firefox or Chrome. For Firefox, modifying the network.http.accept-encoding property from about:config (removing gzip or changing the quality value to 0, eg, "gzip;q=0") fixes the issue entirely, but unfortunately, at least for me, causes Gmail to stop responding on load and complain about "taking too long." Having said that, IE9 loads Gmail just fine, so I'm not quite sure what's going on behind the scenes there. I wish there was a way to selectively set that network.http.accept-encoding property (eg, on a site basis). As others have pointed out, this type of behavior has happened in the past and the "outbreak" as it were is very random. I personally saw the issue using Apple's trailer site (http://trailers.apple.com) where the floating menus to play the trailers wouldn't show up because of truncated/corrupted javascript files being served. It would be interesting to find out what type of web server GameSpot uses and compare it to other sites that have been experiencing the issue. I want to say that Apple's site uses nginx, but I'm not positive.
I'm having the same problem with Firefox. Some videos will load fine, others wont. For instance I couldn't get the latest Arkham City trailer to load, kept saying I needed Flash 10. Yet if I used IE9 it worked fine. This only started about a week ago for me.
... For Firefox, modifying the network.http.accept-encoding property from about:config (removing gzip or changing the quality value to 0, eg, "gzip;q=0") fixes the issue entirely, but unfortunately, at least for me, causes Gmail to stop responding on load and complain about "taking too long." Having said that, IE9 loads Gmail just fine, so I'm not quite sure what's going on behind the scenes there. I wish there was a way to selectively set that network.http.accept-encoding property (eg, on a site basis)...dohcan
Other things might "work", but the thing to do with network.http.accept-encoding is to make it nothing; that is blank. That suppresses the relevant header entirely, which runs a better chance of working with more sites. That said, another option might be to just create another browser profile and put the change there; that profile would be specifically for temporary use with GS while the issue was ongoing. Although many sites have had issues with gzip encoding, I'm fairly sure this issue is specific to GS's server side caching and distribution mechanisms, which I think are proprietary. If we're in luck, this round of the issue may be starting to clear. If so, we'll probably start finding that out fairly soon.
Log in to comment