From cdb04c50e826eec293dffb4fbf3d150d566525be Mon Sep 17 00:00:00 2001 From: "Ryan W. Moore" Date: Sat, 28 May 2016 20:05:47 -0400 Subject: [PATCH] Docs: Fix broken link to websocket security info --- docs/manual/src/docs/asciidoc/_includes/websocket.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/manual/src/docs/asciidoc/_includes/websocket.adoc b/docs/manual/src/docs/asciidoc/_includes/websocket.adoc index ffbeeec6ab..7b4b5db09a 100644 --- a/docs/manual/src/docs/asciidoc/_includes/websocket.adoc +++ b/docs/manual/src/docs/asciidoc/_includes/websocket.adoc @@ -39,7 +39,7 @@ This will ensure that: <2> The SecurityContextHolder is populated with the user within the simpUser header attribute for any inbound request. <3> Our messages require the proper authorization. Specifically, any inbound message that starts with "/user/" will require ROLE_USER. Additional details on authorization can be found in <> -Spring Security also provides <> support for securing WebSockets. +Spring Security also provides <> support for securing WebSockets. A comparable XML based configuration looks like the following: [source,xml] @@ -100,7 +100,7 @@ This will ensure that: <5> Any other message of type MESSAGE or SUBSCRIBE is rejected. Due to 6 we do not need this step, but it illustrates how one can match on specific message types. <6> Any other Message is rejected. This is a good idea to ensure that you do not miss any messages. -Spring Security also provides <> support for securing WebSockets. +Spring Security also provides <> support for securing WebSockets. A comparable XML based configuration looks like the following: [source,xml]