# FileReference download & redirects in IE (crossdomain woes)

**URL:** <https://forum.kirupa.com/t/filereference-download-redirects-in-ie-crossdomain-woes/298578>\
**Category:** flash\
**Created:** [October 21, 2009, 11:38am UTC](https://forum.kirupa.com/t/filereference-download-redirects-in-ie-crossdomain-woes/298578 "2009-10-21T11:38:10Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bombdogs](https://avatars.discourse-cdn.com/v4/letter/b/e68b1a/32.png) [@Bombdogs](https://forum.kirupa.com/u/Bombdogs)\
**Post date:** [October 21, 2009, 11:38am UTC](https://forum.kirupa.com/t/filereference-download-redirects-in-ie-crossdomain-woes/298578/1 "2009-10-21T11:38:10Z")

</div>

Hi all,

having a torrid time with this, please pitch in with _anything_ you feel might be relevant, much googling has turned up a big fat zero for me.

I have a flash app that uses the FileReference download method to serve up download links. Many of the links come from big content delviry networks and a crossdomain policy file is required to avoid a security error. This all works fine. Except for redirects in IE… in FF redirects work.

A typical Charles log in FF looks like this…

1. 302: download file temporarily moved
2. 302: download file found
3. 200: download file received OK
4. 200: crossdomain policy file received OK

In IE the Charles log looks like this…

1. 302: download file temporarily moved
2. 302: download file found
3. 200: client closed connection before receiving entire response

…the request for the crossdomain policy file is not being made in IE & thus flash blocks access to the download (client closed connection). The flash throws the traditional 2048 security error - which is what I’d expect if no crossdomain is available. It’s worth noting that downloads _without a redirect_ work fine in IE, the crossdomain is requested & received.

As far as I can make out there is no way to force “checkPolicyFile” with FileReference - it doesn’t take a LoaderContext object. I’m at a loss of what I can do to resolve this without putting a proxy on our webserver (the backend guru will not allow this as the downloads can be quite large & he thinks will end up being a huge bottleneck).

Given the differing behaviours in IE & FF, I’m putting this down to a bug in IE, which probably means I’m screwed right?

Thanks for reading.

PMF