On 9/28/07, Lennon Day-Reynolds <[EMAIL PROTECTED]> wrote: > I honestly wouldn't expect PUT (or any other HTTP actions other than > GET, POST, and HEAD) to pass the input through a normal > form-decoding step -- most of the time, the "payload" for a PUT is > going to be XML, JSON, or even raw binary. > > Since browsers won't do PUT, why build in support for what amounts > to a browser-only MIME type (application/x-www-form-urlencoded)?
It seems to me that most restful frameworks are assuming that you can PUT the same as you can POST, i.e. that other than the verb (and what you might do with it) the two will be treated the same. I actually ran in to this problem while mussing around with my little Camping testing framework, since I was assuming that doing a proper PUT would have the same affect as doing a simulated PUT using a special query parameter. But I was surprised to find out that I was wrong, and that things aren't parsed as one would expect. Of course, there's also the fact that while browsers don't *currently* support form verbs besides POST, I'm hopeful that that may change eventually. So am I wrong in assuming that PUT and other non-GET verbs should support application/x-www-form-urlencoded, or is this something that should be made to behave more consistently? -- Nathaniel Talbott <:((>< _______________________________________________ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
