Re: Moving 2817 to Historic

Willy,

RFC 2616 also defined the Upgrade header and 101 status code, but it doesn't cover the specific TLS upgrade case (which is why RFC 2817 exists).


> On Feb 13, 2019, at 11:33 AM, Willy Tarreau <w@1wt.eu> wrote:
> 
> Hi Mike,
> 
> On Wed, Feb 13, 2019 at 10:05:03AM -0500, Michael Sweet wrote:
>> Mark,
>> 
>> HTTP Upgrade is used by IPP/1.1 [STD92] and IPP/2.0 [PWG Standard 5100.12]
>> for opportunistic TLS and has been supported and used by CUPS for about 20
>> years.  I would NOT be in favor of marking it historic.
> 
> It's also used by Websocket and even h1->h2 upgrade as well.
> However I think it is completely covered by RFC7230 #6.7 :
> 
>     https://tools.ietf.org/html/rfc7230#section-6.7
> 
> Regards,
> Willy
> 

_________________________________________________________
Michael Sweet, Senior Printing System Engineer