The oldest front-end and back-end separation is like this. HTML files are placed on the static server. The browser accesses the static server to get the HTML and other resource files. After parsing, it sends an ajax request to the backend interface. The backend returns the data in Fill in the browser.
The static server serves as the entrance, provides static file services, and forwards interface requests, so there is no need to cross domains.
The disadvantage of this solution is the SEO problem. If SEO is not considered, this architecture is feasible.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
The oldest front-end and back-end separation is like this. HTML files are placed on the static server. The browser accesses the static server to get the HTML and other resource files. After parsing, it sends an ajax request to the backend interface. The backend returns the data in Fill in the browser.
The static server serves as the entrance, provides static file services, and forwards interface requests, so there is no need to cross domains.
The disadvantage of this solution is the SEO problem. If SEO is not considered, this architecture is feasible.
Yes, it will be no problem if the backend interface allows cross-domain access
Nowadays, many people use this method to separate the front and back ends. The front end only needs to do routing and data binding
Yes, use CORS cross-domain.
Yes, no problem
No problem, you can. Use http protocol
Use JSONP