Created on 2005-03-24 18:24 by yain, last changed 2009-04-05 18:44 by georg.brandl. This issue is now closed.
| Messages (4) | |||
|---|---|---|---|
| msg24774 - (view) | Author: Alexey Dvoychenkov (yain) | Date: 2005-03-24 18:24 | |
I'm not sure, if this is a bug, or intentional
behaviour, because on one hand RFC states that field
names for HTTP headers are case-insensitive, on the
other hand, it's not what server really returns to client.
Example:
print response.getheaders()
Yields this (output formatted a bit for clarity):
[('content-length', '5998'),
('accept-ranges', 'bytes'),
('last-modified', 'Sun, 30 Jan 2005 14:36:09 GMT'),
('connection', 'close'),
('etag', '"26d79-176e-41fcf0d9"'),
('date', 'Thu, 24 Mar 2005 18:14:07 GMT'),
('content-type', 'text/html')]
|
|||
| msg24775 - (view) | Author: Χρήστος Γεωργίου (Christos Georgiou) (tzot) * | Date: 2006-03-31 16:48 | |
Logged In: YES
user_id=539787
I believe that since HTTP Headers are not case sensitive,
this is not a bug.
Fixing the case to either lower-case or upper-case is
typical wherever data are case insensitive, and since Python
strings are case sensitive (in this case, the header name is
being used as a key to a dict), rfc822.py selects lower-case
('suitably canonicalized') to implement case insensitivity.
|
|||
| msg81450 - (view) | Author: Daniel Diniz (ajaksu2) | Date: 2009-02-09 07:11 | |
Superseder: issue 2275. |
|||
| msg85552 - (view) | Author: Georg Brandl (georg.brandl) *  |
Date: 2009-04-05 18:44 | |
Setting as superseder. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2009-04-05 18:44:39 | georg.brandl | set | status: open -> closed nosy: + georg.brandl messages: + msg85552 superseder: urllib/httplib header capitalization resolution: duplicate |
| 2009-02-09 07:11:56 | ajaksu2 | set | nosy:
+ ajaksu2 messages: + msg81450 |
| 2005-03-24 18:24:11 | yain | create | |