Read the statement by Michael Teeuw here.
Cached pictures in iFrame
-
@mykle1 The problem is that it’s not my images. The images are provided by a 3rd party. Any changes would have to be on the MM.
-
@bkeyport the server side doesn’t know you sent this extra parm but it makes the url unique, so fetch thinks it has to get it
-
@sdetweil Oh, so I’d be modifying the code to mmm-iframe to add the timestamp?
-
@bkeyport the url into the iframe, where ever the things is would want to change
url http://someserver/somepath/somefile.img
over and over the browser say,s OH thats the same, no need to load it, got a copyurl http://someserver/somepath/somefile.img?time=1
url http://someserver/somepath/somefile.img?time=2
url http://someserver/somepath/somefile.img?time=3
url http://someserver/somepath/somefile.img?time=4they are all different, so the browser reloads… the web server gets the extra parm, but doesn’t use it.
-
I thought I said that. :-)
-
@bkeyport said in Cached pictures in iFrame:
Oh, so I’d be modifying the code to mmm-iframe to add the timestamp?
I gave you an example bro. :-/
-
@mykle1 I’m trying to understand how to use the example, bro. 😉
Not so good with partial code.
-
Got it working guys, thanks for your help, I’ve created a merge request with Mr. Wong as well.
If anyone else runs across the thread, and it’s still not merged, my code mods are:
-
@bkeyport said in Cached pictures in iFrame:
I’m trying to understand how to use the example, bro.
Been there. I only knew because I came across the same issue and didn’t know what to do, too. You’ll notice that I stated that Sean and Strawberry taught me the solution.
Anyway, it looks like you worked it out.
Good on ya, mate! :thumbsup: