HTTP is a stateless connection and only needs cookies to record the status And websocket always maintains a connection, so there is no need for cookies. When you need to share the login information of the previous system, just send the cookie directly. What you need should be an authentication mechanism. This mechanism can be compatible with the cookie implementation just mentioned, or use Basic Auth, OAuth 2 or the like
websocket is a link to the TCP/IP layer, and cookies are things of the application layer HTTP protocol, so they cannot. Unless websocket the downgrade solution is used when the browser does not support it.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
HTTP is a stateless connection and only needs cookies to record the status
And websocket always maintains a connection, so there is no need for cookies. When you need to share the login information of the previous system, just send the cookie directly.
What you need should be an authentication mechanism. This mechanism can be compatible with the cookie implementation just mentioned,
or use Basic Auth, OAuth 2 or the like
websocketis a link to the TCP/IP layer, and cookies are things of the application layer HTTP protocol, so they cannot.Unless
websocketthe downgrade solution is used when the browser does not support it.