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
Currently, aiohttp.client does not support recent HTTP redirect code 308 Permanent Redirect, defined in RFC 7538. It is simply a permanent version of already handled 307 redirect, or a legacy-free version of 301 redirect.
I would also argue that normalize_path_middleware default redirect class should be changed to HTTPPermanentRedirect, as it is currently very surprising that a user agent will likely retry a POST request as a GET one after receiving a 301 redirect from path normalization, but that is probably a breaking API change.
Still, supporting 308 in aiohttp.client would allow normalize_path_middleware to be used with POST requests in asyncio <-> asyncio communication by specifying redirect 308 manually.
The text was updated successfully, but these errors were encountered:
Currently,
aiohttp.client
does not support recent HTTP redirect code 308 Permanent Redirect, defined in RFC 7538. It is simply a permanent version of already handled 307 redirect, or a legacy-free version of 301 redirect.I would also argue that
normalize_path_middleware
default redirect class should be changed toHTTPPermanentRedirect
, as it is currently very surprising that a user agent will likely retry a POST request as a GET one after receiving a 301 redirect from path normalization, but that is probably a breaking API change.Still, supporting 308 in
aiohttp.client
would allownormalize_path_middleware
to be used with POST requests in asyncio <-> asyncio communication by specifying redirect 308 manually.The text was updated successfully, but these errors were encountered: