Hello Sean,
what comes to my mind first is an issue where the input stream is consumed
before it goes to the testPost method.
Is there some filters (servlet or not) that read the input stream or
consume the request's representation (for example by printing it?)
You can try to debug by providing
Thanks for the hint Thierry. I found a place where one of the 11 (!)
filters in our app was unconditionally calling getParameter on the
ServletRequest. It appears this causes the request body to be consumed,
at least when the Content-Type is x-www-form-urlencoded. I changed it
to avoid
Hello Sean,
that sounds great!
Effectively, getting parameters consumes the request's body, as explains
here
http://docs.oracle.com/javaee/6/api/javax/servlet/ServletRequest.html#getParameter%28java.lang.String%29
:
If the parameter data was sent in the request body, such as occurs with an
HTTP
I have been having a problem for a while, that comes and goes. Recently
it came back and won't go. :-( This is Restlet 2.1.4, Java EE edition.
Sometimes when a client posts a non-empty form with
application/x-www-form-urlencoded, the form arrives empty at the @Post
method. As you might be
4 matches
Mail list logo