Re: HTTP PUT request

Hi Mark, Sadly Malcolm is no longer with us . There is a thread herefor dealing with request parsing which - if it

Re: HTTP PUT request

Hey Malcolm, Is this still the case? This response was five years ago, why would Django not allow access to PUT and DELETE data? On Friday, 10 October 2008 11:09:02 UTC+11, Malcolm Tredinnick wrote: > > > On Thu, 2008-10-09 at 14:13 -0700, DaveV wrote: > > Ahh - never mind - I misread the

Re: HTTP PUT request

On Thu, 2008-10-09 at 14:13 -0700, DaveV wrote: > Ahh - never mind - I misread the first post. > > Still, it would seem helpful if PUT data was processed in a way that > was more readily accessible, such as a PUT dictionary like the POST or > GET ones. No, because it would be almost always

Re: HTTP PUT request

Ahh - never mind - I misread the first post. Still, it would seem helpful if PUT data was processed in a way that was more readily accessible, such as a PUT dictionary like the POST or GET ones. On Oct 9, 2:09 pm, DaveV <[EMAIL PROTECTED]> wrote: > On Aug 20, 6:13 am, Malcolm Tredinnick <[EMAIL

Re: HTTP PUT request

On Aug 20, 6:13 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > 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

Re: HTTP PUT request

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

HTTP PUT request

Hi, There seems to be an issue with Django in the HttpRequest class, in that I cannot access the data provided in a HTTP PUT request. I'm writing a web app which uses a RESTful interface, but at the moment I have to put together a piece of hacky middleware in order to be able to get the PUT data