how to use nginx to solve cross-domain problems. The interface ends with .do, and how to solve cross-domain problems through nginx
server {
listen 80;
server_name localhost;
location ~* (\.do)$ {
//
}
} server {
listen 80;
server_name localhost;
location ~* (\.do)$ {
add_header Access-Control-Allow-Origin *;
add_header Access-Control-Allow-Methods 'GET, POST, PUT, DELETE, OPTIONS';
add_header Access-Control-Allow-Credentials 'true';
add_header 'Access-Control-Allow-Headers' 'Accept, Authorization,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
if ($request_method = 'OPTIONS') {
add_header 'Access-Control-Allow-Origin' *;
add_header 'Access-Control-Max-Age' 1728000;
add_header 'Access-Control-Allow-Credentials' 'true';
add_header 'Access-Control-Allow-Methods' 'GET, POST, DELETE, PUT, OPTIONS';
add_header 'Access-Control-Allow-Headers' 'Accept, Authorization,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
add_header 'Content-Type' 'text/plain charset=UTF-8';
add_header 'Content-Length' 0;
return 204;
}
}
}server {
listen 80;
server_name localhost;
location ~* (\.do)$ {
proxy_set_header Host $host;
add_header 'Access-Control-Allow-Origin' '*';
add_header 'Access-Control-Allow-Credentials' 'true';
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
} Cross-domain problems should not be solved in nginx, and rough addition of set_header will cause problems. Nginx will not verify these set_header , but will cause some problems that are easy to confuse browsers.
Cross-domain problems must be solved in the background, and the back-end framework must be able to deal with cross-domain problems. Let the developer change the code
Previous: Does the vue development environment build not work?
Next: Angularjs ui-rote window cannot be loaded after naming
1, is accessible for static pages when I configure only static directories. when doing development, the server port is 8999, and the project port is 3000. now deploy to linux, do a simple proxy with nginx 2, only set location { root html; ...
nginx configuration upstream mall { server 127.0.0.1:4000; } server { listen 80; server_name www.a.com; rewrite ^(.*) https: $host$1 permanent; } server { listen 443; server_name www.a.com; -sharp ssl on; ssl_certificate cert 1_www.a.com_bundl...
nginx manages static pages, and then forwards requests for data pages to nodejs, why you can only get index.html? how should the page data request be forwarded to the nodejs--8080 port? there should be no need for a firewall to open it worker_proce...
An API service I built myself uses https. The get request parameter of a user is too long, and then the browser cannot access it directly. After shortening the parameters in url, you can. the server uses nodejs local test parameters that can be handled...
locally modified host, such as 127.0.0.1 www.xxx.com node starts a service on port 8080, proxies to port 80 through nginx, and accesses the wwww.xxx.com development project locally then something happened. The operator provided a page wwww.xxx.com ...
vue project needs to be published by node and nginx , but there are some problems that are not very clear. I d like to ask you: requirements: currently there is only one front-end server, so node and nginx are all installed together, and the...
server { listen 80; server_name localhost; -sharpcharset koi8-r; -sharpaccess_log logs host.access.log main; location { proxy_pass http: localhost:8080; } location apis { ...
after pm2 starts the service, the port number must be added after accessing with www. .com. How to hide the port number, only the domain name www. * .com is displayed....
what if both domain name and IP can run independently, but the agent can t get up? How to match this nginx.conf file? ...