Repository navigation
http.client: missing response headers when malformed header is part of the response #73631
Description
| BPO | 29445 |
|---|---|
| Nosy | @bitdancer, @gboudreau |
| Superseder |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = <Date 2017-02-04.20:58:55.818>
created_at = <Date 2017-02-04.20:29:53.415>
labels = ['type-bug', 'library']
title = 'http.client: missing response headers when malformed header is part of the response'
updated_at = <Date 2017-02-05.00:10:37.824>
user = 'https://github.com/gboudreau'bugs.python.org fields:
activity = <Date 2017-02-05.00:10:37.824>
actor = 'gboudreau'
assignee = 'none'
closed = True
closed_date = <Date 2017-02-04.20:58:55.818>
closer = 'r.david.murray'
components = ['Library (Lib)']
creation = <Date 2017-02-04.20:29:53.415>
creator = 'gboudreau'
dependencies = []
files = []
hgrepos = []
issue_num = 29445
keywords = []
message_count = 3.0
messages = ['286987', '286990', '287023']
nosy_count = 2.0
nosy_names = ['r.david.murray', 'gboudreau']
pr_nums = []
priority = 'normal'
resolution = 'duplicate'
stage = 'resolved'
status = 'closed'
superseder = '24363'
type = 'behavior'
url = 'https://bugs.python.org/issue29445'
versions = ['Python 3.5']
Activity
gboudreau commentedon Feb 4, 2017
Tested using urllib3 1.20
I'm pretty sure the problem is caused by an invalid HTTP header returned by the server:
It directly follows the Date response header, which is returned fine, but since no other response headers is returned, I think this broken header is breaking the HTTP response headers parser.
Of note: the
http.client.HTTPresponse.headersobject (HTTPMessage) shows all headers in_payload, but only theDateheader in_headers.Thus why I think this is a http.client issue, and not a urllib3 issue.
bitdancer commentedon Feb 4, 2017
This appears to be a duplicate of bpo-24363. Does the patch there fix the problem for you?
gboudreau commentedon Feb 5, 2017
Yes, indeed. The latest patch in 24363 resolves this issue.
Sorry for the duplicate.