Aglet

Investigate webhook URL redirects and rewrites

Investigation should show whether a redirect changed the request or only exposed stale configuration. Build direct, one-hop, method-changing, invalid-target, and proxy-rewrite fixtures, then compare raw request and receipt. Keep sender behavior and network policy as separate boundaries in the endpoint stack.

Build a useful investigation brief

  1. Build redirect fixtures

    Create direct success, HTTPS redirect, path rewrite, method-changing redirect, invalid Location, and unapproved host cases. Record expected method, body, signature, and disposition before execution. Use synthetic events and destinations. Preserve the configured destination label.

  2. Trace every hop

    Capture configured URL, response status, Location, final request method, body length, headers, signature result, and receipt. Compare direct and redirected paths. Identify the first hop that loses method, bytes, identity, or trust.

  3. Vary one route condition

    Change only scheme, host, path, proxy, redirect status, or sender follow behavior. Compare receipt and effect. If the sender’s handling is not observable, document the missing evidence and require canonical configuration.

What to carry forward

The investigation is ready when redirect and direct fixtures show destination, request preservation, signature, and receipt differences. Deliver a canonical configuration or evidence request. Keep unapproved target behavior outside the safe conclusion. Keep the first changed request attribute visible. Keep the receipt boundary visible.

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