瀏覽代碼

Docs: Fix broken link to websocket security info

Ryan W. Moore 9 年之前
父節點
當前提交
cdb04c50e8
共有 1 個文件被更改,包括 2 次插入2 次删除
  1. 2 2
      docs/manual/src/docs/asciidoc/_includes/websocket.adoc

+ 2 - 2
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 <<websocket-authorization>>
 
-Spring Security also provides <<nsa-websocket,XML Namespace>> support for securing WebSockets.
+Spring Security also provides <<nsa-websocket-security,XML Namespace>> 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 <<nsa-websocket,XML Namespace>> support for securing WebSockets.
+Spring Security also provides <<nsa-websocket-security,XML Namespace>> support for securing WebSockets.
 A comparable XML based configuration looks like the following:
 
 [source,xml]