Thursday, July 26, 2012

Why does Slashdot hate Chrome?

I tried to navigate Slashdot with Google's Chrome browser, and this is what I get for every article:
It's the classic 500 "internal server error":
Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, admin@slashdot.org and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log.
What's interesting is that this suggests a script on Slashdot itself did not finish executing, presumably because one of the variables it got from the browser was insufficient or unexpected. Is anyone else having this madness? I don't normally use Chrome or Firefox, but Firefox seems to handle these same pages just fine.

0 Comments:

Post a Comment

Subvert the dominant paradigm, don't be a solipsist.

Subscribe to Post Comments [Atom]

<< Home