SignalR: Content-Type header in GET requests

[jmajoor]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

WAF is flagging signalR long polling requests due to them having the Content-Type header on GET requests.

The issues was also report on the old code base: SignalR/SignalR#4373

Expected Behavior

There should be no content-type header for SignalR long polling GET requests.

Steps To Reproduce

Use a long polling TypeScript client to communicate to a signalR hub.
Inspect the long polling requests in the developer tools of the browser and you see that the GET requests have a content type set.
"Content-Type": "text/plain;charset=UTF-8",

Exceptions (if any)

No response

.NET Version

.NET 6

Anything else?

Ideally I would like to see POST requests and then also move the access token from the query string to the body of the request.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[casmrv]

This has also been reported previously against asp.net.
Given that signalr long polling frequently ends up being the fallback due to network complexities, it would be good to get this fixed.

[BrennanConroy]

We accept PRs 😃

This one should be fairly straightforward; my biggest concern is that react-native on android should be tested to make sure we don't break it again, as the addition of the header was made for that scenario.

[davidfowl]

Ideally I would like to see POST requests and then also move the access token from the query string to the body of the request.

Not following this one. File a new issues and describe why, I'm not understanding the reasoning here.

[jmajoor]

@davidfowl, turns out that the issue I was hinting at (access tokens) has been properly addressed for long polling. This issue is just for the use of Content-Type in a GET operation. Sorry for the confusion.