Local cross-domain configuration is practical: proxy, local test cross-domain has no problem, the data can be accepted normally, and the background can console
"/api": {
"target": "http://132.232.22.140:8889/api",
"changeOrigin": true,
"pathRewrite": { "^/api" : "" }
}
after deployment to the server, nginx configuration
server {
listen 8000;
-sharp server_name www.alatu..xyz;
root /home/myftp/dist;
index index.html index.htm;
location / {
try_files $uri $uri/ /index.html;
}
location ^~ /assets/ {
gzip_static on;
expires max;
add_header Cache-Control public;
}
location /api {
rewrite ^.+api/?(.*)$ /$1 break;
include uwsgi_params;
proxy_pass http://localhost:8889;
}
error_page 500 502 503 504 /500.html;
client_max_body_size 20M;
keepalive_timeout 10;
}
online tests do not receive data, and there is no console in the background. I am not very grateful for the help of my predecessors.