Re: git: 0c895b819c3f - main - net/http_ping: Deprecate and set expiration date to 2024-02-29
Date: Tue, 23 Jan 2024 14:59:35 UTC
On Tue, 23 Jan 2024 07:01:44 +0100 Daniel Engberg <daniel.engberg.lists@pyret.net> wrote: > > > > I do not understand why a tool with no build or functionality issue > > > > should be removed because it only supports HTTP/1.0. Do we have a > > > > policy to remove ports based on a lack of modern protocol support or > > > > fewer users? > > > > -- Hiroki > > Hi, > > There are functionality issues when HTTP 1.0 isn't supported? > > Quick example: > > http_ping https://chat.openai.com/ > > http_ping: SSL connection failed - -1 > > 002041AE453D0000:error:0A000410:SSL routines:ssl3_read_bytes:sslv3 > alert handshake > failure:/usr/src/crypto/openssl/ssl/record/rec_layer_s3.c:1586:SSL > alert number 40 > > While on Windows for comparison and what I would call expected results > using http-ping. > > HTTP-PING https://chat.openai.com/ GET > > ─→ server advertised HTTP/3 endpoint, using HTTP/3 > > 1: HTTP/3.0, 104.18.37.228:443, code=307, size=11 bytes, > time=183.2 ms > > 2: HTTP/3.0, 104.18.37.228:443, code=307, size=11 bytes, > time=186.2 ms > > 3: HTTP/3.0, 104.18.37.228:443, code=307, size=11 bytes, > time=193.5 ms > > 4: HTTP/3.0, 104.18.37.228:443, code=307, size=11 bytes, > time=187.0 ms > > --- https://chat.openai.com/ ping statistics --- > > 4 requests sent, 4 answers received, 0.0% loss > > round-trip min/avg/max/stddev = 183.215/187.493/193.535/3.764 ms > Well, yes, you demonstrated what it means if only HTTP/1.0 is supported by trying to measure the latency to a popular website. The question was if this is reason enough to deprecate a port that has a maintainer who is generally active in the project. A less intrusive alternative would have been to modify the COMMENT field to say "Measure HTTP/1.0 Latency". Cheers Michael -- Michael Gmelin