Comments on: Debugging crossdomain issues: Following HTTP 302s

By: Jason

Jason — Fri, 07 May 2010 08:12:44 +0000

Brilliant. Thanks for the matching URLs and LoaderContext tip. Saved me a lot of debugging time.

By: zenMonkey

zenMonkey — Wed, 15 Apr 2009 20:05:12 +0000

Thank you for this post – very helpful. I’ve applied it and found that sometimes the img_bmp assign will succeed the try, but then is still null. I’ve worked around this by continually loading original URL until bitmap is non-null. Odd…

private function onLoadComplete(event:Event):void
var img_bmp:Bitmap;
try{
img_bmp = Bitmap(loader.content)// as Bitmap;
}catch(e:Error){
trace(’Cannot access bitmap of image due to crossdomain issues’);
if (loader.contentLoaderInfo) {
load(loader.contentLoaderInfo.url);
}
return;
}
if (img_bmp == null){
if (loader.contentLoaderInfo != null) {
if (loader.contentLoaderInfo.url != null){
load(loader.contentLoaderInfo.url);
}else{
load(imgSrc);
}
}
return;
}
}

By: Gabe Robinson

Gabe Robinson — Thu, 12 Feb 2009 17:43:18 +0000

Had a very similar problem. It would be nice if flash would let you see that the url has changed before the complete handler is triggered.

The help docs say “After the first progress event, the url property reflects the media’s final URL, after any redirects and relative URLs are resolved.”, but if you try to get the url in a progress event listener it throws and error (Error #2099: The loading object is not sufficiently loaded to provide this information).

So since like you concluded we can not get the url until the complete handler, i am loading images twice like you

By: Kevin Fitzpatrick

Kevin Fitzpatrick — Wed, 02 Jul 2008 23:06:26 +0000

Yay 302 weirdness. I found another weird (read: inconsistent between browsers) behavior for you with the Flash Player and 302/303s. Blog to come soon.