On Wed, 2008-08-20 at 02:29 -0700, zvoase wrote: [...] > What I'm doing now is changing the method to POST, accessing the > request.raw_post_data attribute, and then changing the method back to > PUT. This seems a little unnecessary, and I'd like to suggest the > addition of a content attribute which holds any raw content provided, > whether through POST or PUT.
The raw_post_data attribute will contain the raw data regardless of the method used in the HTTP request. So it works identically for PUT and POST. Have a look at the implementation: there's nothing that restricts it to a single method. It would even work for OPTION or other HTTP verbs. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
