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 karlcow
Recipients Paul.Upchurch, karlcow, orsenthil, python-dev
Date 2013-03-05.11:57:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The culprit is here

That an application or a person decides to send another message is ok. Designer choice. That the library is sending something optional as a test seems more uncomfortable.

The list of codes for 4xx is declared at

In HTTP, only the code is mandatory, the text is optional. But indeed you reveal a loophole, which means that someone might want to send a message for the body. That said, I still do not think it should lend in the header for reasons explained previously (serious breakage).

I will come up with something which is fixing the issue without breaking the existent. 

That said, do I open another bug for the test? The test should be fixed too. It should test 400 only. and not the full status-line.

The previous test is also an issue, testing 414. Because the prose in the spec is "URI Too Long" and not "HTTP/1.1 414 Request-URI Too Long"

Hmmm… I see all tests are like this. It should be fixed. Opening bug? Thought?
Date User Action Args
2013-03-05 11:57:57karlcowsetrecipients: + karlcow, orsenthil, python-dev, Paul.Upchurch
2013-03-05 11:57:57karlcowsetmessageid: <>
2013-03-05 11:57:57karlcowlinkissue12921 messages
2013-03-05 11:57:56karlcowcreate