Can they do that ONLY for IE 6 & 8? Because it doesn't look like they want to stop caching, they want the bookmark to stop going to the old iFrame source.
Greg On Jul 27, 11:04 am, Jeff Chimene <[email protected]> wrote: > On 07/27/2010 08:53 AM, Sony wrote: > > > > > A truly idiotic bunch at Microsoft must have decided this was a great > > idea: If you open an IE Bookmark in a text editor you will see it > > records an IFrame's src at the time the bookmark was created. When > > using said bookmark next time around, IE makes a request of the > > IFrame's src without even checking if the src for that IFrame has > > changed in the newly requested page && so if and only if the > > previously recorded src fails to load (either from cache or from > > server) does it try loading the new src that the IFrame tag now > > carries. > > > This is actually a major problem for our GWT web-app - as we release > > every quarter and we employ GWT's 'perfect caching' strategy i.e. > > cache policy of forever for all *.cache.* files. Both IE6 & IE8 end > > up requesting and then loading from cache the older version of our > > cache.html resulting in various incompatibility exceptions. For now > > we just let users know to delete the bookmark and recreate it in these > > types of situations. > > > Any help in fixing this issue would be appreciated. I've tried > > replacing the iframe-linker with the cross-site linker which works but > > then code-splitting is not supported (which we rely on heavily). > > > Thanks much > > Sony > > You can set the cache properties using .htaccess or, if you control the > httpd server, in that software's domain settings. -- 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.
