You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Redirect handling parity with httpx: per-request follow_redirects and event hooks #603
In httpx (and httpx2), follow_redirects is a client default that each request can override: request(), stream(), and send() all take follow_redirects. The client also takes event_hooks, which run for every request in a redirect chain, so a caller can adjust headers on the way.
impit has follow_redirects and max_redirects only on Client / AsyncClient, and no hooks. Could request() and stream() take follow_redirects like httpx does? Hooks or a max_redirects override would be nice too, but per-request follow_redirects is the main gap.
changed the title [-]Per-request follow_redirects, or dropping custom headers on cross-origin redirects[/-][+]Per-request follow_redirects, as in httpx[/+]on Oct 30, 2026
changed the title [-]Per-request follow_redirects, as in httpx[/-][+]Redirect handling parity with httpx: per-request follow_redirects and event hooks[/+]on Oct 30, 2026
Activity
[-]Per-request follow_redirects, or dropping custom headers on cross-origin redirects[/-][+]Per-request follow_redirects, as in httpx[/+][-]Per-request follow_redirects, as in httpx[/-][+]Redirect handling parity with httpx: per-request follow_redirects and event hooks[/+]feat(python): add per-request redirect options (#614)