As a quick check, can you go into /etc/init.d/tomcat6 and at around line 68 you'll see:
TOMCAT_SECURITY=yes If you're allowed to, change that line to: TOMCAT_SECURITY=no Then restart tomcat with: ../tomcat6 restart Of course, you have to be root to do this. On first glance, I don't see a security policy that would cause this. However, if you look at the Ubuntu bugs database, there are many instances of people complaining about the security manager being enabled by default. Just my two cents . . . /mde/ --- On Wed, 2/3/10, c...@munat.com <c...@munat.com> wrote: > From: c...@munat.com <c...@munat.com> > Subject: RE: Parameters disappear from PUTs > To: "Tomcat Users List" <users@tomcat.apache.org> > Date: Wednesday, February 3, 2010, 10:43 PM > OK, turns out my brother has > wireshark installed. We ran it, and the > packets are definitely getting to the server with the PUT > params intact. > So they arrive at the server, but they are missing from the > output of the > valve. Does this mean Tomcat is hosed? > > I thought maybe I'd test 24 on my laptop, but macports is > still at 20, > too. Guess I'll have to do it the hard way. > > >>> From: c...@munat.com > [mailto:c...@munat.com] > >>> Subject: Parameters disappear from PUTs > >>> > >>> When I load my app into Tomcat 6 (Ubuntu), the > form submission works > >>> perfectly if I use a POST: the params are > definitely received. If I > >>> use a PUT, it works, but the parameters are > missing > >> > >> 1) Tell us your /exact/ Tomcat aversion, and > whether it's a 3rd-party > >> repackaged one or a real Tomcat from > tomcat.apache..org. (The Ubuntu > >> flavor of Tomcat gives many people grief, albeit > not with the symptoms > >> you > >> describe.) > > > > I don't actually have a Tomcat aversion, which is why > I'm using it. (It's > > more of an aversion to computers in general, I'd say.) > But the Tomcat > > version is 6.0.20-2ubuntu2. > > > >> 2) Tell us the /exact/ JVM version and vendor > you're using. > > > > Looks like Sun JDK 6-15-1.. > > > >> 3) Take a Wireshark or equivalent trace to verify > that the parameters > >> are > >> being sent over the wire. > > > > Wireshark is kind of a bear to use and I'm not at the > server. If I used > > Live HTTP Header in Firefox and confirmed that the > params are going out, > > is that enough? Because I did and they are. The only > difference in the > > headers is that the POST header includes: > > > > Pragma: no-cache > > Cache-Control: no-cache > > > > > >> 4) Enable the Request Dumper Valve to see if the > parameters are making > >> it > >> into Tomcat (but heed the warning about character > encoding side > >> effects): > >> http://tomcat.apache.org/tomcat-6.0-doc/config/valve.html#Request%20Dumper%20Valve > > > > I did. If I POST the params are there. If I PUT, they > are not, repeat, > > not. > > > >> 5) Try the latest Tomcat 6.0.24 download and see > if the problem > >> persists. > >> Note the following bug report: > >> https://issues.apache.org/bugzilla/show_bug.cgi?id=37794 > >> which was corrected in 6.0.21. It's for > handling POST parameters, but > >> might be related. > > > > Sadly, this is not currently possible. Apt-get is > still at 20, and nothing > > goes on the server that doesn't go through Apt-get. > Fortunately, I can > > work around it by using POST for now, but it would be > nice to be able to > > do REST right. > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
