* Cleanup SignalR Windows Auth with browsers
* Update
* Update authn-and-authz.md
* Update authn-and-authz.md
Co-authored-by: Luke Latham <1622880+guardrex@users.noreply.github.com>
Co-authored-by: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com>
Fixing range for `Connect to a hub` section sample code.
Current code shows this:
```js
const connection = new signalR.HubConnectionBuilder()
.withUrl("/chatHub")
.configureLogging(signalR.LogLevel.Information)
.build();
start();
/* this is here to show an alternative to start, with a then
```
New should show this:
```js
const connection = new signalR.HubConnectionBuilder()
.withUrl("/chatHub")
.configureLogging(signalR.LogLevel.Information)
.build();
async function start() {
try {
await connection.start();
console.log("connected");
} catch (err) {
console.log(err);
setTimeout(() => start(), 5000);
}
};
connection.onclose(async () => {
await start();
});
// Start the connection.
start();
/* this is here to show an alternative to start, with a then
connection.start().then(() => console.log("connected"));
*/
/* this is here to show another alternative to start, with a catch
connection.start().catch(err => console.error(err));
*/
```
* Update hubcontext.md
Failing to call next causes bad things to happen. Better to leave it in the example.
* Update hubcontext.md
This shows how to access IHost for use outside of aspnetcore. ie integration with other dependency injection frameworks
* hubcontext.md: Move note back to original location.
* Update hubcontext.md
* Update aspnetcore/signalr/hubcontext.md
Co-authored-by: Brennan <brecon@microsoft.com>
Co-authored-by: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com>
Co-authored-by: Brennan <brecon@microsoft.com>
* Add 3.0 SignalR background service sample
* Fix background-services.md date
* Compressed a few monikers
* Renamed 3.0 sample to 3.x
* Apply suggestion
Co-Authored-By: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com>
* Shrink ClockHubClient.StopAsync snippet by 1 line
Also tweaked the wording slightly in the "any class that inherits from hub..." note
* Remove future tense from note
* Use async On overload in 3.x sample
Co-authored-by: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com>
* Update SignalR CORS for 5.0
* Update aspnetcore/signalr/configuration.md
Co-Authored-By: Scott Addie <10702007+scottaddie@users.noreply.github.com>
Co-authored-by: Scott Addie <10702007+scottaddie@users.noreply.github.com>
* Update MessagePack docs for 5.0
* some formatting
* Edit pass on MessagePack doc updates for 5.0 (#17767)
Co-authored-by: Scott Addie <10702007+scottaddie@users.noreply.github.com>
* [SignalR] Update to streaming sample
Adds the EnumeratorCancellationAttribute to the sample to prevent warnings when users add CancellationTokens. It also allows the server-side code to use `await foreach` with cancellation (i.e. in unit tests).
Fixes#16202
* feedback
One of the anchor links was out of date. But really both links needed updating because they point people at the 2.1 documentation when for SignalR only the 1.x version is relevant. So I've updated the links to explicitly point at the v1.8 branch of the docs which fixes the broken link and points people at the docs relevant to the version they're using.
* New include connectID security warning & applied to hubs.md for SignalR
* patch: Corrected grammar on include warning.
* patch: adding ConnectID section to security.md for Signalr.
* Update aspnetcore/includes/connectionid-signalr.md
Co-Authored-By: Stephen Halter <halter73@gmail.com>
* Update security.md
Changed "ConnectionID" to "ConnectionId"
Co-authored-by: Stephen Halter <halter73@gmail.com>
* update(scale-out): docs for redis backplane
The sticky session was a little bit vague so that one might think even if they use just WebSocket for all the clients and use Redis backplane they still might need "sticky sessions". There was a clarification by @davidfowl [here](https://twitter.com/davidfowl/status/1212068926676275202?s=20)
* Update scale.md
* Update scale.md
* Update scale.md
Co-authored-by: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com>
* Cleaned up moniker versioning for ASP.NET Core SignalR configuration
* patch: Removed 3.0 intro from start of < 3.0 section and extra spaces.
* removed extra >3.0 moniker ranges from original no longer needed.
* Patch: Divided into 3 complete versions >= 3.0, =2.2, < 2.2, removed no 3.1 update warning.
* patch: removed dupe 2.2 keep alive option table from < 2.2 section. Moved H1 above monikers.
* patch: removed java client websockets line from 2.1 version.