Just to double-check, can you acces the form data via the HTTPRequest?
-
chasc...@munat.com 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
Sounds to me like a Tomcat issue... I think we're relying on the container
to parse the body correctly.
On Wed, Feb 3, 2010 at 9:15 PM, c...@munat.com wrote:
It's POST vs. PUT. I'm using AJAX, so I can do PUTs.
The two are identical, except:
POST instead of PUT
The POST version includes:
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
Please put together a reproduceable example on GitHub (works in Jetty,
doesn't work in Tomcat) and we'll look at it.
On Wed, Feb 3, 2010 at 11:48 AM, c...@munat.com 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
Thanks, David.
That's a non-trivial exercise for me, so let me chase down another lead at
the moment. If that proves fruitless, I'll bite the bullet and get
something up on GitHub.
Chas.
Please put together a reproduceable example on GitHub (works in Jetty,
doesn't work in Tomcat) and we'll
Is it a POST or a GET?
On Wed, Feb 3, 2010 at 11:44 PM, c...@munat.com wrote:
Thanks, David.
That's a non-trivial exercise for me, so let me chase down another lead at
the moment. If that proves fruitless, I'll bite the bullet and get
something up on GitHub.
Chas.
Please put together a
It's POST vs. PUT. I'm using AJAX, so I can do PUTs.
The two are identical, except:
POST instead of PUT
The POST version includes:
Pragma: no-cache
Cache-Control: no-cache
which the PUT does not. In other words, the headers are identical except
for the above.
In Jetty, no problem. In Tomcat,
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, c...@munat.com 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
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
