You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Confirming I can reproduce the issues with the Glitch server. Among other issues, refresh was not fully implemented. I'll follow up here once I can actually perform a refresh with the Glitch server.
As of last night, the Glitch server successfully issues a challenge at registration and refresh, and Chrome versions 134.0.6988.0 (the newest Canary) does persist the registration.
Hi Team
I'm digging current implementation behavior based on your prototype server.
https://glitch.com/edit/#!/dbsc-prototype-server
IIUC
Sec-Session-Registration
andSet-Cookie: id=abc; Max-Age=10
Sec-Session-Response
w/ JWT which hasrefresh_url: refresh
10 sec later
id=abc
Cookie was expired/refresh
w/Sec-Session-Id
internallyBut, Browser internal request to
/refresh
doesn't happen.What I missed here ?
The text was updated successfully, but these errors were encountered: