Hi Stephen, hi Douglas, thanks for your replies.
I tried Douglas' approach to load the WSDL-files from a http source with no success. Then I installed a HTTP-Request monitoring tool in Firefox and in IE6 and had a look at the HTTP request heads which will be done when Flash tries to load the WSDL files. I figured out that the Firefox/Flash combination sends a jsession cookie and a basic authentication and the IE6/Flash doesn't. A quick look into google showed me there seem to be several problems with this session id issue ( i.e. FileUpload in FF ). It was suggested to append the session id to the URL. I tried that but in my installation the appended URL had no effect, the additional url information is not recognized. As a consequence it seems I have to add somehow the session id cookie information to the requests flash does. Unfortunately I don't know how to do this. My webservices are configured by the <mx:Webservice /> tag, I tried to create my Webservice in AS but had no luck. If I got it right I'm not able to use the WebserviceProxy because the webservice is individual for each user so I can't use a technical user for the webservice. The last problem is I use a webservice to get the user credentials... I wonder if there is a official documentation about that issue because the scenario FLEX-Application calls Webservice on same server which is secured by basic authentication should not be very exotic. Any more thoughts? Regards, Christoph Zitat von Stephen Allison <[EMAIL PROTECTED]>: > Christoph Guse writes: > >> Hi Douglas, >> >> thanks for your reply. I can switch off https for testing purposes, but >> it is impossible to switch off https in the production environment. So >> your approach can't be the final solution. >> >> I'll try to switch off https tomorrow and will see what happens. >> >> Any more ideas? > > There's a fairly well documented problem when loading data over HTTPS into > the Flash Player when running in IE if the response contains cache-control > headers. If these are set to Cache-Control: no-cache then the browser loads > the data but the Flash player never gets to see it, so you could try seeing > if these headers are being sent and disable them or alter them if they are - > you should be able to find people's solutions with a quick Google. > > There can also be problems in IE with HTTPS if the content is gzipped by the > server, depending on IE settings - the "do not save encrypted data" setting > under internet settings/advanced/security seems to have some effect here. > > Good luck! > Stephen >
