Greetings!
I've been working on migrating our application over to GWT-2.8b1 (from GWT 2.5) and moving from the classic Dev Mode to Super Dev Mode. Migrating a simple sandbox environment went fairly smoothly, and SDM worked just fine for that example, however I have run into problems with using SDM over HTTPS with an external server.
My searches haven't yielded a decent answer to this issue, though I'm aware that this is already an open bug for GWT.
https://github.com/gwtproject/gwt/issues/7535
The one possible solution I came across no longer seems to work in Chrome (mixed HTTPS-HTTP seems completely blocked), basically over-riding CrossSiteIframeLinker. From what I've read this no longer works for Chrome 46+:
http://spreadgwt.blogspot.com/2015/11/gwt-superdev-on-https-pages.html
The most common response I've seen is to develop in HTTP and deploy over HTTPS, however developing in HTTP vs HTTPS for the product requires a code change which works for getting SDM to work, but breaks other product functionality that is assuming HTTPS. This puts our development in a rather painful position.
Are there any other solutions folks have developed for this issue? It's a pretty hefty pain point for the upgrade and I'd be a little surprised if others haven't already figured out a workaround for the issue. Thanks for any suggestions or tips.
-- I've been working on migrating our application over to GWT-2.8b1 (from GWT 2.5) and moving from the classic Dev Mode to Super Dev Mode. Migrating a simple sandbox environment went fairly smoothly, and SDM worked just fine for that example, however I have run into problems with using SDM over HTTPS with an external server.
My searches haven't yielded a decent answer to this issue, though I'm aware that this is already an open bug for GWT.
https://github.com/gwtproject/gwt/issues/7535
The one possible solution I came across no longer seems to work in Chrome (mixed HTTPS-HTTP seems completely blocked), basically over-riding CrossSiteIframeLinker. From what I've read this no longer works for Chrome 46+:
http://spreadgwt.blogspot.com/2015/11/gwt-superdev-on-https-pages.html
The most common response I've seen is to develop in HTTP and deploy over HTTPS, however developing in HTTP vs HTTPS for the product requires a code change which works for getting SDM to work, but breaks other product functionality that is assuming HTTPS. This puts our development in a rather painful position.
Are there any other solutions folks have developed for this issue? It's a pretty hefty pain point for the upgrade and I'd be a little surprised if others haven't already figured out a workaround for the issue. Thanks for any suggestions or tips.
You received this message because you are subscribed to the Google Groups "GWT Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment