1 Reply Latest reply on Oct 18, 2012 2:14 PM by JoshBeall

    Using RSLs results in a mixed content warning in Chrome?  When did this start happening?

    JoshBeall

      Hello All,

       

      We've got a secure (delivered via HTTPS) Flex app that has been using RSLs for years.  Just today, I noticed that Chrome was showing a "mixed content" warning for our app.

       

      screenshot.png

       

      We're not getting this same warning in IE or Firefox.  I poured over the requests in Chrome's developer tools, and there were only two HTTP requests:

       

      http://fpdownload.adobe.com/pub/swz/crossdomain.xml

      http://fpdownload.adobe.com/crossdomain.xml

       

      These both appear related to the Adobe hosted Flex RSLs.

       

      I changed my compilation options to merge libraries into code (no RSLs).  As soon as I did this, the mixed content warning in Chrome went away (and so did these two HTTP requests).  Switch back to RSLs, and the mixed content warning comes back (along with the two HTTP requests).

       

      Turning off RSLs makes my app quite a bit fatter--over 600kb fatter.  That's a lot.  I want to use RSLs, like we've been doing in the past!  How can this be fixed?

       

      Chrome Version: 22.0.1229.94 m

      Flash Player Version: 11.4.31.110

      OS Version: Windows 7, 64 bit

      Complete User-Agent string:

      Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4