Hi, On Wednesday, December 7, 2011 11:09:38 AM UTC+1, Thibault Jouannic wrote: > > If I'm not wrong, only the PUT method can specify POST like > parameters. >
Before writing my answer I did look on w3c and at least OPTIONS is allowed to have a body (can't tell you if it has to be a specific contenttype, but I doubt that). Well, fix is not that simple, since you have to handle the multipart/ > form-data case, (which is the default encoding used in test client): > Agreed, I was mostly referring to your curl example which shouldn't issue multipart I guess ;) I can work with that. My main concern is the lack of clarity in the > documentation. > +1 one, it would be good to know when what is filled (as people seem to appear to have problems with the current form). > Then, maybe a variable named something like FORM_DATA would be less > error prone? > Right, but that would make the distinction between GET and POST disappear, or at least I would expect GET params to be in it if I submitted a form etc… Either way, since form-data is usually not the common way for stuff like this people might ask why there is no JSON_DATA etc… Anyway, I think that discussion should be summarized > somewhere in the documentation, to prevent any further WTF?! effect. Please add a patch to the tracker, since it always best if people with the problem write it as they know what's missing. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/Tagzx6tF-K4J. 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.
