valid HTTP responses without a reason phrase considered malformed

[malaysf]

awsrequest.py is too restrictive in parsing 100 Continue responses and rejects valid responses that do not have a reason phrase.

The HTTP 1.1 RFC does not require the status line to contain a reason phrase, and defines the line as follows:

Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF
Reason-Phrase  = *<TEXT, excluding CR, LF>

awsrequest.py will reject valid responses such as: HTTP/1.1 100 \r\n\r\n or HTTP/1.1 500 \r\n\r\n

I will post a PR for this issue in a few minutes.

[swetashre]

@malaysf - Thank you for the post. Marking this as enhancement. It looks like the PR is approved and there is a comment in it. Let's track the progress of this issue under the linked PR.

[github-actions]

Greetings! It looks like this issue hasn’t been active in longer than one year. We encourage you to check if this is still an issue in the latest release. Because it has been longer than one year since the last update on this, and in the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment to prevent automatic closure, or if the issue is already closed, please feel free to reopen it.

[tim-finnigan]

Thanks for your patience here. I reopened this issue because it auto-closed and another issue (#3149) was recently opened asking for an update. The reason why this issue and the corresponding PR (#1932) will not be prioritized is because the requested behavior is outside of the standard behavior of Amazon S3.

[github-actions]

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.