This article is mainly because I have heard others talk about json cross-domain and cross-domain before, but I am still confused and only know one thing. So in a rage, I read through various information and found out if there was anything incorrect. , please correct me^_^
First of all, understand that browsers have a very important security restriction, which is the same-origin policy: client scripts in different domains cannot read each other's resources without explicit authorization. Cross-domain means different sources~
To put it simply, as long as the protocol, port, and domain name are different, it is cross-domain!
However, when doing some in-depth front-end programming, cross-domain operations are inevitably required. At this time, the "same origin policy" appears to be too harsh.
Solution:
1. Use jsonp to solve cross-domain issues: (only for GET requests)
Implementation principle: The
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
