I moved the SWF to the same server as the data source, and it is still
erroring. Also, I pass a cache buster and have the following cache
control headers in the PHP scripts:

Header('Cache-Control: no-cache'); 
Header('Pragma: no-cache');

Still no dice. 

Thanks for the response, I appreciate it. :)

-- William

--- In [email protected], "Richard Rodseth" <[EMAIL PROTECTED]> wrote:
>
> Could be the cache issue. Try PHP equivalent of:
> 
>         response.setHeader("Cache-Control", "max-age=0,
must-revalidate");
> 
> On Nov 29, 2007 7:29 AM, Abyss Knight <[EMAIL PROTECTED]> wrote:
> 
> >   I'm getting a 2032 Stream error in IE6, and only in IE6. It works in
> > IE7, FF2, and even Safari but not in IE6. I have a crossdomain file on
> > the target server, and I have done a Security.allowDomain('*') as
> > well. Anyone have any idea why this would be happening? Somehow this
> > past QA, so I need to get it fixed pretty quick. ;) I'm sure you all
> > know how that goes. Anyways, here's the error details:
> >
> > (mx.messaging.messages::ErrorMessage)#0
> > body = (Object)#1
> > clientId = "DirectHTTPChannel0"
> > correlationId = "86375043-9D26-EB56-F2BD-8BF26D5633AC"
> > destination = ""
> > extendedData = (null)
> > faultCode = "Server.Error.Request"
> > faultDetail = "Error: [IOErrorEvent type="ioError" bubbles=false
> > cancelable=false eventPhase=2 text="Error #2032: Stream Error. URL:
> > http://myurl.com/myfile.php?var=3333";]. URL:
http://myurl.com/myfile.php";
> > faultString = "HTTP request error"
> > headers = (Object)#2
> > messageId = "5956F03D-F7C2-81A0-4E32-8BF26E70038B"
> > rootCause = (flash.events::IOErrorEvent)#3
> > bubbles = false
> > cancelable = false
> > currentTarget = (flash.net::URLLoader)#4
> > bytesLoaded = 0
> > bytesTotal = 0
> > data = (null)
> > dataFormat = "text"
> > eventPhase = 2
> > target = (flash.net::URLLoader)#4
> > text = "Error #2032: Stream Error. URL:
> > http://myurl.com/myfile.php?var=3333";
> > type = "ioError"
> > timestamp = 0
> > timeToLive = 0
> > [object HTTPService]
> >
> >  
> >
>


Reply via email to