Webhook attempts fail with connection_reset when a reused keep-alive connection was closed by the destination

Aperta
  • Qualcosa non va?
#1,150 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 3 giorni

@Wali05 ci sta già lavorando.

Dal 29/10/2026.

  • #1184 di @Wali05 — aperta

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
67/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go
Ambito
backend, networking

Direzione di ricerca

Start in the webhook client where Go's http.Transport reuses idle connections and delivery attempts handle connection_reset. Trace how a failed attempt affects logging and the retry budget, then exercise the webhook delivery path with a destination that closes a reused connection. Done means the delivery is retried on a fresh connection without recording a failed attempt or consuming destination retry budget.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

The webhook client keeps idle connections open and reuses them for later deliveries to the same destination (Go's default http.Transport, 90 s idle timeout). This saves a TCP and TLS handshake per delivery.

Sometimes the destination, or a proxy/CDN in front of it, has already closed an idle connection on its side. The next delivery is written to that connection and reset a few milliseconds later, before any response. Go doesn't retry it on a fresh connection, because a POST without an Idempotency-Key header isn't considered safe to replay. Outpost records it as a failed attempt with connection_reset.

For the user this shows up as:

  • a failed attempt in the attempt log, though the endpoint is healthy
  • delivery delayed by one retry interval
  • one retry used from the destination's retry budget

Usually the next scheduled retry opens a new connection and succeeds, so the event is still delivered. If it happens on the last attempt of the retry schedule, Outpost gives up on the event even though the endpoint was healthy.

The error is transient and comes from our connection reuse rather than from the destination, so it shouldn't need to surface as a failed attempt or count against the retry budget.

Lingua principale
Go
Stelle
1.1k
Fork
70
Merge medio
3g 9h
PR unite (30g)
34

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di hookdeck/outpost

Tutte le issue di hookdeck/outpost

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.