On Thu, Jun 25, 2009 at 5:39 PM, Roald Hoolwerf<ro...@hoolwerf.net> wrote:
> But that is exactly my problem: Why is my client sending a GET request > instead of a POST request? No idea. That is definitely a nonsense and be it just for the length restrictions of GET. > I’ve tried “redirecting” the request to > super.doPost(), but that gave the following error: > org.apache.xmlrpc.XmlRpcException: Failed to parse XML-RPC request: > Premature end of file. Makes no sense. A POST request allows to process an unnamed object: The request body. In a GET request, we could at best select a particular parameter to parse it. In other words, you need to have the client fixed. > I’ve tried looking up the Content-length of the request, but for both > doGet() and doPost() those are -1. They shouldn’t be -1 as far as I know? For GET the -1 is perfectly fine: There is no request body, hence no content. Jochen -- Don't trust a government that doesn't trust you.
