On Mon, Jan 18, 2010 at 8:14 AM, Malcolm Box <malcolm....@gmail.com> wrote: > On Sat, Jan 16, 2010 at 4:58 AM, Russell Keith-Magee > <freakboy3...@gmail.com> wrote: >> >> On Sat, Jan 16, 2010 at 6:32 AM, Malcolm Box <malcolm....@gmail.com> >> wrote: >> <snip> >> > It seems to me that Django should process POST and PUT requests the same >> > - >> > i.e. the request.FILES attribute should be initialised for either if a >> > multipart content-type is detected. >> > >> > Have I fundamentally misunderstood how this stuff should work? >> >> On first inspection, I don't think you've got anything fundamentally >> wrong. Support for PUT and the other 'exotic' HTTP request methods is >> one area where Django support is a little bit patchy. >> > Well that's good to know! > >> >> This is mostly an artefact of the vast majority of browsers providing >> exactly zero support for requests other that GET and POST. As a result >> Django is (by necessity) really good at handling GET and POST; PUT, >> DELETE et al are all essential parts of the full HTTP spec, but >> support in Django isn't quite as comprehensive. >> >> This is one of those areas where patches are definitely welcome. >> > I'm happy to provide some patches - presumably a bug report + patch is the > way to go.
As always. > Which raises the question of what the correct behaviour should be, so the > bug can report that it's not happening and the patch can implement. > > As a first pass: > > "On a PUT request, Django should populate request.PUT and request.FILES in > the same way as for POST requests. FILES will be initialised if the content > is multipart, and the PUT dictionary will have key/value pairs if the > uploaded content included url-encoded form entries. > > If the format of the datastream is not understood, it will be left in > _raw_post_data as previously, and req.FILES and req.PUT initialised to empty > hashes." > > Does this sound reasonable as a bug/feature description? Sounds reasonable to me. I can't think of any obvious reason that the handling for PUT should differ from POST. Yours, Russ Magee %-)
-- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
