


javascript - What are the methods of cross-domain implementation?
1. Through IFRAME
2. Through JSONP
3. Set http header, Access-Control-Allow-Origin:*
4. Server proxy
5. nginx reverse proxy to achieve cross-domain
Anything to add?
Reply content:
1. Through IFRAME
2. Through JSONP
3. Set http header, Access-Control-Allow-Origin:*
4. Server proxy
5. nginx reverse proxy to achieve cross-domain
Anything to add?
How can we not have PHP’s powerful tool class, curl. How perfect can we achieve with this
<code>window.name</code>
Set Access-Control-Allow-Origin:* should belong to CORS
Use window.navigator
for cross-domain
This solution can only be used in ie6 and ie7
because there is a bug in ie6 and ie7. That is, the navigator
of the parent page and the child page are shared.
General solutions are postMessage
, <code>window.name</code>, window.navigator
.
postMessage
is used in standard browsers.
<code>window.name</code> and window.navigator
are used in ie
, but the implementation of <code>window.name</code> must regularly check whether name
has changed, while navigator
does not exist.
feature detection
The priority is postMessage, navigator, name.
See the picture below:
The mainstream ones include cors, HTML5 postmessage, josnp, and server proxy
I happened to see a summary: Front-end cross-domain and its solutions

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



How to fix Nginx 403 Forbidden error? Check file or directory permissions; 2. Check .htaccess file; 3. Check Nginx configuration file; 4. Restart Nginx. Other possible causes include firewall rules, SELinux settings, or application issues.

The server does not have permission to access the requested resource, resulting in a nginx 403 error. Solutions include: Check file permissions. Check the .htaccess configuration. Check nginx configuration. Configure SELinux permissions. Check the firewall rules. Troubleshoot other causes such as browser problems, server failures, or other possible errors.

Steps to start Nginx in Linux: Check whether Nginx is installed. Use systemctl start nginx to start the Nginx service. Use systemctl enable nginx to enable automatic startup of Nginx at system startup. Use systemctl status nginx to verify that the startup is successful. Visit http://localhost in a web browser to view the default welcome page.

Answer to the question: 304 Not Modified error indicates that the browser has cached the latest resource version of the client request. Solution: 1. Clear the browser cache; 2. Disable the browser cache; 3. Configure Nginx to allow client cache; 4. Check file permissions; 5. Check file hash; 6. Disable CDN or reverse proxy cache; 7. Restart Nginx.

How to configure Nginx in Windows? Install Nginx and create a virtual host configuration. Modify the main configuration file and include the virtual host configuration. Start or reload Nginx. Test the configuration and view the website. Selectively enable SSL and configure SSL certificates. Selectively set the firewall to allow port 80 and 443 traffic.

How to confirm whether Nginx is started: 1. Use the command line: systemctl status nginx (Linux/Unix), netstat -ano | findstr 80 (Windows); 2. Check whether port 80 is open; 3. Check the Nginx startup message in the system log; 4. Use third-party tools, such as Nagios, Zabbix, and Icinga.

The methods to view the running status of Nginx are: use the ps command to view the process status; view the Nginx configuration file /etc/nginx/nginx.conf; use the Nginx status module to enable the status endpoint; use monitoring tools such as Prometheus, Zabbix, or Nagios.

The error log is located in /var/log/nginx (Linux) or /usr/local/var/log/nginx (macOS). Use the command line to clean up the steps: 1. Back up the original log; 2. Create an empty file as a new log; 3. Restart the Nginx service. Automatic cleaning can also be used with third-party tools such as logrotate or configured.
