Re: tomcat PUT not working

2010-03-31 Thread Michael Wojcik
Christopher Schultz wrote: On 3/28/2010 6:28 PM, Michael Wojcik wrote: André Warnier wrote: For all these reasons, currently Tomcat does not support the getParameters() family of methods, when the request method is PUT. This is a Tomcat limitation, not an HTTP one. Again, Tomcat does not

Re: tomcat PUT not working

2010-03-29 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 André, On 3/28/2010 10:23 AM, André Warnier wrote: For GET and POST requests, both the HTTP RFC and the Servlet Spec provide some answers and describe how it is done. Basically (and roughly), - for a GET (which does not have a body), such request

Re: tomcat PUT not working

2010-03-29 Thread Michael Wojcik
André Warnier wrote: The area of contention here is whether a HTTP PUT request can or not have parameters, and whether such parameters can or not be encoded as part of the HTTP body of a PUT request (or as part of the URL query string of the request). As far as I can tell, this is a Tomcat

Re: tomcat PUT not working

2010-03-29 Thread André Warnier
Michael, Many thanks for your comments, clarifications and references. I believe that these will help the Tomcat development team in their decision about implementing (or not) the getParameter family of methods on HTTP methods other than GET and POST. I did indeed leave some aspects out of

Re: tomcat PUT not working

2010-03-29 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael, On 3/28/2010 6:28 PM, Michael Wojcik wrote: André Warnier wrote: For all these reasons, currently Tomcat does not support the getParameters() family of methods, when the request method is PUT. This is a Tomcat limitation, not an HTTP

Re: tomcat PUT not working

2010-03-28 Thread André Warnier
Kumar Kadiyala wrote: Chris, I see the content when I read the InputStream. Thanks for your help. Hi. It seems that you are helped, and that is the essential part. Maybe to balance a bit with the subject of your post (Tomcat PUT not working), I just want to provide some additional

Re: tomcat PUT not working

2010-03-26 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kumar, On 3/25/2010 4:34 PM, Kumar Kadiyala wrote: I have REST based web services some of which use the PUT method. The PUT method can contain a request body. The web service works fine with Websphere and is out in the field. We are in the

Re: tomcat PUT not working

2010-03-26 Thread Kumar Kadiyala
Chris, I see the content when I read the InputStream. Thanks for your help. Kumar --- On Fri, 3/26/10, Christopher Schultz ch...@christopherschultz.net wrote: From: Christopher Schultz ch...@christopherschultz.net Subject: Re: tomcat PUT not working To: Tomcat Users List users

tomcat PUT not working

2010-03-25 Thread Kumar Kadiyala
Hi, I have REST based web services some of which use the PUT method. The PUT method can contain a request body. The web service works fine with Websphere and is out in the field. We are in the process of migrating to tomcat and I noticed that my web service which uses PUT is not able to get

Re: tomcat PUT not working

2010-03-25 Thread Konstantin Kolinko
2010/3/25 Kumar Kadiyala kumark...@yahoo.com: We are in the process of migrating to tomcat and I noticed that my web service which uses PUT is not able to get the request body anymore. I use HttpServletRequest's getInputStream and it always returns null. It should be something in your

Re: tomcat PUT not working

2010-03-25 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kumar, On 3/25/2010 12:53 PM, Kumar Kadiyala wrote: I have REST based web services some of which use the PUT method. The PUT method can contain a request body. The web service works fine with Websphere and is out in the field. We are in the

Re: tomcat PUT not working

2010-03-25 Thread Kumar Kadiyala
Hi Chris, On 3/25/2010 12:53 PM, Kumar Kadiyala wrote: I have REST based web services some of which use the PUT method. The PUT method can contain a request body. The web service works fine with Websphere and is out in the field. We are in the process of migrating to tomcat and I noticed that