Take the 2-minute tour ×
Stack Apps is a question and answer site for apps, scripts, and development with the Stack Exchange API. It's 100% free, no registration required.

I am implementing a javascript client that uses the Flash based XHR replacement Flensed in the interest of providing more robust api communication than that provided by JSONP.

Apparently the current flash version does not like the current crossdomain.xml.

The only difference I can see between a policy file that works with Flensed, thus Flash 10, is the inclusion of the xml directive and doc-type. In other words, a semantically correct crossdomain xml file.

Can we deploy the proposed version of crossdomain.xml on stackauth and all api endpoints?

Current:

   <?xml version="1.0" encoding="UTF-8"?>
   <cross-domain-policy>
      <allow-access-from domain="*" />  
      <site-control permitted-cross-domain-policies="master-only"/>  
    </cross-domain-policy>

Proposed:

    <?xml version="1.0"?>
    <!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
    <cross-domain-policy>
      <allow-access-from domain="*" />  
      <site-control permitted-cross-domain-policies="master-only"/>  
    </cross-domain-policy>
share|improve this question
    
Given the official Cross-domain policy file specification (and the fact that it isn't working correctly currently) I'd qualify this as a bug actually (have retagged accordingly). –  Steffen Opel Oct 2 '10 at 12:08
add comment

1 Answer 1

up vote 1 down vote accepted

These are rolling out, and should be on all API and StackAuth instances soon-ish.

share|improve this answer
1  
stackauth.com/crossdomain.xml & stackauth.com/1.0/crossdomain.xml are either lagging update or were missed. these are actually the most critical of the bunch. –  Sky Sanders Oct 12 '10 at 11:16
add comment

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .