To get authenticated SignalR hubs to work, you need to allow credentials in CORS, so your aspnetcore code might look like this:
|
1 2 3 4 5 6 7 |
services.AddCors(action => action.AddPolicy(policyName, builder => builder .AllowAnyMethod() .AllowAnyHeader() .AllowAnyOrigin() .AllowCredentials())); |
As of
UPDATE, 2018 May 30: It’s alive. The dotnet team officially announces 2.1 on their blog! The newest version of ASP.NET Core will be released in
In a previous post, I wrote about using SignalR in AspNetCore. Today, I tried the next step up – SignalR as a service! You will
We’ve all been waiting for the first production release of SignalR for AspNetCore, and supposedly it’s going to be out there any day now. Impatient
At Trailhead, we’ve recently been noticing an increase in a couple of questions from our clients. They are: 1. Is Web Forms dead?, and 2.