Andréas Kühne <[EMAIL PROTECTED]> writes:

> However, at the moment I am having a bit of a problem with the
> qx.io.remote.RemoteRequest object. We are using a java backend on our
> server, running Apache infront of a tomcat application. The problem is that,
> even though we are setting the request type to "POST", the apache server
> indicates that the request URI is sometimes to long. AFAIK the parameters
> should not be put on the the URI in a post request, but rather in the
> request data. So my questions are:
>  
> 1. Am I wrong in my assumption that the URI should not have parameters on it
> if it is a POST request and not a GET request?
>
> 2. How can I solve the problem either way?

Hi Andreas,

If you are directly using RemoteRequest (which has changed names, BTW: it's
now qx.io.remote.Request in current code) then the only parameter which is
sent, by default, is "nocache".  Its value is a date string.  I wouldn't think
that this would yield a "too long" error from apache (and doesn't in any of my
tests with JSON-RPC).

Are you calling request.setParameter() from your code?  Parameters specified
this way are sent as part of the URL.

If you're not calling request.setParameter() and you want to try having no
parameters at all sent, then issue a call to request.setProhibitCaching(false)
which will remove that parameter.

A great tool for seeing what is actually being sent "over the wire" is
'wireshark', formerly called 'ethereal'.  That's the right tool to use to see
what's actually being sent from client to server.

Cheers,

Derrell

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to