SignalR Adds Remote Access Cross-Domain Support

jimmyjack · 发表于 2021-4-23 12:39:20

Requirement: The front-end and back-end are not on the same domain, so there is a cross-domain problem, how can the front-end connect to the remote SignalR?

First, the js code is as follows:

SignalR is visible.

At first try to connect will report an error as follows:

Access to fetch at 'http://localhost:27939/testHub/negotiate?negotiateVersion=1' from origin 'http://localhost:5009' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

ASP.NET Core 3.1 Add Allow Cross-Domain

The ConfigureServices code looks like this:

Visible at login.

The Configure code is as follows:

Login to see.

Trying to connect again results in the following error:

Login/Register to see larger image

Access to fetch at 'http://localhost:27939/testHub/negotiate?negotiateVersion=1' from origin 'http://localhost:5009' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'.

Modify the ConfigureServices code again as follows:

Login Visible.

Login/Register to see larger image

Problem solved!

I · 发表于 2021-9-22 21:00:27

I'm not sure if I'm going to be able to do this, but I'm sure I'll be able to.

jiao983 · 发表于 2022-11-16 14:46:09

Learning Learning Learning Learning

		Auto Login	Retrieve password
Retrieve Password			Register

[Information]SignalR Adds Remote Access Cross-Domain Support

Related posts

Sections viewed