Webhooks on BareProxy.com

BareProxy Adds a Webhook Inbox That Keeps Every Event Until the App Takes It

Sat, 31 Oct 2026 00:00:00 +0000

BareProxy 0.16.0 is out with a webhook inbox. It takes webhooks from Stripe, GitHub, Shopify and anything else that sends them, writes each one to disk, and then hands it to your app. If the app is down, the inbox keeps trying until the app is back.

Webhooks have a weak spot. The sender tries a few times and then gives up. An app that is being deployed, or has crashed, or is simply slow for ten minutes, loses whatever arrived in that window. Most teams find out when a customer asks why a paid invoice still shows as unpaid.

BareProxy Inbox and Drift Watcher Use Examples

Sat, 31 Oct 2026 00:00:00 +0000

Six short recipes for the two features that arrived in BareProxy 0.16.0, the webhook inbox and the drift watcher. Each one was run on the released Linux binary and the output below is copied from that run. The tested configs used a temporary folder, local ports and names under .test; the configs here use the usual paths and example names, and the output is left as it came, test names included. The webhooks were signed with test secrets in Stripe’s and GitHub’s formats, and the drift recipes ran against a local stand-in for DNS and HTTPS, because the machine had no public DNS.

BareProxy Killed in the Middle of Webhook Deliveries and No Event Was Lost

Sat, 31 Oct 2026 00:00:00 +0000

The worst moment for a webhook relay to die is after it has sent an event to the app and before the app has answered. The app may have charged the card or shipped the order. The relay can’t know. If it sends the event again, the app might do the work twice. If it doesn’t, the event might be lost.

The inbox handles this by marking every attempt on disk before it starts. This case kills BareProxy with SIGKILL in exactly that window and looks at what happens next. It ran on the released 0.16.0 binary for Linux, on 127.0.0.1, with Stripe-format webhooks signed by a test secret made for the run.

Duplicate Webhooks and a Bad Deploy Replayed With the BareProxy Inbox

Sat, 31 Oct 2026 00:00:00 +0000

Two things go wrong with webhooks that have nothing to do with the app being down. Senders send the same event more than once, on purpose, because they can’t tell whether you got it. And sometimes the app is up and answering, but answering wrong, because the last deploy broke the handler.

This case runs both through the inbox, after a quick check of what it does with forged signatures. It used the released 0.16.0 binary for Linux, on 127.0.0.1. The webhooks follow the real GitHub, Shopify and Stripe formats, each signed with a test secret made for the run.

How the BareProxy Inbox Kept Webhooks Through a One Minute App Deploy

Sat, 31 Oct 2026 00:00:00 +0000

Most webhook losses happen during deploys. The old process stops, the new one takes a minute to come up, and whatever Stripe or GitHub sent in that minute gets an error. The sender retries a few times on its own schedule and then gives up.

This case puts the webhook inbox between three senders and an app, stops the app for about a minute and keeps sending. It ran on the released BareProxy 0.16.0 binary for Linux. The app and the senders are small Python scripts on 127.0.0.1. The webhooks use the real formats and signatures of GitHub, Stripe and Shopify, signed with secrets made fresh for the run, and none of those services was contacted.