bpo-30160: Clarify intended usage of request handler stream #1300
Conversation
Although the library does not enforce compliance with the HTTP protocol, violations are not technically disallowed. Extend the stream's description to avoid suggesting that intentional protocol violations are not supported.
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA). Unfortunately our records indicate you have not signed the CLA. For legal reasons we need you to sign this before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. Thanks again to your contribution and we look forward to looking at it! |
|
@jugglinmike, thanks for your PR! By analyzing the history of the files in this pull request, we identified @bitdancer, @birkenfeld and @benjaminp to be potential reviewers. |
|
I signed the CLA immediately prior to submitting this pull request, but I understand that it may take up to 24 hours for that to be processed. Will any further action be necessary from me to re-validate this pull request? |
|
Not from you, no. |
|
I haven't gotten myself set up to do backports yet, so it would be great if you could generate those PRs. |
The library does not enforce compliance with the HTTP protocol, so violations are not technically disallowed. Extend the stream's description to avoid suggesting that intentional protocol violations are not supported. (cherry picked from commit a083c8e)
The library does not enforce compliance with the HTTP protocol, so violations are not technically disallowed. Extend the stream's description to avoid suggesting that intentional protocol violations are not supported. (cherry picked from commit a083c8e)
The library does not enforce compliance with the HTTP protocol, so violations are not technically disallowed. Extend the stream's description to avoid suggesting that intentional protocol violations are not supported. (cherry picked from commit a083c8e)
The library does not enforce compliance with the HTTP protocol, so violations are not technically disallowed. Extend the stream's description to avoid suggesting that intentional protocol violations are not supported. (cherry picked from commit a083c8e)
Although the library does not enforce compliance with the HTTP protocol,
violations are not technically disallowed. Extend the stream's
description to avoid suggesting that intentional protocol violations are
not supported.