I think we'll explore some of these options but maybe start with turning off SSL on our server. For now, I can also run with the embedded local Jetty server using ssh-port-forwarding on some of the ports for the client-server communication.
-- Thanks for the help!
On Wednesday, October 1, 2014 3:26:33 AM UTC-6, Thomas Broyer wrote:
On Wednesday, October 1, 2014 3:26:33 AM UTC-6, Thomas Broyer wrote:
On Wednesday, October 1, 2014 1:16:23 AM UTC+2, Rogelio Flores wrote:Mmm, could it be that my remote server uses HTTPS? I see a javascript warning about this in the console, and just noticed in the release notes something about super dev mode being disabled for security reasons in that scenario and that it didn't work anyway (?). Is there a workaround for that other than not running HTTPS? I know you'll say just run without ssl, but in my case it's not that easy.I think you can make it work, but it's not that easy:
- use a custom linker that extends CrossSiteIframeLinker and overrides getJsDevModeRedirectHookPermit
ted
https://gwt.googlesource.com/gwt/+/2.6.1/dev/core/src/com/ google/gwt/core/linker/ CrossSiteIframeLinker.java#275 - setup a reverseproxy on your host to serve your CodeServer with HTTPS
see https://gwt.googlesource.com/gwt/+/ 0fee61f7b0ece4ded32f9b9a25cf6b bcde5521de/dev/codeserver/ java/com/google/gwt/dev/ codeserver/SourceHandler.java# 157 An alternative could be to setup a reverseproxy to your remote server to see it locally as HTTP?
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+unsubscribe@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.
No comments:
Post a Comment