Re: GwT app behing Apache httpd ProxyPass

2015-08-11 Thread Ed
Here is what our proxy directive's looks like. We used this with RPC and RequestBuilder. VirtualHost *:443 ProxyPreserveHost On ProxyRequests Off ServerName .yy.com ServerAlias SSLProxyEngine On SSLProxyCheckPeerCN off SSLProxyCheckPeerExpire off ProxyPass /

Re: GwT app behing Apache httpd ProxyPass

2015-08-11 Thread Piotr Morgwai Kotarbinski
the below thread is about a similar issue, hope it will help you: https://groups.google.com/forum/#!starred/google-web-toolkit/Zi_dtUEePlY On Monday, August 10, 2015 at 8:36:24 PM UTC+7, Kulnor wrote: Am trying to provide public access to a back end GwT app running on back end private cloud

Re: GwT app behing Apache httpd ProxyPass

2015-08-10 Thread Klemens Schrage
We solved this by extending RemoteServiceServlet and overriding doGetSerializationPolicy. This method has a Parameter for the moduleBaseURL. We check if the moduleBaseURL starts with www.ourdomain.com/proxyname/appname and replace it with www.ourdomain.com/appname prior to the super.

Re: GwT app behing Apache httpd ProxyPass

2015-08-10 Thread Klemens Schrage
We solved this by extending RemoteServiceServlet and overriding doGetSerializationPolicy. Thie method has the moduleBaseURL as a parameter. We replace the moduleBaseURL coming in as www.domain.com/proxyname/appname with www.domain.com/appname and call *super*.doGetSerializationPolicy. This way

GwT app behing Apache httpd ProxyPass

2015-08-10 Thread Kulnor
Am trying to provide public access to a back end GwT app running on back end private cloud server going through an Apache httpd server as front end proxy. I can ProxyPass via AJP or HTTP, but when I try to load the app, I get an XSRF error on the first call as the module path requested is not