Status 101

[tangor]

In all my years I've never seen a Status 101 in raw logs.

The IP was an apparent ordinary USA corporate, the UA looks like an ordinary "Safari"

Site is HTTP, itty bitty, no commerce, info only, no great shakes ...

Had to look it up ... "Request to Change Protocols"

Is this something that might occur more frequently in the future as the web moves to HTTPS?

My server (hosted) responded with a 200, switching from HTTP/1.1 to HTTP/2.0

Only the root was requested.

Been doing "web" since 1996 and I cannot recall ever seeing this before.

Just curious

Aside: only 1 hit that resulted in 101 followed by 200...

[lucy24]

The server understands and is willing to comply with the client's request, via the Upgrade message header field . . . for a change in the application protocol being used on this connection. The server will switch protocols to those defined by the response's Upgrade header field immediately after the empty line which terminates the 101 response.

I looked it up because I wondered if there was a request header involved--as indeed there is. It seems very much analogous to the “Upgrade-Insecure-Requests” header, which I looked up not long ago after seeing it for years. The latter, it turns out, is giving the server permission to redirect the request from http to https. By now, of course, 99 sites out of 100 don’t wait for permission; we’re going to redirect everyone whether they like it or not, and if they can’t handle it, tough. (I guess the exception is if your target audience is stuck with very, very ancient browsers--I usually think of reservation schools in this context--that aren’t in their power to change.)

Within a few more years, protocol will probably be handled the same way: if you want to visit my site, you can jolly well use https/2-or-higher.