Preventing iframe caching in browser

Question

How do you prevent Firefox and Safari from caching iframe content   I have a simple webpage with an iframe to a page on a different site  Both the outer page and the inner page have HTTP response headers to prevent caching  When I click the  back  button in the browser  the outer page works properly  but no matter what  the browser always retrieves a cache of the iframed page  IE works just fine  but Firefox and Safari are giving me trouble   My webpage looks something like this    lt html gt     lt head gt  lt  -- stuff -- gt  lt  head gt   lt body gt     lt  -- stuff -- gt     lt iframe src  webpage2 html var xxx    gt     lt  -- stuff -- gt   lt  body gt   lt  html gt    The var variable always changes  Despite the fact that the URL of the iframe has changed  and thus  the browser should be making a new request to that page   the browser just fetches the cached content   I ve examined the HTTP requests and responses going back and forth  and I noticed that even if the outer page contains  lt iframe src  webpage2 html var 222    gt   the browser will still fetch webpage2 html var 111   Here s what I ve tried so far    Changing iframe URL with random var value Adding Expires  Cache-Control  and Pragma headers to outer webpage Adding Expires  Cache-Control  and Pragma headers to inner webpage   I m unable to do any JavaScript tricks because I m blocked by the same-origin policy    I m running out of ideas  Does anyone know how to stop the browser from caching the iframed content   Update  I installed Fiddler2 as Daniel suggested to perform another test  and unfortunately  I am still getting the same results   This is the test I performed    Outer page generates random number using Math random   in JSP  Outer page displays random number on webpage  Outer page calls iframe  passing in random number  Inner page displays random number    With this test  I m able to see exactly which pages are updating  and which pages are cached   Visual Test  For a quick test  I load the page  navigate to another page  and then press  back   Here are the results   Original Page    Outer Page  0 21300034290246206 Inner Page  0 21300034290246206   Leaving page  then hitting back    Outer page  0 4470929019483644 Inner page  0 21300034290246206   This shows that the inner page is being cached  even though the outer page is calling it with a different GET parameter in the URL  For some reason  the browser is ignoring the fact that the iframe is requesting a new URL  it simply loads the old one   Fiddler Test  Sure enough  Fiddler confirms the same thing    I load the page    Outer page is called  HTML   0 21300034290246206  lt iframe src  http   ipv4 fiddler 1416 page1 aspx var 0 21300034290246206    gt    http   ipv4 fiddler 1416 page1 aspx var 0 21300034290246206 is called    I navigate away from the page and then hit back    Outer page is called  HTML   0 4470929019483644  lt iframe src  http   ipv4 fiddler 1416 page1 aspx var 0 4470929019483644    gt    http   ipv4 fiddler 1416 page1 aspx var 0 21300034290246206 is called   Well  from this test  it looks as though the web browser isn t caching the page  but it s caching the URL of the iframe and then making a new request on that cached URL  However  I m still stumped as to how to solve this issue   Does anyone have any ideas on how to stop the web browser from caching iframe URLs

User · Answer

Have you installed Fiddler2   It will let you see exactly what is being requested  what is being sent back  etc  It doesn t sound plausible that the browser would really hit its cache for different URLs

User · Answer

If you want to get really crazy you could implement the page name as a dynamic url that always resolves to the same page  rather than the querystring option   Assuming you re in an office  check whether there s any caching going on at a network level  Believe me  it s a possibility  Your IT folks will be able to tell you if there s any network infrastructure around HTTP caching  although since this only happens for the iframe it s unlikely

User · Answer

Make the URL of the iframe point to a page on your site which acts as a proxy to retrieve and return the actual contents of the iframe  Now you are no longer bound by the same-origin policy  EDIT  does not prevent the iframe caching issue

User · Answer

I also had this problem in 2016 with iOS Safari  What seemed to work for me was  giving a GET-parameter to the iframe src and a value for it like this   lt iframe width  60   src     other url cachebust 1  allowfullscreen gt  lt  iframe gt

User · Answer

