Ok, so I narrow down the scope : In fact I have three crossdomain.xml file one is the root :
<cross-domain-policy> <site-control permitted-cross-domain-policies="all"/> </cross-domain-policy> and two others in 2 different virtual directory for the webservices with that : <cross-domain-policy> <allow-http-request-headers-from domain="*" headers="*" secure="false" /> <allow-access-from domain="*" secure="false"/> </cross-domain-policy> What seems to happening is that in HTTPS, the crossdomain policy of the virtual directory are not loaded. So I'm not sure if its an IIS rediredtion problem or a crossdomain issue. Addind this tags : <allow-http-request-headers-from domain="*" headers="*" secure="false" /> <allow-access-from domain="*" secure="false"/> to the root crossdomain file make all works fine but it's not a good solution. Benoît Milgram / Flapflap http://www.kilooctet.net I'm also a music mashup / bootlegs producer : http://www.djgaston.net On Thu, Aug 13, 2009 at 5:36 PM, Flap Flap <flapflapl...@kilooctet.net>wrote: > Hi all, > > I have an IIS server that can serve both http and https webservice. > I must access webservice from local swf file to both protocol. > So I have my crossdomain.xml like that : > > - <#123146758b920521_> <cross-domain-policy> > <allow-http-request-headers-from domain="***" headers="***" secure="* > false*" /> > <allow-access-from domain="***" secure="*false*" /> > </cross-domain-policy> > > Which works fine in HTTP (despite it's says that it will ignore the secure > false) but doesn't in HTTPS. > If I use IE to watch the files I get both of them (in HTTP / HTTPS) > > Any clue ? > > Thanks > > Benoît Milgram / Flapflap > http://www.kilooctet.net > > I'm also a music mashup / bootlegs producer : > http://www.djgaston.net >