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
Thanks for bringing this issue back to our attention. It looks like the original issue (#1931) auto-closed due to lack of activity. I can reopen that one to continue tracking and bring it up with the team for discussion. It looks like a PR was submitted for this (#1932) and was approved but the team decided to close it and its not clear why. Please refer to that original issue for updates going forward.
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
Describe the bug
Related Issue
I think botocore still ignore "HTTP/1.1 100" that does not contain reason-phrase content (Continue).
Is there any reason?
Expected Behavior
When a s3 server returns 100 Status code without reason phrase (Continue),
boto3 should work without errors.
Current Behavior
boto3 raises errors ( botocore.exceptions.ConnectionClosedError: Connection was closed before we received a valid response from endpoint URL )
Reproduction Steps
Possible Solution
change one of the following functions in awsrequest.py (https://github.com/boto/botocore/blob/develop/botocore/awsrequest.py)
Additional Information/Context
No response
SDK version used
Version: 1.34.73
Environment details (OS name and version, etc.)
Redhat 7.9
The text was updated successfully, but these errors were encountered: