Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1251635 > unrolled thread

Bug#1107103: Salsa also broken

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1107103: Salsa also broken "Trent W. Buck" <twb@cyber.com.au> - 2025-07-02 09:50 +0200
    Bug#1107103: Salsa also broken Chris Hofstaedtler <zeha@debian.org> - 2025-07-02 13:10 +0200
      Bug#1107103: Salsa also broken "Trent W. Buck" <twb@cyber.com.au> - 2025-07-02 13:40 +0200

#1251635 — Bug#1107103: Salsa also broken

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

$ curl -sSfL --http1.1 https://salsa.debian.org/debian/logcheck | file -
/dev/stdin: HTML document, Unicode text, UTF-8 text, with very long 
lines (9923)

Testing was done on Debian 12.

[toc] | [next] | [standalone]

#1251653

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

[toc] | [prev] | [next] | [standalone]

#1251655

On 2/7/25 21:00, Chris Hofstaedtler wrote:
> 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: [...]
> Anyway, none of that is relevant for w3m TTBOMK.

My fault.

w3m didn't work, so I cross-checked with curl, which also didn't work 
for http 1.0 (but did for http 1.1).

So I guessed that meant salsa was broken for http 1.0, and mentioned it 
on the "w3m can't do github because w3m is http 1.0" bug.

It didn't occur to me that curl might fail for unrelated reasons.

Further testing shows that
"w3m https://salsa.debian.org/debian/logcheck" works, but
"dman logcheck" then clicking (^I^M) the same link fails, with error message
"Can't load https://salsa.debian.org/debian/logcheck"

I don't know what's going on there, but I agree it's not relevant to 
1107103 (w3m HTTP/1.0 client is too old for github.com).

Sorry for the noise.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web