408 Request Timeout

Good lord its been a long time since we posted here - far too busy I guess!

Amongst many other things, including Fryup Friday and having jarofgreen over at BlipCentral for a chat, today we managed to fix the cause of an odd bug many Chrome users have been reporting recently.

It turns out that a recent release of Chrome tries to speed things up by preemptively opening connections to sites before the user actually visits the next page. Nice idea, but unfortunately their implementation doesn't bother to check the connection state when a request is made over that connection.

In our case, our load-balancer (HAProxy) returns a 408 error after a connection has been opened but idle for 15 seconds. Chrome was opening a connection early, and then simply seeing and return the error response.

The bug has been filed but until its fixed here's the workaround - seems to do the job!