Example of a cross-domain detailed code by nginx reverse agent

Example of a cross-domain detailed code by nginx reverse agent

Update: june 19, 2025 10:25:36 by: little dragon

Nginx as a reverse proxy that can easily resolve cross-domain issues at the front end without the need for back-end co-operation. The article focuses on the relevant information on nginx counter-agents for cross-domain solutions. It is very detailed by code and can be consulted by friends who need it. Down

Foreword

Nginx reverse proxy resolution cross-domain

I. Co-source strategy ii. What is the cross-domain

Cross-origin refers to the discrepancy between the domain name of the page currently being visited and the resource domain name requested in the browsing browser. Cross-domain issues arise, for example, when data are requested on ajax through ajax. Cross-domain problems usually occur in back- and back-end separation applications, and when the current and back-ends are deployed on different domains or ports, the browser prevents cross-domain requests for security reasons. The cross-domain is caused by the browser's co-source policy。

Iii. Nginx for cross-domain resolution

Nginx solves cross-domain problems through a reverse agent, which is operated directly in nginx directoryHTML, and you need to download nginx: https://nginx. Org/self-downline

1. Front-end illustrative code

The codes are as follows (example):

	
		= >It's called "view""width" is "device-width," "initial-scale" is "one."Click to get
		
		
		I'm sorry. I don't knowNclick =() =>
let's see. Console. Log (222);
note: we don't have a full backend address here: we just add one/api to the front.
/ / / port where to delete
xhr. Open (`get', '/api/user/all')
i don't know=()=
if (xhr. Readystate=4 & xhr. Status=200) {
(json. Parse (xhr. Responsetext))
♪ i'm sorry ♪
♪ i'm sorry ♪
xhr. Send()
♪ i'm sorry ♪I'm sorry

2. Description

This is the interface address on my back server: the port number is 5000, and my front page is the 80 port, so it causes cross-domain problems

Iv. Nginx reverse agent configuration

Configure the reverse agent, here/api/ must match the address of the front-end request interface。

Local/ api/
proxy pass http://127. 0. 0. 1: 5000/;
♪ i'm sorry ♪

V. Start nginx

Double click on nginx. Exe

Vi. Final effects

We found our back-end request working。

Extension 1. Nginx's role as a web server 2. Nginx's default as a reverse agent 3

1. Request entrance at the network level

4. How to verify whether the request has passed nginx5. If you do not want the request to pass nginx's summary

In conclusion, there are many ways in which nginx can address cross-domain issues, such as modifying response headers and using the cors module. But you can choose the most appropriate solution to cross-domain problems based on real needs。

This is where the article on the nginx reverse agent crossing resolution is presented. More about the nginx reverse agent addressing cross-domain content are requested to search for previous script home articles or to continue looking at the following article for more support for script homes in the future