thanks for the detailed answer
* let your server send an HTML page doing a JavaScript redirect to
the HTTPS URL, passing the hash along:
I like that idea, but I couldn't find an easy way to teach my tomcat
doing this
so I do something similar:
in the HTML page of my application I insert some
we have some public (plain HTML) pages, that are not ssl encrypted
these pages have (relative) links to a GWT application
some of those links in the public area use history tokens, to open
certain views of the GWT application: so you click the link, then
http:///secure/GWTApp.html#sometoken
On 3 juin, 14:06, Martin Trummer martin.trum...@24act.at wrote:
we have some public (plain HTML) pages, that are not ssl encrypted
these pages have (relative) links to a GWT application
some of those links in the public area use history tokens, to open
certain views of the GWT application:
I has some issues like this also, what i did was update my site to
always use fully qualified names. How I did this for GWT, i created a
RPC call back to the server to get the web server name and then always
added this to my pages.
Below is the code on the server side.
package
