DS6 added the comment:
Whoa, I thought - no selection - would not change the set values, but I
guess I was wrong. I have no idea what I'm doing, sorry.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22467
DS6 added the comment:
Yeah, I was aware it's used for getting the request headers. It's strange that
it's not used for setting reply headers, though the casing really doesn't cause
any problems for the current implementation and really only affects fringe
cases like mine and that fellow
DS6 added the comment:
Oh... It showed that the message had been created but it really hadn't, because
I had the Status field set to - no selection - so now I've posted two
(three) times.
Good lord I am sickeningly bad at this. I'll just stop posting now
New submission from DS6:
Inconsistent casing, such as Content-type vs Content-Type, Content-Length
vs Content-length, while technically not breaking any RFC or other
HTTP-related rules (headers are case-insensitive, after all), can occasionally
cause problems when attempting to retrieve
DS6 added the comment:
Erp, *retrieve, and I meant copyfile, not sendfile. I'm tired.
Very quick reply, by the way.
I suppose I forgot to mention that _headers_buffer is for sending headers, not
for receiving them. As far as I can read, the received header information is
already case
