Yeah, try dumping the Req instance and seeing what is there - if its empty, then you can be sure its Tomcat causing the problem and not Lift.
Cheers, Tim On Feb 4, 8:03 am, Naftoli Gugenheim <[email protected]> wrote: > Just to double-check, can you acces the form data via the HTTPRequest? > > ------------------------------------- > > chas<[email protected]> wrote: > > Straight from the headers: > > Content-Type: application/x-www-form-urlencoded; charset=UTF-8 > > It's a regular form with four text fields. Simple. > > Wireshark shows that the packets are arriving at the server with the > parameters intact in the header. Adding a valve to the server.xml file > allowed me to determine that they were present in Tomcat on a POST > request, but missing from the PUT. > > Proxy is through Apache 2. I can see no reason that Apache would strip > parts of the header from a PUT, so my presumption is that Tomcat is > discarding them. I've got a discussion going on the Tomcat users list, but > I'm 90% sure it's not Lift. Does the Lift filter engage before a valve? > > Chas. > > > > > > > Are you sending Content-Type: application/x-www-form-urlencoded or > > multipart/form-data (as appropriate for the body)? > > > -Ross > > > On Feb 3, 2010, at 2:48 PM, [email protected] wrote: > > >> I have a lift app that works perfectly when I use mvn jetty:run. Then I > >> package it into a war and load it up in Tomcat 6 on the server, and when > >> I > >> do, suddenly it won't work. > > >> The issue is with the S.params. I have a form that submits via an Ajax > >> PUT > >> request. The params are sent in the header just fine. As I said, works > >> like a charm on Jetty. But when it gets to Tomcat, the entity is saved > >> with blank attributes... i.e., everything worked but the > >> S.param("whatever") showed up blank. I tested this by doing > >> S.param("whatever").openOr("Phooey") and, indeed, that attribute was set > >> to "Phooey" on the new entity. > > >> Tomcat issue? Or am I missing something obvious? This form is running on > >> a > >> subdomain, so that's where I'm looking now (in server.xml). > > >> TIA, > >> Chas. > > >> -- > >> You received this message because you are subscribed to the Google > >> Groups "Lift" group. > >> To post to this group, send email to [email protected]. > >> To unsubscribe from this group, send email to > >> [email protected]. > >> 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 [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > 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 [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
