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, Tomca
-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
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 my
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 T
-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 requ
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
Chris,
I see the content when I read the InputStream. Thanks for your help.
Kumar
--- On Fri, 3/26/10, Christopher Schultz wrote:
> From: Christopher Schultz
> Subject: Re: tomcat PUT not working
> To: "Tomcat Users List"
> Date: Friday, March 26, 2010, 10:33 AM
&
-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 th
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 m
-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 t
2010/3/25 Kumar Kadiyala :
>
> 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 application.
Note, t
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 th
12 matches
Mail list logo
