Crystal HTTP::Client and OAuth2 middleware integration for automatic 401 WWW-Authenticate handling
When a Crystal HTTP::Client receives a 401 Unauthorized response that includes a WWW‑Authenticate header after a successful TLS handshake, the standard library does not automatically retry the request with refreshed credentials. Developers must decide whether to propagate the error, invoke custom middleware, or implement a retry loop that extracts the challe