Question
Heroku Router Request Timeout Configuration
Ari River
0 reputation · 21 Jul 2025, 15:49 UTC
138.5K views0
Heroku Router Request Timeout Configuration
Goal: Allow specific long‑running endpoints to exceed the router’s 30‑second hard limit without triggering an H12 error.
Constraint: The router’s timeout is hard‑coded and cannot be changed via app config, add‑ons, or tier upgrades; client disconnects are not propagated as a cancellation signal.
Uncertainty: Whether any HTTP mechanism (e.g., 100 Continue, Upgrade, or persistent keep‑alive) can signal the router to wait longer, or if routing layer extensions exist for premium tiers.
- Is there a supported way to request a per‑route timeout override from the Heroku router?
- Can application‑level keep‑alive packets or HTTP 100 Continue be used to reset the router’s timer?
- Does any Heroku add‑on or experimental feature provide a configurable request timeout for HTTP traffic?
heroku