Actually, I've been thinking about this issue, read again the bug report and current thread, and I'd like to re-open the discussion, if you don't mind.
> request.POST is a > special-case for a request body submitted with the > "x-www-form-urlencoded" or "multipart/form-data" content types. This is > common for POST because these content types are used by web browsers to > submit HTML forms. So, don't you think the `request.POST` variable should be processed for every request with the "x-www-form-urlencoded" content type, whatever the http verb is? Even if form urlencoded web services are not common, it is still the easiest way to send a request to a web server. Here's a few examples. 1) Using curl http://pastie.org/2979317 2) Using httplib2 http://pastie.org/2979319 I understand that browsers should not send PUT requests, and I agree that if the requests comes as json or xml, the parsing is up to the developer. But in the case of an urlencoded request, why would django make PUT requests' processing harder, forcing the user to parse the querystring by himself (which is not really well documented, as far as I know)? If there is a valid explanation, I would be happy to hear it. Otherwise, I could provide a patch to solve the issue. Let me know. Regards, Thibault J -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
