Invalid 410 (ERR_INVALIDCAPCMD) response format #292

Closed
opened 2026-10-05 04:10:33 +02:00 by adam · 0 comments
Owner

The IRCv3 Client Capability Negotiation document indicates that a ERR_INVALIDCAPCMD message should contain two parameters after the client identifier: the name of the (invalid) command, and a human-readable description of the error (for information, the freenode server correctly sends both arguments).

ZNC only provide the description of the error.

In src/Client.cpp, at line 930, one just needs to add sSubCmd as second argument, before the third one (the description of the error).

The [IRCv3 Client Capability Negotiation document](http://ircv3.org/specification/capability-negotiation-3.1) indicates that a `ERR_INVALIDCAPCMD` message should contain two parameters after the client identifier: the name of the (invalid) command, and a human-readable description of the error (for information, the freenode server correctly sends both arguments). ZNC only provide the description of the error. In [`src/Client.cpp`, at line 930](https://github.com/znc/znc/blob/c99eedaac3666130110b9cdf5e548eb61b8af0dc/src/Client.cpp#L930), one just needs to add `sSubCmd` as second argument, before the third one (the description of the error). <!-- github-sync-id:26160420 -->
adam closed this issue 2026-10-05 04:10:33 +02:00
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/znc#292