Cookie details
A mechanism for cookies to store data on a remote browser and track and identify users. In terms of implementation, a cookie is a small piece of data stored on the client, and the browser (i.e., the client) interacts with the server through the HTTP protocol.
Cookies exist independently of languages. Strictly speaking, cookies are not implemented by languages such as PHP and Java, but are indirectly operated on cookies by these languages, that is, sending HTTP commands. When the browser receives the command, it operates the cookies and returns them to the server. Therefore, cookies are implemented and managed by the browser. For example, PHP has not really set up cookies, but just sends instructions for the browser to do this. In PHP, you can use the setcookie() or setrawcookie() function to set cookies. After the last parameter HttpOnly is set, JavaScript cannot read the cookie.
When setting cookies, you need to pay attention to: ① The function has a return value, false failed, true succeeds, success is for reference only, and does not mean that the client will receive it; ② The cookies set by PHP cannot take effect immediately, and you have to wait for the next page to see it (the cookies are transmitted from the server to the browser, and the browser on the next page can pass the set cookies back to the server); if it is set by JavaScript, it will take effect immediately; ③ The delete function that does not display in the cookies, you can set the expire expiration time to automatically trigger the browser's deletion mechanism.
Cookies are part of the HTTP header, that is, the data domain is sent or requested; functions such as setcookie() must be called before the data, which is the same as the header() function. However, you can also use the output buffer function to delay the output of the script, knowing that all cookies and other HTTP headers are set.
Cookies are usually used to store some information that is not very sensitive or to control login. They can also be used to remember usernames, remember password-free login, prevent ticket swiping, etc. There are restrictions on the cookies allowed under each domain name, and this limitation is also different depending on the browser. The more cookies, the better. It will increase broadband and increase traffic consumption, so don’t abuse cookies; don’t use cookies as the client’s memory. Each cookie limit for a domain name is stored in the form of 4 kilobytes (KB) key-value pairs.
There is another type of cookie created by Flash and becomes Flash Shard Object, also known as Flash Cookie. Even if all privacy data of the browser is cleared, this type of stubborn cookie will still exist on the hard drive because it is only managed by Flash, and many websites use this technology to identify users.
Cookies cross-domain, mainly to unify the application platform and realize single sign-in; they need to use the P3P protocol (Platform for Privacy Preferences), through P3P, users can specify the browser's privacy policy to achieve the purpose of storing third-party cookies. They only need to add configuration information about P3P to the HTTP header information when responding to user requests. Cookies cross-domain involve two different applications, customarily called first and third parties. Third parties are usually ads from other people, or URLs from other websites that may use cookies.
OK, let me introduce to you how to rewrite the cookie path by vue webpack. The specific content is as follows:
The reverse proxy server provided by webpack is very convenient in the development stage. You can use the reverse proxy function by configuring a few lines of simple code, including path rewriting, cookie processing, etc.
The API path used in the project development stage is /admin, and it is / when deployed online. Therefore, during the development process, you need to configure the reverse proxy in proxyTable and rewrite the path. The path rewriting code is as follows (config/):
proxyTable: {
'/admin': {
target: 'http://127.0.0.1:8080',
changeOrigin: true,
pathRewrite: {
'^/admin': '/admin2'
},
}
}
Log in after starting the project. At this time, the API request was successful, but when obtaining the logged-in user information, it was found that the cookie was not brought over. View the request and discover the login requestSet-CookieThe Path in the response header is /admin2. But the path we request is /admin, and the cookie will of course not take effect.
Looking through the document, it was found that proxyTable supports onProxyRes callback function to customize responses, and the process is set by replacing the backend server.cookie-path To process it, the code is as follows:
proxyTable: {
'/admin': {
target: 'http://127.0.0.1:8080',
changeOrigin: true,
pathRewrite: {
'^/admin': '/lesson/admin'
},
onProxyRes: function (proxyRes, req, res){
const cookies = ['set-cookie']
if (cookies) {
const newCookies = (cookie=> {
return (/Path=\/admin2/, 'Path=/')
})
delete ['set-cookie']
['set-cookie'] = newCookies
}
}
},
},
After restarting webpack, I logged in again and found that the path of the cookie has been rewritten to /.
Summarize
The above is the method of rewriting the cookie path by vue webpack that I introduced to you. I hope it will be helpful to you. If you have any questions, please leave me a message and the editor will reply to you in time. Thank you very much for your support for my website!
If you think this article is helpful to you, please reprint it. Please indicate the source, thank you!