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 is called the webserver notices that this resource is secured an sends a redirect to https then the browser requests https://..../secure/GWTApp.html#sometoken
that works fine in all browsers, except... you'll never guess it ...here it comes: Internet Explorer (tested in IE6 and IE7) the only workarounds I can think of: * use absolute URLs in the public pages: <a href="https://my.domain.com/.../secure/GWTApp.html#sometoken> I don't like that, because the domain is different for the development/test/productiontest servers * I could use a special URL parameters to wrap the historytoken <a href="./secure/GWTApp.html?historyToken=sometoken> and when the application starts I could implement some magic to update the history maybe anyone knows a more elegant way to solve this? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
