HOME | DD

Description
For a while, deviantART users would have around a 10-20% chance of randomly getting a "browser timed out" error (HTTP code 408) whenever they would try to do anything, anything at all, that involved contacting the web server. This could cause "cannot remove message" errors, "an error occurred while displaying this deviation", errors while previewing or posting comments, or errors while submitting art. Pretty much every function was affected. (Not just the "difi" calls!)

This error code doesn't even make sense, because a 408 error is what results when a web browser connects to a web server but then takes too long to actually request a web page. Even if a major network issue was causing the server to not receive web page requests correctly, there's supposed to be a delay, usually over a minute, before the server gives up waiting and throws the HTTP 408 error. In this case, there is no delay, therefore there is no timeout. Clearly, something else is wrong, and we're not even seeing the right error.

(I wonder if it's an issue with the load-balancing that dA is using...)

Description
For a while, deviantART users would have around a 10-20% chance of randomly getting a "browser timed out" error (HTTP code 408) whenever they would try to do anything, anything at all, that involved contacting the web server. This could cause "cannot remove message" errors, "an error occurred while displaying this deviation", errors while previewing or posting comments, or errors while submitting art. Pretty much every function was affected. (Not just the "difi" calls!)

This error code doesn't even make sense, because a 408 error is what results when a web browser connects to a web server but then takes too long to actually request a web page. Even if a major network issue was causing the server to not receive web page requests correctly, there's supposed to be a delay, usually over a minute, before the server gives up waiting and throws the HTTP 408 error. In this case, there is no delay, therefore there is no timeout. Clearly, something else is wrong, and we're not even seeing the right error.

(I wonder if it's an issue with the load-balancing that dA is using...)