unkinben 1476120c7b fix: use a timeout-configured HTTP client for upstream requests ...

All upstream GET/HEAD and bearer-token requests used http.DefaultClient,
which has no timeouts, so a slow or wedged upstream could pin a goroutine
and connection indefinitely. Introduce a shared upstreamClient with
dial, TLS-handshake and response-header timeouts (no overall Client
timeout, so large artifact bodies can still stream, bounded by the
request context).

Refs #67

2026-07-02 00:26:36 +10:00

..

circuit_test.go

Feat/v3 go rewrite (#47)

2026-06-07 19:30:35 +10:00

circuit.go

Feat/v3 go rewrite (#47)

2026-06-07 19:30:35 +10:00

classifier_test.go

Feat/v3 go rewrite (#47)

2026-06-07 19:30:35 +10:00

classifier.go

Feat/v3 go rewrite (#47)

2026-06-07 19:30:35 +10:00

engine.go

fix: use a timeout-configured HTTP client for upstream requests

2026-07-02 00:26:36 +10:00

httpclient.go

fix: use a timeout-configured HTTP client for upstream requests

2026-07-02 00:26:36 +10:00