Repository navigation
Server: honor HTTP-date Retry-After values for webhooks #525
Description
Problem
Webhook retries honor numeric Retry-After values, but ignore valid HTTP-date values and use the exponential backoff instead. Receivers using date-form values can therefore be retried earlier than requested.
Expected behavior
Parse both delay-seconds and HTTP-date values. For a date, calculate the delay from the current time and preserve the existing 10-second maximum. Missing or invalid values should continue using the existing exponential backoff.
Tests
- Numeric and HTTP-date values produce the expected delays.
- Past dates, invalid values, and missing headers follow the documented fallback behavior.
- Delays remain capped at 10 seconds.
Document the supported formats and add an appropriate @chatcops/server changeset.
Activity
piyusshhjangid commentedon Oct 31, 2026
Hi @anurag629, if this issue makes sense, could you please add the appropriate label and assign it to me? I’d be happy to work on it after #524 0r #504 is merged.
anurag629 commentedon Oct 31, 2026
@piyusshhjangid confirmed:
parseRetryAfter()(packages/server/src/webhook.ts:164-169) only reads delay-seconds, so an HTTP date likeWed, 21 Oct 2026 07:28:00 GMTfalls through to the backoff.Date.parseon the header, minus now, clamped toMAX_RETRY_AFTER_MS, with a past date counting as 0, is the fix. It's held for you: you're at two with #477 and #519, so say here when one of them is merged. Do it after #524, since both touch the retry loop.anurag629 commentedon Oct 31, 2026
@piyusshhjangid #524 and #504 are in, so this is yours now.