From a26ce20d47db9f1164d7332019c08d9e18037f7e Mon Sep 17 00:00:00 2001 From: Jupiter <4177229+jupiterhub@users.noreply.github.com> Date: Mon, 19 Oct 2020 20:39:32 +0900 Subject: [PATCH 1/2] Wording changes. Fixed typo 'CorsConfiguraiton' --- src/docs/asciidoc/web/webflux-websocket.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/docs/asciidoc/web/webflux-websocket.adoc b/src/docs/asciidoc/web/webflux-websocket.adoc index 033751bed2f0..0e08d972d502 100644 --- a/src/docs/asciidoc/web/webflux-websocket.adoc +++ b/src/docs/asciidoc/web/webflux-websocket.adoc @@ -412,7 +412,7 @@ only Tomcat and Jetty expose such options. The easiest way to configure CORS and restrict access to a WebSocket endpoint is to have your `WebSocketHandler` implement `CorsConfigurationSource` and return a -`CorsConfiguraiton` with allowed origins, headers, and other details. If you cannot do +`CorsConfiguration` with allowed origins, headers, and other details. If you cannot do that, you can also set the `corsConfigurations` property on the `SimpleUrlHandler` to specify CORS settings by URL pattern. If both are specified, they are combined by using the `combine` method on `CorsConfiguration`. From 1c6a61f54ed5f930f69cdeb11b95d3b6e9b653bf Mon Sep 17 00:00:00 2001 From: Jupiter <4177229+jupiterhub@users.noreply.github.com> Date: Thu, 14 Jul 2022 10:43:01 +0900 Subject: [PATCH 2/2] fix: broken link to rsocket protocol page --- src/docs/asciidoc/rsocket.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/docs/asciidoc/rsocket.adoc b/src/docs/asciidoc/rsocket.adoc index 97bf16736ccd..3270aa567b96 100644 --- a/src/docs/asciidoc/rsocket.adoc +++ b/src/docs/asciidoc/rsocket.adoc @@ -53,7 +53,7 @@ through RSocket across the network. === The Protocol One of the benefits of RSocket is that it has well defined behavior on the wire and an -easy to read https://rsocket.io/docs/Protocol[specification] along with some protocol +easy to read https://rsocket.io/about/Protocol[specification] along with some protocol {gh-rsocket}/rsocket/tree/master/Extensions[extensions]. Therefore it is a good idea to read the spec, independent of language implementations and higher level framework APIs. This section provides a succinct overview to establish some context.