Post the policy file (eg, crossdomain.xml). Wouldn't this file need to know about the proxy server? If so, I am not sure why it works sometimes.
Hello, my crossdomain.xml file is as follows:
<?xml version="1.0"?> <cross-domain-policy> <allow-access-from domain="*" /> </cross-domain-policy>
I don't think that the crossdomain should know about the proxy server. The proxy that i'm saying is in the client side. If, for example, a company has a Squid server which the machines use as proxy, do you understand?
I'm lost about what should i do, i googled a lot with no helpful answers.
Thanks for your reply, regards.
Look into the allow-http-request-headers-from tag. This would go between your cross-domain-policy tags. I just now discovered this tag, it seems relevant to your issue.
I will be watching the following video after I post this:
And yes, I now believe I understand the situation with your proxy server. You are saying that the SWF is downloaded from the proxy server? If so, then the wildcard should be fine.
I just came across this:
"For example, the
FileReference.download()methods do not support the
requestHeadersproperty of the URLRequest object is ignored; custom HTTP request headers are not supported in uploads or downloads.
The URL can be HTTP or, for secure uploads, HTTPS. To use HTTPS, use an HTTPS url in the
urlparameter. If you do not specify a port number in the
urlparameter, port 80 is used for HTTP and port 443 us used for HTTPS, by default.
GETparameters to the server, set the
dataproperty of the URLRequest object to your parameters, and set the
methodproperty to either
Also in the API description for FileReference.upload(), they mentioned about using the
uploadDataFieldName parameter for POST operations. So you can try that or inserting data in that parameter or the URLRequest.data property.
I hope that helps, lets us know what you discover.
Hello, thank you for your answer. I don't think that the trouble should be in the URLRequest, as in many other cases the upload works, but i took a look in it without success. I added the crossdomain entries that you said, and i got it working in IE, but in Chrome it keeps throwing the IOError...
This is not the first problem that i find in Flash regarding specific browsers, i think that Flash should be fully "crossbrowser" shouldn't it?
Yes, I agree that Flash Player should be consistent regardless of the browser its in. And perhaps it is. But if you are using the URLRequest.requestHeaders to do a POST operation with FileReference, then your risks are high. As its documented not to use the requestHeaders property in this situation. So the results may be sporadic and perhaps that is what you are experiencing.
I have discovered after watching that video, that the allow-http-request-headers-from tag in the crossdomain policy file seems beneficial IF you are using custom headers. So I don't think adding this tag to your crossdomain file will rectify your problem.
What does your code look like now? Did you remove the code for the requestHeaders?
it's a bug in the version of flash that ships with chrome. try installing a different (non-beta) version of chrome, it should work fine.
this really sucks. now we have to tweak our flash version detection libraries to exclude specific versions of chrome? great...