Detailed explanation for solving the problem of cross-domain access to nginx/apache static resources

1. Cross-domain access to apache static resources

Locate the apache profile httpd.conf

Find this line.

# LoadModule headers_module modules/mod_headers.so

Remove the # comment character

LoadModule headers_module modules/mod_headers.so

The purpose is to open the apache header information customization module

Add header to the standalone host configuration file

Header set Access-Control-Allow-Origin *

For example:

ServerAdmin admin@example.com DocumentRoot "*" ServerName www.jb51.com Header set Access-Control-Allow-Origin * ErrorLog "*" CustomLog "* *" common SetOutputFilter DEFLATE Options FollowSymLinks ExecCGI Require all granted AllowOverride All Order allow,deny Allow from all DirectoryIndex index.html index.phpApacheCopy

It means to add a header information when accessing the resources of this domain name.

Restart apache

Service httpd restart

2. Nginx static resources allow cross-domain access

Similarly, find the appropriate domain name profile

Add a configuration to the server module:

Add_header 'Access-Control-Allow-Origin'' *'

Example:

Server {listen 80; add_header 'Access-Control-Allow-Origin'' *'; location / Roboto/ {root / home/images; autoindex on;}}

Nginx overload

. / nginx-s reload

Once configured through the above methods, there will be no problem for cross-domain access to static resources again.

The above is the solution to allow cross-domain access to nginx/apache static resources.