docs: note where streamingRefresh sends the WebSocket cookie

On a WebSocket upgrade, the refreshed session cookie arrives on the 101
response. Traefik keeps middleware headers on that response, and RFC 6455
section 4.1 has clients store cookies from it.

Claude-Session: https://claude.ai/code/session_01G1d1n1BrHHHw8dBUkbiBPC
This commit is contained in:
2026-09-28 17:28:01 +01:00
parent 7ae75d2523
commit 74decb21c2
+2 -1
View File
@@ -322,7 +322,8 @@ WebSocket upgrade. The middleware handles this automatically:
for streaming until the session cookie expires. Set `streamingRefresh: true`
to refresh an expired token on the request. If the IdP rejects the refresh
(`invalid_grant`), the request gets `401`. If the IdP cannot be reached,
the request is forwarded as before.
the request is forwarded as before. On a WebSocket upgrade, the refreshed
session cookie arrives on the `101 Switching Protocols` response.
No configuration needed — this is implicit behavior.