Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(session): note the plain Retry-After the proxy relays

Yudhi Armyndharis0356b6445ee3
diff --git a/src/modules/session/session-proxy.interceptor.ts b/src/modules/session/session-proxy.interceptor.ts
index 8e4b41d2b..e4b324a6e 100644
--- a/src/modules/session/session-proxy.interceptor.ts
+++ b/src/modules/session/session-proxy.interceptor.ts
@@ -31,8 +31,9 @@ const RELAYED_RESPONSE_HEADERS = [
'content-disposition',
'x-content-type-options',
// Throttle answers come from the OWNER's counters, so the client must be told what the owner
- // said: without these a forwarded 429 arrives with no indication of when to retry. The suffixed
- // names are the ones the throttler actually sets (there is no bare Retry-After).
+ // said: without these a forwarded 429 arrives with no indication of when to retry.
+ // ProxyAwareThrottlerGuard sets the plain Retry-After that HTTP clients read; the base throttler
+ // adds the per-tier Retry-After-<name> and X-RateLimit-* headers. All of them are relayed.
'retry-after',
'retry-after-short',
'retry-after-medium',