From 709a41fd437b7619156a7b74163ea9c5ebde1284 Mon Sep 17 00:00:00 2001 From: Sam Brannen Date: Sat, 8 Jan 2022 16:35:58 +0100 Subject: [PATCH] Fix broken links to WebSocket support in Spring Security & Spring Session --- src/docs/asciidoc/web/websocket.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/docs/asciidoc/web/websocket.adoc b/src/docs/asciidoc/web/websocket.adoc index 2a8042403d5..74f4a076584 100644 --- a/src/docs/asciidoc/web/websocket.adoc +++ b/src/docs/asciidoc/web/websocket.adoc @@ -1732,11 +1732,11 @@ the user is already authenticated at the HTTP transport level, and expects that the WebSocket or SockJS session contain the authenticated user. NOTE: Spring Security provides -https://docs.spring.io/spring-security/site/docs/current/reference/htmlsingle/#websocket[WebSocket sub-protocol authorization] +https://docs.spring.io/spring-security/reference/servlet/integrations/websocket.html#websocket-authorization[WebSocket sub-protocol authorization] that uses a `ChannelInterceptor` to authorize messages based on the user header in them. -Also, Spring Session provides a -https://docs.spring.io/spring-session/docs/current/reference/html5/#websocket[WebSocket integration] -that ensures the user HTTP session does not expire when the WebSocket session is still active. +Also, Spring Session provides +https://docs.spring.io/spring-session/reference/web-socket.html[WebSocket integration] +that ensures the user's HTTP session does not expire while the WebSocket session is still active.