Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
CONNECT: consider using ALPN registry for the :protocol values. #471
Please consider using the ALPN protocol IDs registry instead of the HTTP Upgrade token registry for the
The only downside is that there is no
Also, we should add
IMHO this would not be logical. CONNECT and Upgrade are really similar in that they are used to transport something over HTTP, and that something may very well be a TLS stream which itself contains its own ALPN.
Anyway this should be discussed on the mailing list, not via issues here.
@PiotrSikora, those are the same topic. The
However, if we were redefining the Upgrade registry now, I'd argue for using the ALPN registry for both of these. Fundamentally, they are both registries of tokens which identify an application-layer protocol which can run over a bytestream. (Or collection of bytestreams, when used with QUIC.) The only real restriction is that Upgrade requires that the protocol be able to answer the original HTTP request in the new protocol, which means there has to be a defined mapping between HTTP requests and whatever the new protocol is.
The currently-registered values are disjoint, but I wonder if perhaps HTTPter should consider merging the two registries?