Forum user: yusufg

Far Future Expire header only works if the URL remains the same. A query string is considered as part of the URL in determining whether the object being requested is the same or not

I can understand if you want to put cache-busting into requests from within the swf, however the swf itself must be loaded from the same URL including any query string if you want to take advantage of any expire headers

Hi, I would like to benefit from standard HTTP cache behaviour.
That is, ask for the same url and observe the browser pick up the object from its cache.

However, I observe that when I use flashembed. It appends a querystring with a random number after the swf object

e.g

if I'm looking to retrievehttp://example.org/test.swf, when I observe the request/response via HTTPScoop or Fiddler or Firebug I see the following request

http://example.org/test.swf?0.75603134

I would like to understand why the random string is generated behind the scene.

Static Asset Versioning should be done by the web site designer via different mechanisms

Greetings, Have you any more insight on this issue ? What are you tending towards wrt multi-domain license

Regards, Yusuf

Hi, The restriction of the multidomain license being applicable only within one class C range seems to preclude serving the flv files from a CDN.

A CDN typically takes a subdomain (for example) flv.mydomain.com and returns appropiate IP's depending on the user connectivity. These can be in different netblocks

Can the flowplayer team provide some guidance for this use case ? or clarify the intent behind their multi-domain license