Cross domain access solution flex summary

Recommended for you: Get network issues from WhatsUp Gold. Not end users.

In fact, the solution of online information are many, is to add a policy file crossdomain.xml, this paper is to introduce how to add this file.

The contents of the crossdomain.xml file (* part themselves according to the need for configuration):

<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "">
    <allow-access-from domain="*"/>
    <allow-http-request-headers-from domain="*" headers="*"/>


First of all, clear, A application to request a B application resources, this strategy document is to be added to the B application, at the beginning, read some posts that are to be added to the A application, mislead me for a long time.


Below is the text

Configuration of 1.tomcat server is very simple, directly to the file into the webapps/ROOT Tomcat webapps, the premise is to guarantee the full directory structure


The 2 is mainly about Weblogic (my version is 12C) configuration, a bit of trouble, the final success is tested repeatedly measured, specific principle I do not really understand.

1)Add a default application of C to the B application server where,

That is as long as the input application behind the http://xxxx:7001/ do not need to add project context can access. My approach is configured by a server console, the later again.

Create a new index project,






A blog add the weblogic.xml file in the index project under the root directory, the content is set to

<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1
//EN" "">


But I tried without success, so I directory so simple, attached file content, is very simple:


<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
" "">
<web-app id="WebApp_ID">



2)Configure the server default application In the Weblogic console, Admin Console -> Servers -> DefaultServer (AdminServer) -> Protocols -> HTTP -> Default WebApp Context Root: Web Java EE modified for application of Web Context Root (here is the project name index), Preservation, No need to restart Weblogic.
But in the actual situation in my, I feel very pit but very important point is the key point is, Each time the operation of the index project, For example, update start stop fell again even reboot the Weblogic, Configure default application to operate again, Even if the default application is index, You need to put it to null, Preservation, Then fill, Then save, Otherwise, You are not using http://xxxx:7001/ to access index applications, The result would be 404, While http://xxxx:7001/index can.
I don't understand the principle of Weblogic, also did not know that what is a BUG or my own problem, later study slowly.
3)As above, if the default application can normal visit, then invoke the B application to the A application, nature also can be successful, otherwise, it will offer you encounter "sandbox security conflict" error


Reference material:













































Recommended from our users: Dynamic Network Monitoring from WhatsUp Gold from IPSwitch. Free Download

Posted by Gaby at December 07, 2013 - 6:39 PM