No connect: "Waiting for CAP LS response..."

[g4570n]

Hi, I updated to the latest version of irssi-git from the opensuse repo. Since I updated I have not been able to establish a connection with the irssi-proxy instance that I have in a vps.

This is the message I get:

[Xyz] Irssi: Looking up server-vps.xyz
[Xyz] Irssi: Connecting to server-vps.xyz [xxx.xxx.xx.xx] port 2777
[Xyz] Waiting for CAP LS response...
[Xyz] Irssi: Connection to server-vps.xyz established

The last line says connection established, but the channels to which I am connected do not appear and I begin to receive these messages:

[Xyz] Irssi: Connection lost to server-vps.xyz
Irssi: Removed reconnection to server server-vps.xyz port 2777
[Xyz] Irssi: Looking up server-vps.xyz
[Xyz] Irssi: Reconnecting to server-vps.xyz [xxx.xxx.xx.xx] port 2777 - use 
          /RMRECONNS to abort
[Xyz] Waiting for CAP LS response...
[Xyz] Irssi: Connection to server-vps.xyz established

I have Irssi 1.3-head (20210420 1300)

I updated from this other version, where I did not have this problem: https://github.com/irssi/irssi/compare/b2c93656..9503d4bc

perhaps this problem is related to: #1303

[ailin-nemui]

Thanks for helping test the git version. Irssi-proxy does not support the newer IRCv3 CAP LS protocol. Please try /server modify -nocap server-vps.xyz

[g4570n]

Thanks, that worked.

I did not see anything about that option in /help server

[dequis]

This looks like a bug tbh

[crabctrl]

Using -nocap seems to cause incorrect behaviour as well, with irssi seemingly assuming that the server has certain capabilities when it does not. For instance, it assumes the welcome message to be in the format :serverhost 001 <some other param> :Welcome to the IRC network..., instead of the spec-compliant format, :serverhost 001 :Welcome to the IRC network..., causing the reply to be truncated to to the IRC network... when displayed to the user (which itself seems like incorrect behaviour, the parameter starts with a colon, it should not be being split).

[ailin-nemui]

the standard reply should always be 001 <target> :welcome, so this sounds like a buggy server

[crabctrl]

Can you please link to the spec which defines that? RFC 2812 and RFC 1459 do not list a <target> parameter for 001 (as well as a large number of other replies that irssi assumes should be prefixed with a target), nor is there a target parameter listed in the BNF in those two specs.

[ailin-nemui]

this was considered canonical when the rfcs were written, compare to the implementations (irc2, ircu) or see https://modern.ircdocs.horse/#numerics