There is no way to make this work. Unless, the foreign domain you try to access supports a procedure like C.O.R.S, JSONP or postMessage.
There are a few exceptions (like always):
If you're dealing with a WebApp for instance, you can tell your users that they have to grant access to cross-domain-calls
.
In Gecko/Firefox for instance, you can call
netscape.security.PrivilegeManager.enablePrivilege('UniversalBrowserRead')
which enables the browser to access foreign domains via ajax/iframes
. In this scenario, an user has to set
signed.applets.codebase_principal_support
to true
under about:config
to make this work.
In the Internet Explorers
of this world, there is a setting called something like allow cross-domain access
deeply hidden in the security
tab, which must be set to enable
.
Chrome
allows cross-domain calls with a commandline argument:
chrome.exe --disable-web-security
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…