Im currently seeing the same issue, however, in completely reverse. As of this moment, a0 & a1 are not allowing other domains and a2 & a3 are allowing all domains.
The other day, all 4 were not allowing other domains. Is there any reason or rhyme for this and more importantly, what is the expectation? Are we supposed to be able to make calls from Flash for profile images or not? On Nov 28, 3:57 pm, stephen <[email protected]> wrote: > Hey, > > It appears the crossdomains for a2, a3, etc are different and are > preventing flash from accessing profile images on these domains. a0 > and a1 are fine, however the api returns profile image urls using all > of these domains (a0 - a?). > > Are the crossdomains suppose to be all the same or are we suppose to > target only the first two? From the few that I've tested, it seems > all profile images are accessible through the a0 or a1 domains despite > what the api returns. > > Crossdomains > > http://a0.twimg.com/crossdomain.xmlhttp://a1.twimg.com/crossdomain.xmlhttp://a2.twimg.com/crossdomain.xmlhttp://a3.twimg.com/crossdomain.xml > > Stephen -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
