I’ve never done this, but I have an idea. You can use websocket to generate a QR code as a connection and cache the socket_id at the same time. http://www.xxx.com/api/login/{socket_id} When the QR code is scanned, send a request to login/{socket_id} Use scoket_id in the backend and use websocket to notify the page to jump. The specific login business can be written in login. It doesn’t need to be a URL, as long as the socket_id can be transmitted to the server through the mobile terminal.
Back-end redirection, some information of the QR code can be placed in the url parameters
I’ve never done this, but I have an idea.
You can use websocket
to generate a QR code as a connection and cache the socket_id at the same time.
http://www.xxx.com/api/login/{socket_id}
When the QR code is scanned, send a request to login/{socket_id}
Use scoket_id in the backend and use websocket to notify the page to jump.
The specific login business can be written in login.
It doesn’t need to be a URL, as long as the socket_id can be transmitted to the server through the mobile terminal.
ajax polling, this is what WeChat does.