I've got a flash swf file that pings a PHP script to request a file download.
The first time that the request is made to the PHP script, IE will display the "save as" dialog and save the file without a hitch.
However, the second time the request is made, IE blocks the download and displays the Information bar: "To help protect your security, Internet Explorer blocked the site from downloading the file to your computer."
I tried accessing the PHP script directly through the IE address bar, and the first, scond and third requests did not cause the Info bar to issue a warning. The info bar only pops out when the request is made through the SWF file, on the SECOND (or third) attempt -- even if the subsequent attempts use a unique URL.
It's odd because when the ping to the PHP page is made the first time, IE responds correctly, however, on subsequent attempts to download either the same file or a new file using the link in the SWF file, IE issues a warning.
One would think that IE would issue the warning on the first ping, not subsequent pings.
All the PHP header stuff is set up correctly, so it's not a PHP issue.
It's not a firewall issue (that was triple checked).
My gut tells me that IE is checking the actual URL to the PHP script - (sans query string)...
... and parsing just:
... and thinking to it's self, "this file [download.php] was already requested through Flash, I'm not going to let this file be requested through Flash again."
What could IE be doing to allow the first request, but block the second (and third) request either to the same file ID or a new file ID?
It doesn't make sense for a completely unique URL to somehow get interpretted or cached.