Originally Posted by ggalan
could you explain your technique further please
alright, here we go:
inside a loader swf that does get cached:
new URLRequestHeader("Cache-Control", "no-store, no-cache, must-revalidate");
var swfloader:Loader = new Loader();
//this phploader file is what outs your flash file
//it outputs binary data
//theres alot more to it than that for more security
//but this answers in general your original question
var request:URLRequest = new URLRequest("phploader.php");
var headers:Array = new Array(nocache);
request.requestHeaders = headers;
request.method = URLRequestMethod.POST;
goto my site actiontad.com and try to load tadspingpong.swf
you'll get a blank swf,
however that is the call to the ping pong game in examples
it is the loader swf that loads the real swf file
in a similar (more complex) manner as what I am describing here
header("Cache-Control", "no-cache, no-store, must-revalidate");
now this can get very involved, but generally speaking, a swf loaded this way will not get cached.
lets get deeper a bit:
ie has whats known as a secret cache,
(so Iv'e been told)
Responses from the server can be kept there even if no cache headers where sent. (i've never seen this happen to a swf outed in the above way)
A person with a packet sniffer can still get your swf files rather easily if you just use a simple method as defined above.
The key to besting a sniffer is breaking up packets, but that is more than i will get into here and now.
I hope you can get a good idea of what i'm talking about, if not, just know that in general no matter what you do, things (code) on the web can and will be seen.