📝 docs: WS session-expiry probe findings (handshake 401, established-stream open) #189
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/ws-expiry-probe"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The 2 h live probe launched after #161 (to settle "does an established stream survive the session expiry?") returned partial results: the observation host suspended across the boundary, but the post-expiry checks (73 min after expiry) are solid: the old cookie is rejected with 401 at the WS handshake, exactly like REST — confirming expiry is enforced everywhere the cookie is presented, and validating a posteriori the layered re-auth design of
stream_measurements(proactive pre-handshake refresh + reactive 401 fallback). The established-stream-at-expiry question stays open; an inhibited rerun is in flight and will follow as its own update.Evidence
pytest= 242 passed,mypyclean.Merge Danger
Door: two-way — documentation only.
Blast Radius: none — no code change.
WIP: 📝 docs: WS session-expiry probe findings (handshake 401, established-stream open)to 📝 docs: WS session-expiry probe findings (handshake 401, established-stream open)