[2.7] bpo-38330 Only set content-length when transfer-encoding is not present#16501
[2.7] bpo-38330 Only set content-length when transfer-encoding is not present#16501analoq wants to merge 1 commit into
Conversation
…nt per RFC7230 3.3.2
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). CLA MissingOur records indicate the following people have not signed the CLA: For legal reasons we need all the people listed to sign the CLA before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. If you have recently signed the CLA, please wait at least one business day You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
|
Thank you the pull request, but Python 2 has now reached end of life. |
RFC 7230 3.3.2 states "A sender MUST NOT send a Content-Length header field in any message that contains a Transfer-Encoding header field."
Includes both content-length and transfer-encoding. With this change:
Includes only transfer-encoding.
https://bugs.python.org/issue38330