1. is there any supplement to cross-Origin through IFRAME2, JSONP3, http header setting, Access-Control-Allow-Origin: * 4, server proxy 5, and nginx Reverse proxy? 1. IFRAME
2. through JSONP
3. set the http header, Access-Control-Allow-Origin :*
4. server proxy
5. implement cross-origin through nginx Reverse proxy
Are there any other supplements?
Reply content:
1. IFRAME
2. through JSONP
3. set the http header, Access-Control-Allow-Origin :*
4. server proxy
5. implement cross-origin through nginx Reverse proxy
Are there any other supplements?
PHP powerful tool class, curl. use this to achieve perfection
window.name
Set Access-Control-Allow-Origin: * it should belong to CORS
Usewindow.navigator
Cross-Origin
This solution can only be used in ie6 and ie7.
This is because there is a bug in ie6 and ie7. Is the parent page and child pagenavigator
Is shared.
The general solution ispostMessage
,window.name
,window.navigator
.
postMessage
Is used in standard browsers.
window.name
Andwindow.navigator
Yesie
,window.name
Must be checked regularly.name
Change or not, andnavigator
This does not exist.
feature detection
The priority is postMessage, navigator, and name.
See:
Mainstream include cors, HTML5 postmessage, josnp, and server proxy.
Here is a summary: frontend Cross-Origin and its solution.