Hi,
>> Has anyone opened a bug against Chrome for this behavior (did a brief search >> and didn't see one)? I'd be interested in following it as this behavior will >> likely have an impact on an upcoming project I've got. >> >> -Patrick > > Hi Patrick, > > yes: > https://code.google.com/p/chromium/issues/detail?id=377581 Ah, thats great. I was trying to find a simple and reliable testcase yesterday, but the preconnect logic at least seems quite random. I was able to reproduce it, with 3 second gaps between the 408 + FIN and a subsequent GET, just not reliably. Anyway, whats "interesting" is that when the GET request after 408+FIN is trying to download a picture incorporated in the site (a 1px iamge in my case), the whole chrome tab hangs completely until you close it or Chrome detects that the process is stuck. It does not recover by itself. At least in that particular case the user attributes the issue to the browser instead of the server. I will do some more testing and update the bug report above with my findings. Regards, Lukas
