Skip to content

feat(frontend): consume X-New-Token header for sliding token refresh#695

Merged
gary-Shen merged 1 commit into
releasefrom
feat/jwt-sliding-token-refresh
Jun 2, 2026
Merged

feat(frontend): consume X-New-Token header for sliding token refresh#695
gary-Shen merged 1 commit into
releasefrom
feat/jwt-sliding-token-refresh

Conversation

@gary-Shen

Copy link
Copy Markdown
Member

The backend re-issues a token via the X-New-Token response header when the current one is near expiry. Read that header in both axios response interceptors and update localStorage.token so active users stay logged in.

The header value uses the same Bearer xxx format the login endpoint returns, so it drops straight into the existing Authorization flow.

The backend re-issues a token via the X-New-Token response header when the
current one is near expiry. Read that header in both axios response
interceptors and update localStorage.token so active users stay logged in.

The header value uses the same `Bearer xxx` format the login endpoint
returns, so it drops straight into the existing Authorization flow.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@gary-Shen gary-Shen merged commit 2d4fba9 into release Jun 2, 2026
1 check failed
@gary-Shen gary-Shen deleted the feat/jwt-sliding-token-refresh branch June 2, 2026 07:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant