im sorry, having a hard time unsubscribing from this mail list. Anyone have any advice? Ive been to the apache page, unsubscribed, but I am still getting emails.
On 10 April 2015 at 08:11, James M. Greene <[email protected]> wrote: > Correction, that should have read: > > Are your *HTML page* and SWF file both being retrieved via the same > protocol (i.e. "http://" vs. "https://")? They need to be, unless you do > go ahead and use `Security.allowInsecureDomain(...)`. > > Sincerely, > James Greene > > > On Fri, Apr 10, 2015 at 10:10 AM, James M. Greene < > [email protected]> > wrote: > > > Are your JS and SWF file both being retrieved via the same protocol (i.e. > > "http://" vs. "https://")? They need to be, unless you do go ahead and > > use `Security.allowInsecureDomain(...)`. > > > > Sincerely, > > James Greene > > > > > > On Fri, Apr 10, 2015 at 7:33 AM, piotrz <[email protected]> > wrote: > > > >> I am reading about that on the other forums and some folks are pointing > >> that > >> it could be some kind of security issues. > >> > >> My application is behind https domain, both js file which is trying to > >> communicate with my swf are in the same domain. > >> > >> I see that at the initialization of app someone use these two lines: > >> > >> Security.allowDomain("*"); > >> Security.allowInsecureDomain("*"); > >> > >> Documentation is saying that we shouldn't use "allowInsecureDomain" for > >> communication between HTTPS files - This is probably my case. - Could > this > >> cause in some way my errors because these two methods has been used at > the > >> same time ? > >> > >> "Do not use this method to enable scripting between non-HTTPS files, > >> between > >> HTTPS files, or from HTTPS files to non-HTTPS files." > >> > >> Piotr > >> > >> > >> > >> ----- > >> Apache Flex PMC > >> [email protected] > >> -- > >> View this message in context: > >> > http://apache-flex-users.2333346.n4.nabble.com/Flex-JS-Error-calling-method-on-NPObject-tp10044p10048.html > >> Sent from the Apache Flex Users mailing list archive at Nabble.com. > >> > > > > >
