Yael Mintz

@FabienArcellier : Thanks for raising this issue. This patch is actually intentional, and the *not* is not accidental, since we're imitating `requests` redirect handling `[here](https://github.com/psf/requests/blob/main/requests/sessions.py#L197-L201)`: ``` if resp.status_code not in...

This is an interesting case. As I said, maybe we can keep the original res headers and then update the `cassette_request.headers` when [saving the recording](https://github.com/hiredscorelabs/cornell/blob/027eb90525f5583d98b10d973b70294a1fad38e4/cornell/vcr_settings.py#L20). Just need to figure out...

We're currently using aio_pika-9.4.2 and encountered the same issue with `connect_robust` in our production env, as @gaby. Once RabbitMQ becomes reachable again, the client is stuck on [await self.__connection_close_event.wait() ](https://github.com/mosquito/aio-pika/blob/master/aio_pika/robust_connection.py#L130).

@RomaLash : Actually I did try adding timeout to the `connect_robust` func, but this did not resolve my issue, in case of `Unexpected connection close from remote`. I assume this...