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 David.Pizzuto, r.david.murray
Date 2013-12-11.18:43:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1386787386.37.0.743445385754.issue19951@psf.upfronthosting.co.za>
In-reply-to
Content
I did some research on this for a previous issue, and every description of query strings I could find agreed that the format was '<name>=<value>'.  That is, that the '=' is not optional, even though some servers (note, *not* browsers, they just transmit or display the URI provided by the user or server) will accept parameters without the '=' and treat them as if they had one.

So I think this being rejected by strict_parsing is correct.  I'm closing this as invalid.

As for what strict_parsing, controls, you can check the source.  It looks like this and empty arguments (ie: &&) are the only things it controls.
History
Date User Action Args
2013-12-11 18:43:06r.david.murraysetrecipients: + r.david.murray, David.Pizzuto
2013-12-11 18:43:06r.david.murraysetmessageid: <1386787386.37.0.743445385754.issue19951@psf.upfronthosting.co.za>
2013-12-11 18:43:06r.david.murraylinkissue19951 messages
2013-12-11 18:43:06r.david.murraycreate