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 com.cindiescreations.CindiesCreations.server;

import javax.servlet.http.HttpServletRequest;

import com.cindiescreations.CindiesCreations.client.RootURL;
import com.google.gwt.user.server.rpc.RemoteServiceServlet;

public class RootURLImpl extends RemoteServiceServlet implements
RootURL {
        private static final long serialVersionUID = 1L;

        @Override
        public String getRootURL(String nop) {
                HttpServletRequest req = getThreadLocalRequest();
                String reqUrl = req.getRequestURL().toString();
                reqUrl = reqUrl.substring(0, reqUrl.length()-25);
                return reqUrl;
        }
}

On Jun 3, 7:06 am, Martin Trummer <[email protected]> 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: so you click the link, 
> thenhttp://..../secure/GWTApp.html#sometokenis called
> the webserver notices that this resource is secured an sends a
> redirect to https
> then the browser requestshttps://..../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
-~----------~----~----~----~------~----~------~--~---

Reply via email to