Hi, On Wednesday, December 7, 2011 9:33:52 AM UTC+1, Thibault Jouannic wrote:
> 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? > That would be really odd imo and confusing as hell if you find PUT/DELETE/HEAD/OPTIONS/whatever data in request.POST > 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)? > put_data = QueryDict(self.raw_post_data, encoding=your_encoding) not really hard if you ask me. > 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. > Stuffing it into POST is a no go, adding an extra PUT/OPTIONS/<whatever http verb allows entitity body> is something we don't like either. Given that the fix in Client code is a oneliner I think it's not really an issue. Cheers, Florian -- 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/-/2HMtmOujeKkJ. 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.
