Large number of duplicate strings for concurrent websocket connections

[davidfowl]

Seems like something we could consider interning:

We could probably eliminate this by making these known headers (though I think we should potentially remove other known headers and replace them with the websocket headers 😄).

cc @benaadams

[benaadams]

Should resolve it? #31311

It won't get rid of localhost:5000 though as the Host value; that is amortized across many requests and the WebSocket upgrade is just one per connection. Would need a different approach.

Could switch it in the "allowed origins" middleware; so if you specify allowed origins and one matches then it could switch the header value for the string object in the middleware options? 🤔

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. Because it's not immediately obvious that this is a bug in our framework, we would like to keep this around to collect more feedback, which can later help us determine the impact of it. 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.