ClientResponseError wrong error propagation?

[AlJohri]

In the client, I believe you catch ServerDisconnectedError and a couple other errors and propagate as ClientResponseError with __cause__ set as the real error. I think some other place in the code, I'm getting the raw "ServerDisconnectedError". Realized this since I wasn't catching the error.

Usually: ClientResponseError with cause ServerDisconnectedError
Sometimes: ServerDisconnectedError with cause ConnectionResetError

Is this by design?

[fafhrd91]

ServerDisconnectedError means server dropped connection before completing response.
in second case is second case you probably should get ConnectionResetError

exception handling needs some cleanup

[fafhrd91]

client does not catch ServerDisconnectedError anymore

[lock]

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.