Stay signed in through a network blip #114

Merged

jcoffey-dev merged 1 commits from fix/keep-session-on-blip into main

2026-10-18 22:40:30 +00:00

Author	SHA1	Message	Date
jcoffey-dev	eb901af98f	Stay signed in through a network blip ci / build (pull_request) Skipped Details ci / publish (pull_request) Skipped Details ci / notices (pull_request) Successful in 52s Details github/ci (branch) GitHub Actions Details ci / github (pull_request) Successful in 1m51s Details Any failed token refresh signed you out and reloaded the sign-in page: a dropped connection, a server restart or a laptop waking up lost the page and anything typed into it, and signing in again landed on the dashboard. - Only a refusal from the token endpoint (400, 401, 403: the refresh token is spent or revoked, or the account locked) ends the session. - No answer, a 5xx, rate limiting or a proxy's error page keeps you signed in on the page. A note says the server can't be reached; the refresh is retried after 5, 10 and 20 seconds, then every minute, at once when the browser comes back online, or on "Try now". - A request with a token that hasn't run out still goes ahead while the refresh waits, and a failed refresh no longer reads as a 401. - When the session does end, signing in again comes back to the page you were on. 2 new strings, English only.	2026-10-18 15:31:22 -07:00

Author

SHA1

Message

Date

jcoffey-dev

eb901af98f

Stay signed in through a network blip

ci / build (pull_request) Skipped

Details

ci / publish (pull_request) Skipped

Details

ci / notices (pull_request) Successful in 52s

Details

github/ci (branch) GitHub Actions

Details

ci / github (pull_request) Successful in 1m51s

Details

Any failed token refresh signed you out and reloaded the sign-in page: a
dropped connection, a server restart or a laptop waking up lost the page
and anything typed into it, and signing in again landed on the dashboard.

- Only a refusal from the token endpoint (400, 401, 403: the refresh
  token is spent or revoked, or the account locked) ends the session.
- No answer, a 5xx, rate limiting or a proxy's error page keeps you
  signed in on the page. A note says the server can't be reached; the
  refresh is retried after 5, 10 and 20 seconds, then every minute, at
  once when the browser comes back online, or on "Try now".
- A request with a token that hasn't run out still goes ahead while the
  refresh waits, and a failed refresh no longer reads as a 401.
- When the session does end, signing in again comes back to the page
  you were on.

2 new strings, English only.

2026-10-18 15:31:22 -07:00