Add non extended connect support to http/2

[webczat]

Would it be possible to add connect support to http/2? I mean the CONNECT method without the :protocol header.
I mean looking at current code for extended connect, it seems trivial, but unsure. handling is probably exactly same except allowing ":protocol" to not be present.

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Would it be possible to add connect support to http/2? I mean the CONNECT method without the :protocol header.
I mean looking at current code for extended connect, it seems trivial, but unsure. handling is probably exactly same except allowing ":protocol" to not be present.

Author:	webczat
Assignees:	-
Labels:	area-System.Net.Http, untriaged
Milestone:	-

[wfurt]

What would be the use case @webczat?

[webczat]

Hello,
I am unsure if browser ever, when giving https server as a proxy, try to use http2 for the connection? in that case they'd likely use the CONNECT method.
The motivation to report this in my case is, however, i admit, just the fact that it's a specific case where the feature is already there, just it has a restriction (that it works only when the ":protocol" header is present, but it could probably work as well without it. so it is pretty much an artificial restriction IMO, and that this method is specified in HTTP2 from what I can tell. It might be not enough of a motivation to implement it, though, even though this change looks trivial, at least to me.