iframe caching bug????

[bhu Boue vidya]

hi there

i have a web page which displays a list of "stories" in summary
format, the user can then click on an entry and the actual story will
be viewed inplace. the story is injected into the web page via an
iframe (i use iframes as our stories have to be compatible with iOS
into the future). a story could be a youtube, a vimeo, a custom story
type etc.

the url for a story iframe is of the form "/embed/viewer/story/9999"
where 9999 is the unique story id. when the user wants to preview a
story any existing story that is onscreen is closed (i.e. that iframe
in the DOM is removed - using jQuery), so there is only one story
iframe on the page at any one time.

it all works well, except after a while, the wrong story starts
getting played! (it is always a story that was previously played on
the page). i have checked my injection code - fine - i checked
outerHTML of the injected code, fine - when inspecting via dev tools
the iframe's src url is exactly what it should be, yet when i look at
my apache logs the url being resolved on the server for the iframe is
for the previous (wrong) story(!!!!) - once this happens every story
preview thereafter is the same wrong story....

i don't get it - the story urls being used in the iframe are all
unique for each story - there can't be any kind of weird caching going
on, surely? i have also made sure the story viewer iframe code emits
"no caching"-style headers.

why oh why would the browser be asking for a different url to the one
injected into the DOM?

any help greatly appreciated!
bhu

[PhistucK]

Yes, unfortunately, that was a highly annoying bug that also affected YouTube videos/Google advertisements and other iFrames in Google Reader (for example) since the birth of Chrome.

I assume you are using the stable version of Chrome.

But, hey, fear not, the salvation is near!

There is a fix for this in Chrome 14 (currently in beta). :)

It should be released as stable within a few weeks.

The tracking issue for this was -

crbug.com/73460

☆PhistucK

--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
   http://groups.google.com/a/chromium.org/group/chromium-discuss

[bhu Boue vidya]

thank you thank you thank you

i thought i was going mad....

bring on chrome 14

On Sep 2, 6:39 am, PhistucK <phist...@gmail.com> wrote:
> Yes, unfortunately, that was a highly annoying bug that also affected
> YouTube videos/Google advertisements and other iFrames in Google Reader (for
> example) since the birth of Chrome.
> I assume you are using the stable version of Chrome.
>
> But, hey, fear not, the salvation is near!
> There is a fix for this in Chrome 14 (currently in beta). :)
> It should be released as stable within a few weeks.
>
> The tracking issue for this was -
> crbug.com/73460
>

> ☆*PhistucK*

> > Chromium Discussion mailing list: chromium-disc...@chromium.org