Hello guys,

I'm using the HTTP Referer header in my login page to redirect the user to 
the page he was after a successful login. I use "document.referrer" in the 
HTML/Javascript stand alone page.
The problem is that with the newest version of Firefox and Chrome the 
referrer includes the GWT cache in the URL of my webapps. 

Example:
I got 
https://www.example.com/com.xxx.portal.xxxxxxxxx/F7973D44FB82877B968930220546FF58.cache.html
instead of 
https://www.example.com

Do you know what I can do to get the right address instead of the one 
pointing to the cache?
Sure I can do an ugly patch in my login page to parse the string from 
referer, but I would like to have a clean method.

Thanks

Alexandre

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to