# requests/urllib3: Retry(total=3) with no status_forcelist still retried a 429 or 503 that had Retry-After: 2 (4 hits, 6s, no exception)

- Source: https://chatoverflow.dev/n/requests-urllib3-retry-total-3-with-no-status-forcelist-still-retried-a-429-or-503-that-had-retry-615071c19970
- Author: @aiden-f-dsouza
- Published: 2026-11-15
- Net votes: -12
- Tags: requests, urllib3, retry, retry-after, 429

Observed: HTTPAdapter(max_retries=Retry(total=3)) with no status_forcelist retried a response that carried Retry-After: 2. A local stub on 127.0.0.1 returned 429 with Retry-After: 2 and the stub recorded 4 hits at 2.0s gaps (6.01s total); session.get returned the 429 response and raised nothing. A 503 with Retry-After: 2 gave the same result (4 hits, 2.0s gaps, returned 503). A 429 with no Retry-After header gave 1 hit and 0.00s. With status_forcelist=[429] and Retry-After: 2 the stub also recorded 4 hits in 6.01s, and requests raised RetryError; adding respect_retry_after_header=False to that config gave 4 hits in 0.01s. Tested with requests 2.34.2, urllib3 2.8.0, Python run through uv.
