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. doGetSerializationPolicy-call. This way we don't get the XSRF error.
Hope this helps you out. Best regards Klemens Schrage Am Montag, 10. August 2015 15:36:24 UTC+2 schrieb 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 in the > same web application as for the servlet. > Tried few variations using ProxyPass / ProxyPassReverse and Substitute but > no resolution yet. Has anyone configured as similar setup? Any suggestion > would be appreciated. > best > *K > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
