none
IE default caches setting for HTML RRS feed

  • Question

  • Hi,

    I've got over thousands PC which runs in Windows 7 with IE9.0.36. They access IIS7.5 serving static HTML pages.

    Some of them can load the updated-content, some of them aren't. After inspection, I discovered that it was used default "Expires Setting" of IIS7.5 as below.

    I've tested those setting with two IIS7.5 server, connected by IE9 and IE11. There is no such problem.

    May i know what is default HTML caches expiry setting employed?

    How does it treat if there is no information about expiry of a page.

    thanks

    Tuesday, May 5, 2015 1:34 PM

Answers

  • Hi Andrewlpchan,

    Here is a link you may be interested in :
    HTTPS Caching and Internet Explorer
    http://blogs.msdn.com/b/ieinternals/archive/2010/04/21/internet-explorer-may-bypass-cache-for-cross-domain-https-content.aspx

    For the first question :
    WinINET will not reuse a previously-cached resource delivered over HTTPS until at least one secure connection to the target host has been established by the current process.
    According to my understanding ,the cached contents from other https connections won`t be used until the other https connection has been established.They are different in this point at least.

    For the second ,I agree with you .The cached contents from the https is encrypted and the contents from the http is not .Based on the information before , even the cached contents from the https connections won`t be used unless the contents from the https have been eastablished .In my opinion ,they should be treated as different cached contents.

    Best regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Marked as answer by andrewlpchan Sunday, May 17, 2015 6:16 AM
    Friday, May 8, 2015 2:40 AM
    Moderator

All replies

  • Hi andrewlpchan,

    Here is a link for reference:(Pay attention to the "Understanding Caching"part )
    Caching Improvements in Internet Explorer 9
    http://blogs.msdn.com/b/ie/archive/2010/07/14/caching-improvements-in-internet-explorer-9.aspx

    This catalog is concentrated on Internet Explorer 8, 9 and 10 and Internet Explorer 11 for the IT Pro Audience. Topics covered are: Installation, Deployment, Configuration, Security, Group Policy, Management questions.
    To get more information ,it is recommended to ask for help from our IIS Forum .Thanks for your understanding and cooperation.
    IIS Forum
    http://forums.iis.net/

    Best regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.


    Wednesday, May 6, 2015 7:29 AM
    Moderator
  • Yes,

    I found that before, of which some of IE9 is not working.

    As the IIS server didn't config the HTTP response headers before (i.e.: Expires, Cache-Control, Pragma.), It uses default setting rather than that , IE didn't know if it is fresh, neither by

    max-age = (DownloadTime - LastModified) * 0.1

    But this is for some browsers only.

    From the passage, It still uses max-age for the validation of freshness

    If a cached response is stale (older than its max-age or past the Expires date), then the client will make a conditional request to the server to determine whether the previously cached response is still valid and should be reused. The conditional request contains an If-Modified-Since and/or If-None-Match header that indicates to the server what version of the content the browser cache already contains. The server can indicate that the client’s version is still fresh by returning HTTP/304 Not Modified headers with no body, or it can indicate that the client’s version is obsolete by returning a HTTP/200 OK response with the new version of the content.

    Thanks alot

    Wednesday, May 6, 2015 8:11 AM
  • May i know if http and https is different cache handling machanism? Means, if IE caches one file over http and this cache will be never used against https. Am i right? Thanks
    Thursday, May 7, 2015 1:40 PM
  • Hi Andrewlpchan,

    Here is a link you may be interested in :
    HTTPS Caching and Internet Explorer
    http://blogs.msdn.com/b/ieinternals/archive/2010/04/21/internet-explorer-may-bypass-cache-for-cross-domain-https-content.aspx

    For the first question :
    WinINET will not reuse a previously-cached resource delivered over HTTPS until at least one secure connection to the target host has been established by the current process.
    According to my understanding ,the cached contents from other https connections won`t be used until the other https connection has been established.They are different in this point at least.

    For the second ,I agree with you .The cached contents from the https is encrypted and the contents from the http is not .Based on the information before , even the cached contents from the https connections won`t be used unless the contents from the https have been eastablished .In my opinion ,they should be treated as different cached contents.

    Best regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Marked as answer by andrewlpchan Sunday, May 17, 2015 6:16 AM
    Friday, May 8, 2015 2:40 AM
    Moderator