Author demian.brecht
Recipients Guido, demian.brecht, martin.panter, orsenthil, r.david.murray
Date 2015-02-16.17:44:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <54E22C8F.2050701@gmail.com>
In-reply-to <1423879743.64.0.945548577855.issue22928@psf.upfronthosting.co.za>
Content
> Maybe join them with tabs rather than spaces then, since it was previously "\r\n\t". This way it is even closer to before.

After thinking about this a little more, I think I'd prefer to keep
spaces rather than tabs. The reason being is that, in my mind, now that
continuations have been made obsolete it's more natural to do something
like this:

putheader('Authorization', 'Bearer', 'my_token')

than

putheader('Authorization', 'Bearer my_token')

I realize it's a semantic change from previous behavior, but it seems to
me to be preferable given the latest RFCs. I'd think that at some point
in the future, we'd want to remove \x20 from the valid header value
range to entirely conform to the spec. This is the first step in
allowing for graceful deprecation.
Files
File name Uploaded
issue22928_1.patch demian.brecht, 2015-02-16.17:44:51
History
Date User Action Args
2015-02-16 17:44:55demian.brechtsetrecipients: + demian.brecht, orsenthil, r.david.murray, martin.panter, Guido
2015-02-16 17:44:54demian.brechtlinkissue22928 messages
2015-02-16 17:44:54demian.brechtcreate