IE10 HTTP Keep‑Alive connections close after ~60 seconds of inactivity

Determine why IE10 terminates idle HTTP Keep‑Alive connections after roughly 60 seconds of inactivity when handling low‑traffic workloads and assess the resulting effect on connection‑setup overhead.

The idle timeout is not configurable via the browser interface, is regarded as an internal value that may differ across Windows updates or IE10 cumulative patches, and it is uncertain whether a server‑supplied Keep‑Alive: timeout header overrides this fallback or merely extends it.

• Does IE10 honor a server‑sent Keep‑Alive: timeout value longer than its internal 60‑second limit?
• If the internal timeout applies, how many additional TCP handshakes occur per hour for a workload that issues one request every five minutes?
• What is the estimated increase in network‑level cost caused by these extra handshakes compared with a truly persistent connection?