RPC fault string=Security error accessing url

Ask a Question related to Macromedia Flex General Discussion, Design and Development.

  1. #1

    Default RPC fault string=Security error accessing url

    Hi Guys,

    My app's been online for some time now (over a month) and I've logged in today
    and noticed the attached error which has appeared out of the blue (I haven't
    logged in to it for a couple of weeks but everything was working fine). Any
    idea as to what sort of problem the application's having?

    Thanks

    Here is the error:
    [url]http://s299.photobucket.com/albums/mm312/thedigit/?action=view&current=error.jpg[/url]

    mac_55 Guest

  2. Similar Questions and Discussions

    1. security error accessing url
      I'm using flex builder to create a small flex project to learn how to call web service in flex,but I encountered a problem really confusing me.I...
    2. #39304 [NEW]: Segmentation fault with list unpacking of string offset
      From: dave at ramenlabs dot com Operating system: Linux PHP version: 5CVS-2006-10-30 (CVS) PHP Bug Type: Reproducible crash...
    3. HTTPService: Security error accessing url
      I have the following code in my Flex 2.0 application. Basically I'm trying to send a HTTP request to a remote computer with Cocoon installed. The...
    4. Error: code:Channel.Security.Error string:'Security
      Flex 2.0 beta 1 I created an mxml application with the following tag: <mx:WebService id="ws"...
    5. Using Integrated Security for Accessing SQL on Remote Server
      Hello, I am currently trying to use integrated security to access the SQL database for the ASP.NET application (deployed on an intranet) I am...
  3. #2

    Default Re: RPC fault string=Security error accessing url

    Oddly, I've just installed Flash Player version 9,0,115,0 and it seems to work fin in there, no errors.

    Hrm. Any ideas?
    mac_55 Guest

  4. #3

    Default Re: RPC fault string=Security error accessing url

    Generally when something is labeled as a Security error with flash it relates
    to the crossdomain.xml file. The first thing I'd check is all of the services
    being used to bring in data are coming from places that are allowed within the
    crossdomain.xml file. An easy way to test this would be to allow everything
    within the crossdomain.xml, test it to see if you get the same error, if you
    don't then you know the problem belongs there, if you do get the same error
    then the problem lies in something deeper like maybe your application cannot
    currently find your crossdomain.xml to even check the policies? Just a thought.

    Kaotic101 Guest

  5. #4

    Default Re: RPC fault string=Security error accessing url

    Where should the crossdomain.xml be placed? I have it in the root of the webserver's web directory
    mac_55 Guest

  6. #5

    Default Re: RPC fault string=Security error accessing url

    FlashPlayer 9.0.124 has increased restrictions with its security model.
    For URL based access (FlashLoader) you need the crossdomain.xml in the server
    root. For socket based access you need a socket policy file and a policy file
    server (assumingly).

    I haven't been able to get the latter working. See my cry for help here:

    [url]http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=60&catid=58[/url]
    5&threadid=1360744

    Adobe has more info here:
    [url]http://www.adobe.com/devnet/flashplayer/articles/fplayer9_security.html[/url]



    SalmonArm Guest

  7. #6

    Default Re: RPC fault string=Security error accessing url

    I'm not sure if I need a socket policy file, I'm using web services...?
    mac_55 Guest

  8. #7

    Default Re: RPC fault string=Security error accessing url

    Try changing your crossdomain.xml file to the following for a quick test. It
    will allow access to everything. Once you've changed that, refresh your
    application and tell us if the web services still throw a security error, if it
    does not throw a security error then you do not need the socket policy file you
    just need to fine tune your crossdomain.xml access rights for your application.
    Having the crossdomain.xml inside of your web root is the right place for it.

    <?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="*" />
    </cross-domain-policy>

    Kaotic101 Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139