Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility between Core SignalR server and Net 4 SignalR clients. #59703

Open
1 task done
tdhintz opened this issue Jan 3, 2025 · 0 comments
Open
1 task done

Compatibility between Core SignalR server and Net 4 SignalR clients. #59703

tdhintz opened this issue Jan 3, 2025 · 0 comments
Labels
area-signalr Includes: SignalR clients and servers

Comments

@tdhintz
Copy link

tdhintz commented Jan 3, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

We have a Net 4 winform providing a bridge between browsers and Windows TWAIN scanners. It was migrated to Net Core and now the negotiate fails. Research suggests this is because there is no compatibility option between Core and Net 4 SignalR servers and clients. The impact is that it is not possible to update either the SignalR server or client without requiring a reinstall of the winform bridging component across the entire customer base. This is a huge logistical issue.

Describe the solution you'd like

Provide a Net 4 SignalR compatibility mode for Core, or describe how Core can be configured for compatibility.

Additional context

Trace:

Debug: 2025-01-03 09:22:25.757 1 candidate(s) found for the request path '/s/negotiate'
Debug: 2025-01-03 09:22:25.758 Request matched endpoint '/s/negotiate'
Debug: 2025-01-03 09:22:25.760 The maximum request body size has been set to 104857600.
Information: 2025-01-03 09:22:25.761 Executing endpoint '/s/negotiate'
Information: 2025-01-03 09:22:25.763 Executed endpoint '/s/negotiate'
Information: 2025-01-03 09:22:25.764 Request finished HTTP/2 GET https://localhost:59754/s/negotiate?clientProtocol=2.1&connectionData=%5B%7B%22name%22%3A%22s%22%7D%5D&_=1735912793367 - 405 0 text/plain 14.2070ms

@dotnet-issue-labeler dotnet-issue-labeler bot added the area-signalr Includes: SignalR clients and servers label Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-signalr Includes: SignalR clients and servers
Projects
None yet
Development

No branches or pull requests

1 participant