Home Dashboard Directory Help
Search

IE 10 on Windows 8 does not refresh page on Browser Back by lmckenney


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


Type: Bug
ID: 788524
Opened: 5/23/2013 11:04:47 AM
Access Restriction: Public
1
Workaround(s)
view
0
User(s) can reproduce this bug

Description

There may be several inter-related issues:
1. I have Browser History->Temporary Internet Files set to Check for newer versions Every time I visit a page. I've also tried Automatically. My setting stays, unlike some seeing a flip-flop of the setting.
2. In F12 Developer Tools, Cache setting "Always refresh from server" is greyed out and cannot be changed. It doesn't seem to matter if Protected Mode is on or off. I consider this another problem, but included here, since it might be related to, or the cause of, my browser back problem.
3. I have checked Syncmode5 and it correctly reflects Every time I visit a page.

When I visit the https://transparentct.com website on my new (one month old) Windows 8 IE10 machine, information messages and updates to web pages are not refreshed when I browser back to the page. For instance, from the Home page, if I navigate to another page to set a preference that will be reflected on the Home page, and then browser back to the Home page, the preference change is not visible. If I manually refresh or select Home from the menu, then the page is updated and the change is visible. And it's not just by going one page away. I can go numerous pages, and then traverse back to the original page via browser back, and the content is still stale. With Vista / IE 8 and Windows 7 / IE 8 on this site, this is not an issue. I have tried compatibility view for the domain, as well as IE 7, IE 8 and IE 9 emulation modes on this machine, to no avail.

I don't think this problem is specific to this particular website, but I can't think of a site where I can predict that the page should have changed while I was "away" on other pages within the site.
Details
Sign in to post a comment.
Posted by EricLaw [ex-MSFT] on 12/27/2013 at 9:06 AM
As described in the blog post, this behavior is by-design. If you want to prevent use of the cache, you need to use no-store.
http://blogs.msdn.com/b/ie/archive/2010/07/14/caching-improvements-in-internet-explorer-9.aspx
Posted by Microsoft on 6/27/2013 at 3:31 PM
Thank you for your feedback.

We are currently unable to reproduce this issue as described. We have recently released Internet Explorer 11 Release Preview. If you can still reproduce the issue, please reactivate the feedback or submit a new feedback for the issue. Thank you.

Best regards,

The Internet Explorer Team
Posted by Microsoft on 6/14/2013 at 2:23 PM
lmckenney, thank you for your feedback.

1- Please provide the refrences to MSDN documentation you are using.
2- Please provide us with the requested fiddler trace, for our review.
3- What other post are you refrencing in your comments.

We value your feedback. If you have the additional information requested, please submit with more details on how to reproduce the issue. You can also read the guidelines at https://connect.microsoft.com/IE/content/content.aspx?ContentID=16254 regarding filing a good bug report.

Best regards,

The Internet Explorer Team
Posted by lmckenney on 5/30/2013 at 12:52 PM
I have done some analysis with Fiddler on my Vista IE8 vs my Windows 8 IE10 machines for the website. I also found this on an msdn blog, which is very discouraging to me and may account for some of the other posts on this site:

Without further ado, here are some IE10 Minor Changes:

•Internet Explorer now ignores no-cache on back/forward navigations, as other browsers do and RFC2616 allows. ◦This also allows Conditional GET revalidation of no-cache resources.
◦Use no-store to prevent resource reuse in forward/back navigations.

Our website uses no-cache, must re-validate and even has an Expire date in the past. But true to the blog, IE10 is ignoring no-cache and apparently Expire date/time on browser forward and back. IE8 in Fiddler sees that the ETag has changed because it sends the request. Fiddler doesn't even see a request or the movement to the new url via the browser back or forward when on Windows 8 and IE10, so I don't even get a 304 not modified response. In fact, as far as Fiddler seems to know, I never left the last page that wasn't cached. IE10 just grabs the cached version, even though it is stale, without asking about it because we haven't incorporated the no-store into our website code.

If I have mis-interpreted the blog and what I've seen with Fiddler, please let me know. If more than just adding no-store is necessary to cause a real refresh on browser back and forward, I would love to hear more on this as well.

Thank you.

Posted by Microsoft on 5/24/2013 at 11:08 AM
Thank you for your feedback.

To assist with troubleshooting this issue, please provide a fiddler trace - taken while you repro the issue.
http://fiddler2.com/get-fiddler


We value your feedback. If you have additional information that can help us recreate this issue — such as a specific url, more detailed steps, test results from different machines, or additional conditions needed to repro the bug. You can also read the guidelines at https://connect.microsoft.com/IE/content/content.aspx?ContentID=16254 regarding filing a good bug report.

Best regards,

The Internet Explorer Team
Sign in to post a workaround.
Posted by lmckenney on 5/30/2013 at 12:53 PM
possibly adding no-store to the Cache parameters, since the msdn blog says ie10 ignores no-cache on browser back and forward.