On Wed, Jul 02, 2025 at 05:32:55PM +1000, Trent W. Buck wrote: > It looks like Salsa also requires HTTP/1.1+ now? > > How hard is it to "just" make w3m speak HTTP/1.1? > I seem to recall 1.0 and 1.1 are pretty similar. > > I just ran "dman logcheck" (with PAGER=w3m) and followed the link to > https://salsa.debian.org/debian/logcheck, but it silently failed to change > page. > > $ curl -sSfL --http1.0 https://salsa.debian.org/debian/logcheck | file - > curl: (35) OpenSSL/3.0.16: error:0A00006E:SSL routines::bad extension > /dev/stdin: empty
I'm not sure why we're discussing curl behaviour in a w3m bug. Anyway what you are seeing here is a bug in curl: it puts an alpn extension into the request, and for --http1.0 the value is "http/1.0". I doubt this is a valid value. Indeed curl from trixie (even with --http1.0) sets alpn=http/1.1, and salsa correctly returns a reply. You can also see this in curl's output if run it with -vv: ... * ALPN: offers http/1.0 ... * OpenSSL/3.0.16: error:0A00006E:SSL routines::bad extension Anyway, none of that is relevant for w3m TTBOMK. Chris
