Re: HTTP Referer problem with GWT
> > When is 2.7 scheduled to release? > I think I have read somewhere (here or on G+) that RC1 might happen at the end of september. -- J. -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: HTTP Referer problem with GWT
> > How can I use the xsiframe linker? > > What impact will this have on my webapp? If I still use the devMode will > it break it? > The only difference is that permutations are now js files and not html files. So if you don't do anything special with the GWT compiler output (e.g. matching *.cache.html in a web server or similar) then you should not have any problems. -- J. -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: HTTP Referer problem with GWT
How can I use the xsiframe linker? What impact will this have on my webapp? If I still use the devMode will it break it? Le vendredi 5 septembre 2014 11:31:47 UTC-4, Jens a écrit : > > Maybe use the xsiframe linker which produces *.cache.js files instead of > html files. The xsiframe linker will be the default in GWT 2.7 anyways. > > -- J. > -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: HTTP Referer problem with GWT
When is 2.7 scheduled to release? On Fri, Sep 5, 2014 at 11:31 AM, Jens wrote: > Maybe use the xsiframe linker which produces *.cache.js files instead of > html files. The xsiframe linker will be the default in GWT 2.7 anyways. > > -- J. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Google Web Toolkit" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/google-web-toolkit/pyYyqufWBMc/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > google-web-toolkit+unsubscr...@googlegroups.com. > To post to this group, send email to google-web-toolkit@googlegroups.com. > Visit this group at http://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: HTTP Referer problem with GWT
Maybe use the xsiframe linker which produces *.cache.js files instead of html files. The xsiframe linker will be the default in GWT 2.7 anyways. -- J. -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
HTTP Referer problem with GWT
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.x/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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
