Chromes keep-alive packets seem to block Apache from answering all requests from other clients. They do not appear in the access log nor in mod_status and the browsers keep waiting for an answer. This happens no matter if keep alive is enabled or disabled in Apache.
This only happens when the client is on another network, which seems to be related to a Chrome feature to keep the connection alive behind NAT gateways/firewalls. From browsers on the server machine, I can always access pages on Apache, even when clients on the the second network are blocked.
When I refresh the page in Chrome, sometimes the other requests are also answered.
Is this an Apache bug or a misconfiguration? Or can it be caused by a network configuration?
- Apache: 2.4.20 x64 VC14
- PHP: 7.0.5 TS x64 VC14
- Windows Server 2012 R2