Multiple solutions for cross-domain reasons in web development

Cross-domain reasons

This is due to the browser's same-origin policy restrictions;

Cross-domain means: when a request URL If any one of the protocol, domain name, and port number is different from the current page URL, it is cross-domain.

JSONP

This method is not suitable for development and can be said to be completely eliminated, but due to the complexity of implementation, the interviewer is very interested in this solution.

Core idea: The web page requests JSON data from the server by adding a src attribute of a <script> tag. After receiving the request, the server puts the data in the parameter position of a callback function with a specified name and passes it back.

Disadvantages: Requires backend cooperation to complete, can only send get requests

Implementation: Note that the backend returns a method call and actual parameters.

Nginx solution

Backend solution

Add annotations at the Controller layer:

@CrossOrigin(origins = "*", allowedHeaders = "*")

origins : List of allowed origin domains

allowedHeaders : The field types in the request headers allowed in cross-origin requests

The above is the detailed content of various solutions to the cross-domain reasons of web development. For more information about cross-domain solutions for web development, please pay attention to other related articles on 123WORDPRESS.COM!