bpo-30160: Clarify intended usage of request handler stream by jugglinmike · Pull Request #1300 · python/cpython (original) (raw)

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation5 Commits1 Checks0 Files changed

Conversation

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters

[ Show hidden characters]({{ revealButtonHref }})

jugglinmike

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.

@jugglinmike

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.

@the-knights-who-say-ni

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!

@mention-bot

@jugglinmike

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?

@bitdancer

bitdancer

@bitdancer

I haven't gotten myself set up to do backports yet, so it would be great if you could generate those PRs.

zware pushed a commit to zware/cpython that referenced this pull request

May 24, 2017

@jugglinmike @zware

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)

zware pushed a commit to zware/cpython that referenced this pull request

May 24, 2017

@jugglinmike @zware

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)

zware added a commit that referenced this pull request

May 24, 2017

@zware

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)

zware added a commit that referenced this pull request

May 24, 2017

@zware

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)