Jens, Thanks for the reply and information, it sounds like there is a workaround then for the GWT part but we still have the same/similar issue with Tomcat's authentication. We need to solve that too else its only a partial solution.
Btw, regarding the GWT serialization issue...I read online some say a way around this is to use IsSerializable instead of Serializable to mark objects going across the wire but its not clear if that 'trick' still works or not. Also some say to drop GWT RPC and use JSON instead that doesn't have the same issue. I don't really care what the format of the data is going across the wire, I just need the results to work. Is there an easy way to switch the RPC format to JSON or some other format that doesn't have this issue? -Dave On Thu, Jul 9, 2015 at 9:29 AM, Jens <jens.nehlme...@gmail.com> wrote: > The "issue" is that GWT will send you the moduleBaseURL as payload from > the client to the server and the server uses that value to find the RPC > policy file on disk. When you use a reverse proxy then the moduleBaseURL > will not change when passing the proxy, it will always be > http://domain.com/appname/<modulename> or http://domain.com/<modulename> > (depends on how you deploy your app). Because of this GWT's default > implementation of RemoteServiceServlet.doGetSerializationPolicy() does not > work anymore as it tries to match the moduleBaseURL with the server context > path which can now be totally different because of the proxy. > > So you either have to write custom code to find the RPC policy file on > your server (thats what I also do at the moment) or you can try overriding > the default moduleBaseURL on the client by using <meta name='gwt:property' > content='baseUrl=/appcontext/myapp'> in your host page. > > Also keep in mind when you use a reverse proxy that you might need to > rewrite cookie domains / paths as well. In apache you can do that with > ProxyPassReverseCookieDomain and ProxyPassReverseCookiePath. > > > -- J. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Google Web Toolkit" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/google-web-toolkit/Zi_dtUEePlY/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > google-web-toolkit+unsubscr...@googlegroups.com. > To post to this group, send email to google-web-toolkit@googlegroups.com. > Visit this group at http://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
