Ha, ha. Brilliant. The writers of the Servlet Spec incorporated the short-sightedness of the browser makers, who saw no point in PUTs and DELETEs. Both POST and PUT methods include entities per RFC 2616, so why is PUT the poor step-sister?
Maybe I'll take another look at virtual hosting in Jetty... They seem to have ignored the spec on this point. Chas. > On Fri, Feb 5, 2010 at 6:34 PM, David Pollak > <feeder.of.the.be...@gmail.com> wrote: >> Crud. >> >> Can someone do a survey of how other JVM web frameworks handle the PUT >> inconsistencies on different containers? > > Does S.param map directly to the servletrequest getParameter? If so, > I think the Servlet Spec explains it: > > The following are the conditions that must be met before post form > data will be populated to the parameter set: > 1. The request is an HTTP or HTTPS request. > 2. The HTTP method is POST. > 3. The content type is application/x-www-form-urlencoded. > 4. The servlet has made an initial call of any of the getParameter > family of methods on the request object. > > /Jeppe > > -- > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to lift...@googlegroups.com. > To unsubscribe from this group, send email to > liftweb+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/liftweb?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
