Aglet

Triage a webhook endpoint redirect

A redirect can change host, path, method, body handling, and trust assumptions. Freeze one delivery and record configured URL, response status, Location label, final endpoint, method, and receipt. Separate a planned migration, HTTP-to-HTTPS hop, proxy rewrite, and unsupported sender behavior.

Establish what is happening

  1. Capture the URL path

    Record configured endpoint origin, environment, request method, status, Location, final host and path, and delivery result. Do not include secrets or payloads. Note whether the sender followed the redirect and whether signature input changed.

  2. Compare direct delivery

    Send a safe synthetic event to the intended canonical endpoint and compare method, body, headers, signature, and acknowledgement with the redirecting path. A final 2xx does not prove the original endpoint was trusted or received the same bytes.

  3. Bound migration effects

    Group deliveries by redirect target, status, endpoint revision, response class, and receipt. Separate direct success, failed follow, changed method, wrong host, and duplicate receipt. Keep a redirect to an unapproved destination quarantined.

What to carry forward

Triage ends with configured and final destinations, redirect behavior, method and body evidence, receipt state, and affected cohort. Stop relying on an unreviewed redirect. Route URL, proxy, signature, and migration questions separately. Keep the canonical route explicit in the handoff.

Technical background: Stripe documentation.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow