Q:

408 Request Time-outs still continues

I'm frequently getting 408 Request Time-out errors  when browsing through Stack Overflow and Meta. I used to get this four or five times a day before, but now it has become very frequent. I've read this February 2011 question in which Kyle Brandt ♦ says:

We send our web logs to SQL so we can query them. It turns out that we have a bug that prevents 408s from being logged to SQL. [...] I will do more extensive research when our 408s are part of queryable logs (should be a week or two [...]).

My internet connection is somewhat stable and I haven't experienced this issue on other sites before. I don't think it's a browser-specific issue as it is reproducible on latest versions of Google Chrome and Firefox (on Ubuntu 13.10). However, it is specific to Stack Overflow and Meta. I'm unable to reproduce this on other SE sites.
Am I the only one facing this issue? Could it be something wrong with the regional CDN or something like that? Could someone please take a look at this issue? (not pointing hands)
This appears when I try to close-vote questions, too:

A:

As far as we can tell, the recent reports of this are due to a Chrome update.
A client side timeout seems to have stopped working, which created a small window in which a 408 sent to close a speculative connection by the server was unintentionally read as the response when attempting to use the connection to send a request.
So, you would potentially get a 408 when you sent a request between 15 and 16 seconds after your most recent request.
We've filed a bug report for Chrome, and implemented the workaround from HAProxy here.
Let me know if anyone's still observing regular 408 errors.