Have you tried adding the various HTTP Header options for no-cache to the iframe page

User · Answer

To get the iframe to always load fresh content  add the current Unix timestamp to the end of the GET parameters  The browser then sees it as a  different  request and will seek new content   In Javascript  it might look like   frames  my iframe   location href  load iframe content php group ID     group ID     amp timestamp     timestamp

User · Answer

After trying everything else  except using a proxy for the iframe content   I found a way to prevent iframe content caching  from the same domain   Use  htaccess and a rewrite rule and change the iframe src attribute   RewriteRule test   0-9      a-zA-Z0-9    html   test index php idEntity  1 amp token  2  QSA   The way I use this is that the iframe s URL end up looking this way  example com test 54 e3116491e90e05700880bf8b269a8cc7 html    Where  token  is a randomly generated value  This URL prevents iframe caching since the token is never the same  and the iframe thinks it s a totally different webpage since a single refresh loads a totally different URL       example com test 54 e3116491e90e05700880bf8b269a8cc7 html example com test 54 d2cc21be7cdcb5a1f989272706de1913 html  both lead to the same page   You can access your hidden url parameters with   SERVER  QUERY STRING

User · Answer

I set iframe src attribute later in my app  To get rid of the cached content inside iframe at the start of the application I simply do   myIframe src             somewhere in the beginning of js code  for instance in jquery     handler   Thanks to  http   www freshsupercool com 2008 07 10 firefox-caching-iframe-data

User · Answer

I found this problem in the latest Chrome as well as the latest Safari on the Mac OS X as of Mar 17  2016  None of the fixes above worked for me  including assigning src to empty and then back to some site  or adding in some randomly-named  name  parameter  or adding in a random number on the end of the URL after the hash  or assigning the content window href to the src after assigning the src   In my case  it was because I was using Javascript to update the IFRAME  and only switching the hash in the URL   The workaround in my case was that I created an interim URL that had a 0 second meta redirect to that other page  It happens so fast that I hardly notice the screen flash  Plus  I made the background color of the interim page the same as the other page  and so you notice it even less

User · Answer

It is a bug in Firefox 3 5   Have a look   https   bugzilla mozilla org show bug cgi id 279048

User · Answer

This is a bug in Firefox   https   bugzilla mozilla org show bug cgi id 356558  Try this workaround    lt iframe src  webpage2 html var xxx  id  theframe  gt  lt  iframe gt    lt script gt  var  theframe   document getElementById  theframe     theframe contentWindow location href    theframe src   lt  script gt

User · Answer

As you said  the issue here is not iframe content caching  but iframe url caching   As of September 2018  it seems the issue still occurs in Chrome but not in Firefox   I ve tried many things  adding a changing GET parameter  clearing the iframe url in onbeforeunload  detecting a  reload from cache  using a cookie  setting up various response headers  and here are the only two solutions that worked from me   1- Easy way  create your iframe dynamically from javascript  For example   const iframe   document createElement  iframe   iframe id           iframe src   myIFrameUrl  document body appendChild iframe    2- Convoluted way  Server-side  as explained here  disable content caching for the content you serve for the iframe OR for the parent page  either will do    AND  Set the iframe url from javascript with an additional changing search param  like this   const url   myIFrameUrl     timestamp     new Date   getTime   document getElementById  my-iframe-id   src   url    simplified version  beware of other search params

User · Answer

I have been able to work around this bug by setting a unique name attribute on the iframe - for whatever reason  this seems to bust the cache  You can use whatever dynamic data you have as the name attribute - or simply the current ms or ns time in whatever templating language you re using  This is a nicer solution than those above because it does not directly require JS   In my particular case  the iframe is being built via JS  but you could do the same via PHP  Ruby  whatever   so I simply use Date now     return   lt iframe src      src      name      Date now          gt      This fixes the bug in my testing  probably because the window name in the inner window changes

[browser] Preventing iframe caching in browser

Examples related to browser

Examples related to caching

Examples related to iframe

Examples related to back-button