SignalR GET with body

[marcstern]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

In recent versions, SignalR sometimes send GET requests with a header "Transfer-Encoding: chunked".
Some reverse proxies crash with this in certain conditions and most WAF block this.

Expected Behavior

GET requests should have no Transfer-Encoding header, nor body.

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

No response

Anything else?

No response

[BrennanConroy]

What client are you using? What transport? "In recent versions", what version did it start happening?

[marcstern]

Hello.

We have the problem with version 8.0.0. We tried Chrome & Edge.
Actually, the problem may have been present in older versions, not sure.
We detected this because we were behind a WAF.

It seems that the problem happens during SignalR negotiation.
If the web socket cannot be established, a GET requests with a header "Transfer-Encoding: chunked" is sent.
Because it's inside the negotiation, we don't see it in the developers tools but we saw it on the WAF.

[BrennanConroy]

Because it's inside the negotiation, we don't see it in the developers tools

That doesn't make any sense. If the request is coming from the browser it will be in the developer tools.

SignalR in the browser never sets Transfer-Encoding: chunked. So either the browser is setting it for some reason (out of our control), you're setting it in your configuration, or you're omitting some information about your setup.

[marcstern]

I will try to get more detailed info from the developer