Timeout Design Patterns: Connection vs Read Timeouts

One of the most dangerous defaults in software engineering is that standard HTTP client libraries have infinite timeouts by default:

• Python's standard urllib / unconfigured requests.get() blocks indefinitely.
• Java's HttpURLConnection defaults to infinite connection and read timeouts.
• Go's http.DefaultClient has no timeout configured (Timeout: 0).
• Node.js http.request socket timeout defaults to infinity unless explicitly set.

What Happens in Production with Infinite Timeouts:

When a single downstream backend server freezes (due to a deadlocked database query, unhandled thread lock, or kernel packet drop), upstream client sockets stay open indefinitely. Within minutes, every worker thread in the client application becomes permanently blocked waiting for responses that will never arrive. The entire client fleet runs out of threads, file descriptors, and sockets, collapsing the application.