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 r.david.murray
Recipients karlcow, orsenthil, r.david.murray
Date 2013-03-05.13:35:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1362490523.54.0.0594445318325.issue17355@psf.upfronthosting.co.za>
In-reply-to
Content
We are testing our http server.  It is not obviously inappropriate to test the full string.  Especially in the Line to Long case, where we are testing that our specific error message is produced.  If you wish to argue that we should emit the standard message and only put the specific info in the body of the response, that would be a design change, and then we should probably test for *that*, since it would be a change from current behavior.  Personally I find the more-specific information being in the response code message to be helpful, but I haven't done enough web programming lately for my opinion to count for much :)

So, I do not think this issue needs to be separate from issue 12921.  The tests should be fixed as part of the enhancement being advocated there (and I certainly agree it should be *possible* to control the two messages separately, regardless of what we choose to do by default).
History
Date User Action Args
2013-03-05 13:35:23r.david.murraysetrecipients: + r.david.murray, orsenthil, karlcow
2013-03-05 13:35:23r.david.murraysetmessageid: <1362490523.54.0.0594445318325.issue17355@psf.upfronthosting.co.za>
2013-03-05 13:35:23r.david.murraylinkissue17355 messages
2013-03-05 13:35:23r.david.murraycreate