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
SignalR: Missing Accept-Header #47398
Comments
@BrennanConroy Although the issue title cites Swagger this doesn't seem to be OpenAPI related. Any hunch as to what is going on here? |
Yeah, looks like no one is adding an Accept header on negotiate, and I'd guess other requests as well. We'd need to figure out what header value(s) are acceptable. Looking at the browser it sends |
My apologies, I was working on both SignalR and Swagger at the time and it seems I had a brain fart while naming the issue. |
Thanks for contacting us. We're moving this issue to the |
Looks like this issue has been identified as a candidate for community contribution. If you're considering sending a PR for this issue, look for the |
@BrennanConroy Might the following changes within
|
In negotiate yes (although |
@BrennanConroy I believe the |
There is the send from LongPolling and ServerSentEvents, and the get from LongPolling. The ServerSentEvents "get" already sets |
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
The Azure WAF is reporting an anomaly when negotiating a SignalR connection from a Console app to the Azure SignalR Service.
The anomaly that is being reported:
"matchVariableValue": "Microsoft SignalR/6.0 (6.0.5+e5f183b656a0e8bc087108130a5a9b54ae94494e; Windows NT; .NET; .NET 6.0.3)"
Describe the solution you'd like
In
Microsoft.AspNetCore.SignalR.Client
an Accept Header should be added to the negotiating requests.Additional context
I'm running version 6.0.5 of the SignalR Client, as I'm unable to upgrade to 7.0.4 at the moment.
I cannot find the release notes for
Microsoft.AspNetCore.SignalR.Client
to check if the Accept Header hasn't been added, but since I cannot find an issue about this (open or closed), I would assume it hasn't been fixed yet.The text was updated successfully, but these errors were encountered: