André Warnier wrote:
Hi.
Instead of POST-ing to the Apache server on port 80, what happens if
you try to send your POST firectly to Tomcat, at http://localhost:8080 ?
Can you send a logfile of /Tomcat/ after you try that ?
Or better : stop Tomcat, remove your webapp, clean the Tomcat logs,
restart Tomcat, re-deploy your webapp, then have a look at the Tomcat
logs.
Thanks for the quick response.. I am not entirely sure how I would do
that. I am using a generic GWT RPC implementation. Are you familiar? I
should also mention that I can get to my application via Port 80 using
mod-proxy. This seems to work fine, just no functioning servlet. The
majority of the forums always bring up web.xml (I've attached in
previous post)..
-SCarlson
I did some reading.. Here is a quote from another list.
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/64c676ad67fabb6e
"GWT-RPC uses the browsers XMLHTTPRequest mechanism. As such, it is
required to use the same protocol and port used to load your host page
(to avoid running afoul of the Same Origin Policy).
So, if your host page is loaded via HTTP port 80 the RPC uses HTTP
port 80 ... if you are in hosted mode (HTTP port 8888) then rpc uses
HTTP port 8888. If your host page was loaded via HTTPS port 443 then
GWT-RPC uses HTTPS port 443. "
-SCarlson
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
