does not have the expired front end to judge whether the token expires or not?
theoretically, if there is no web socket active push,
the process should call the API twice. If the access_token call fails, then the refresh_token call reacquires access_token, when the original interface

the back end pushes a TONKEN update data to the front end

when you initiate a http request. The browser will bring cookie by default, and the backend receives this request and reads the cookie, inside to check whether it is about to expire. If so, the server updates cookie, and appends it to response. Update cookie.

cookie

answer

if you only need to push the back end to the front end, try SSE

1.refresh token does not know, but the backend knows that when you send the request operation data, the token expires and the backend returns to you that you have no permission (or a custom error code indicates expiration). You take a look at the local error. I have token, so it seems that my token has expired?

2. Okay, what if it expires? when I logged in, I returned not only token but also refresh token, ah, just like what should I do when my Hong Kong and Macao pass expired? take the refresh token to the backend interface to renew the backend and give you a new token. Then I will bring this token. From then on, you can continue to request data