This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author 신동원
Recipients 신동원
Date 2015-11-03.06:38:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1446532683.92.0.439898298366.issue25539@psf.upfronthosting.co.za>
In-reply-to
Content
I tried to login some website using requests session, but it failed because of parsing header.
This is header data of problem. It contains two line of continuous CRLF between the data.

Date: Mon, 02 Nov 2015 08:45:48 GMT
Server: Apache/2.2.20 (Unix) mod_ssl/2.2.20 OpenSSL/0.9.8e-fips-rhel5 DAV/2 PHP/5.2.16 mod_fastcgi/2.4.6
X-Powered-By: PHP/5.2.16
P3P: CP="NOI CURa ADMa DEVa TAIa OUR DELa BUS IND PHY ONL UNI COM NAV INT DEM PRE"

P3P : CP="ALL CURa ADMa DEVa TAIa OUR BUS IND PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA POL HEA PRE LOC OTC"
Set-Cookie: PHPSESSID=**; path=/
Set-Cookie: PHPSESSID=**; path=/
Content-Length: 81
Connection: close
Content-Type: text/html

function parse_headers in http.client, parsing exits when it meet CRLF. (https://hg.python.org/cpython/file/tip/Lib/http/client.py#l197)
Is it standard? Same code works well in python2, or even similar code in ruby.
History
Date User Action Args
2015-11-03 06:38:03신동원setrecipients: + 신동원
2015-11-03 06:38:03신동원setmessageid: <1446532683.92.0.439898298366.issue25539@psf.upfronthosting.co.za>
2015-11-03 06:38:03신동원linkissue25539 messages
2015-11-03 06:38:02신동원create