Glossary
redirect
A 3xx response that tells a client to try another URL. OneLifeVibe never follows one when delivering a webhook.
Updated November 15, 2026
- Standard
- RFC 9110 (HTTP Semantics)
- Also called
3xx redirect
At OneLifeVibe
- A 404 or 410 disables the endpoint after three consecutive failures. Redirects are never followed, requests time out after 10 seconds, and only the first 512 bytes of your response are kept.
- Respond 2xx quickly; anything else is a failure. Retries follow after 30 s, 2 min, 10 min, 1 h and 6 h (6 attempts), then the delivery is dead. Redirects are never followed and requests time out after 10 s.
What it means
A redirect is an HTTP response in the 3xx range. RFC 9110 sets out the class: the server is saying the resource sits somewhere else, and the response carries a Location header with the URL to try instead. The client decides whether to take it.
The code tells you what kind of move it is. 301 and 308 signal a permanent move. 302 and 307 signal a temporary one. 307 and 308 keep the method and body on the second request, where 301 and 302 have historically let clients switch to GET. Browsers follow all of them silently, which is why a redirect can hide a dead route from anyone clicking through a site.
How it works
The client sends a request, gets a 3xx with a Location, then makes a second request to that URL. Each hop is another round trip, so a chain of redirects adds latency and multiplies the chances of something failing partway.
Following is a choice made by the client, not by the server that sends the 3xx. A browser follows. A command line tool may need a flag. A webhook sender can be set to refuse. The body on a 3xx is usually small, often a short HTML note pointing at the new address, and some clients ignore it entirely and read only the headers.
How OneLifeVibe uses it
OneLifeVibe never follows redirects when delivering webhooks. If your endpoint answers with a 3xx, the delivery counts as a failure. Point the endpoint at the address that actually handles the request, so the delivery lands there on the first hop.
A delivery succeeds on a 2xx and fails on anything else. Requests time out after 10 seconds, and only the first 512 bytes of your response are kept. After a failure, retries follow at 30 s, 2 min, 10 min, 1 h and 6 h, six attempts in total, then the delivery is dead. A 404 or 410 disables the endpoint after three consecutive failures.
The practical effect is that a redirect is never a fix for a moved webhook route. Where a browser would quietly absorb the extra hop, a delivery that gets a 3xx burns one of six attempts and moves the schedule forward.
Common mistakes
A common mistake is answering a webhook delivery with a 302 to send the sender somewhere else. Nothing follows it. The 3xx is logged as a failed attempt and the retry clock starts.
The other one is leaving a redirect in place after a route change and assuming receivers cope. Browsers cope. Plenty of servers and webhook senders do not, and OneLifeVibe is one of them. When a route moves, update the endpoint to the new address rather than parking a redirect in front of the old one.
Response time matters too. A handler that redirects and then does the real work on the second hop doubles the round trips inside a 10 second budget. Answer where the request lands, and keep the body short since only the first 512 bytes survive.
Questions
Does OneLifeVibe follow redirects on webhook deliveries?
No. A 3xx response counts as a failure, so the delivery enters the retry schedule: 30 s, 2 min, 10 min, 1 h and 6 h, six attempts, then it is dead. Send the 2xx from the URL you registered.
What happens if my webhook endpoint returns 404?
A 404 or 410 counts as a failure, and three consecutive failures disable the endpoint. Other failures, including a request that runs past the 10 second timeout, follow the same retry schedule.
See it working. The OneLifeVibe connector and Platform API put these pieces together.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.