On 27. 04. 2021. 12:42, Gordan Krešić wrote:
On 27. 04. 2021. 12:37, Vassilis Virvilis wrote:
No sure about that, but if you want to debug in https:// I have written a
blog post after reading the github issue:
https://github.com/gwtproject/gwt/issues/7535
https://vasvir.wordpress.com/2017/02/07/gwt-super-dev-mode-https-setup-in-7-steps/
Yep, overriding default linker looks like the only solution.
Nope, CodeServer's .nocache.js file is not result of linking, but simple
template:
https://github.com/gwtproject/gwt/blob/master/dev/codeserver/java/com/google/gwt/dev/codeserver/stub.nocache.js
Used very simply by CodeServer's LauncherDir:
https://github.com/gwtproject/gwt/blob/47f0f717ed7653c853ef03b5bf511f38e0143c80/dev/codeserver/java/com/google/gwt/dev/codeserver/LauncherDir.java#L122
Looks like Vassilis'es solution worked only using bookmarklets:
https://github.com/gwtproject/gwt/issues/7535
So I downgraded my expectations:
1. I run CodeServer once to get .nocache.js it generates
2. Modified it (basically, just changed serverUrl declaration) and saved
under different name
3. Updated my index.html to include that renamed .nocache.js
Works for debugging session, but now I have to be careful not to let this
slip into production.
-gkresic.
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit/2004b2ff-6bc7-01c0-118c-8c0a91c0a998%40steatoda.com.
