« Return to the blog entry
Ah. That explains some odd behaviour I was seeing.
Do you remember if the problem was with Flash player 9 and/or 10? I think v10 sorts a lot of this out.
One idea I did have was to pass the Cookie part of the URL request the Domino session values. Something like this:
var credsHeader:URLRequestHeader = new URLRequestHeader("Cookie", parentApplication.parameters.AuthType+"="+
parentApplication.parameters.AuthToken
);
urlRequest.requestHeaders.push(credsHeader);
The idea being it replaces the cookies that Flash is sending from IE with our own more trustworthy ones.
Do you know if that would work?
Ah. That explains some odd behaviour I was seeing.
Do you remember if the problem was with Flash player 9 and/or 10? I think v10 sorts a lot of this out.
One idea I did have was to pass the Cookie part of the URL request the Domino session values. Something like this:
var credsHeader:URLRequestHeader = new URLRequestHeader("Cookie", parentApplication.parameters.AuthType+"="+
parentApplication.parameters.AuthToken
);
urlRequest.requestHeaders.push(credsHeader);
The idea being it replaces the cookies that Flash is sending from IE with our own more trustworthy ones.
Do you know if that would work?