Hi,
> Well, here I'm seeing a standard 408 after 2 seconds which should match
> a timeout http-request of 2 seconds. Can you check if you don't have one ?
> Also, this observation from the logs doesn't seem consistent with your first
> claim that the 408 is immediate, here it's only after 2 seconds. Or again we
> are facing this bogus preconnect feature of Chrome. People complain all the
> time that not only it connects before you want to go to the site, but above
> all it displays the error that it receives without checking that it got an
> error prior to using the connection :-(
Wow, I didn't know it was that bad (showing the 408 in the browser).
I do however wonder:
- when we send the 408 an plain HTTP, we also send FIN,ACK
- when we send the 408 in HTTPS, we send a TLS close notification + FIN,ACK
So the TCP connection gets closed.
Why would we see this issue, when in fact we close properly?
I read the bug reports of Mozilla and chromium. While the Mozilla bug report
was very technical, the Chromium bug report is mostly about people complaining
about the preconnect feature and the consequences on server load, the 408
issue is hardly described.
Trying to reproduce this and get some more details ...
Regards,
Lukas
