In the whole architecture, the website may need to use various services such as load balancing, CDN, cloud shield, etc., and when users access the real server, they need to go through layers of proxies.
The user has successfully logged in, but when he jumps to the homepage, he still shows that he is not logged in The user posts the data, but the background does not receive the submitted content The user accesses the URL normally, the content returned is wrong, and there is no problem with the local test
It is precisely because of the layers of proxy access that when we are not properly configured, the proxy may discard some content, such as: useragent, cookies, request headers, URL question mark parameters, etc. We can't find the exact reason.
At this time, it is particularly important to have a page to display the information requested by the user, as shown in the figure below:
Code:
|