From 01884dbf7ffce98b63de5a41be9f9aaae1bd6125 Mon Sep 17 00:00:00 2001 From: Shivaram Lingamneni Date: Tue, 8 Oct 2024 18:54:34 -0400 Subject: [PATCH 1/2] clarify that servers SHOULD send RPL_WHOIS --- _includes/messages/user_queries.md | 16 +++++----------- 1 file changed, 5 insertions(+), 11 deletions(-) diff --git a/_includes/messages/user_queries.md b/_includes/messages/user_queries.md index ef970c2..4db1a60 100644 --- a/_includes/messages/user_queries.md +++ b/_includes/messages/user_queries.md @@ -48,17 +48,8 @@ Reply Examples: Command: WHOIS Parameters: [] -This command is used to query information about particular users. -The server will answer this command with several numeric messages with information about the nicks, ending with [`RPL_ENDOFWHOIS`](#rplendofwhois-318). - -Servers MUST end their reply to `WHOIS` messages with one of these numerics: - -* {% numeric ERR_NOSUCHNICK %} -* {% numeric ERR_NOSUCHSERVER %} -* {% numeric ERR_NONICKNAMEGIVEN %} -* {% numeric RPL_ENDOFWHOIS %}otherwise, even if they did not send any other numeric message. This allows clients to stop waiting for new numerics. - -In exceptional error conditions, servers MAY not reply to a `WHOIS` command. Clients SHOULD implement a hard timeout to avoid waiting for a reply which won't come. +This command is used to query information about a particular user. +The server SHOULD answer this command with numeric messages with information about the nick, ending with [`RPL_ENDOFWHOIS`](#rplendofwhois-318), even if they did not send any other numeric message. This allows clients to stop waiting for new numerics. In exceptional error conditions, servers MAY not reply to a `WHOIS` command. Clients SHOULD implement a hard timeout to avoid waiting for a reply which won't come. Client MUST NOT not assume all numeric messages are sent at once, as server can interleave other messages before the end of the WHOIS response. @@ -67,6 +58,9 @@ Typically, it is used by clients who want to know how long the user in question The following numerics MAY be returned as part of the whois reply: +* {% numeric ERR_NOSUCHNICK %} +* {% numeric ERR_NOSUCHSERVER %} +* {% numeric ERR_NONICKNAMEGIVEN %} * {% numeric RPL_WHOISCERTFP %} * {% numeric RPL_WHOISREGNICK %} * {% numeric RPL_WHOISUSER %} From d36f612bf22722801031213db274d07e1d99cc6c Mon Sep 17 00:00:00 2001 From: Shivaram Lingamneni Date: Mon, 14 Oct 2024 22:29:25 -0400 Subject: [PATCH 2/2] clarify that the SHOULD only applies to well-formed queries --- _includes/messages/user_queries.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/_includes/messages/user_queries.md b/_includes/messages/user_queries.md index 4db1a60..f395c56 100644 --- a/_includes/messages/user_queries.md +++ b/_includes/messages/user_queries.md @@ -49,7 +49,9 @@ Reply Examples: Parameters: [] This command is used to query information about a particular user. -The server SHOULD answer this command with numeric messages with information about the nick, ending with [`RPL_ENDOFWHOIS`](#rplendofwhois-318), even if they did not send any other numeric message. This allows clients to stop waiting for new numerics. In exceptional error conditions, servers MAY not reply to a `WHOIS` command. Clients SHOULD implement a hard timeout to avoid waiting for a reply which won't come. +The server SHOULD answer this command with numeric messages with information about the nick. + +The server SHOULD end its response (to a syntactically well-formed client message) with [`RPL_ENDOFWHOIS`](#rplendofwhois-318), even if it did not send any other numeric message. This allows clients to stop waiting for new numerics. In exceptional error conditions, servers MAY not reply to a `WHOIS` command. Clients SHOULD implement a hard timeout to avoid waiting for a reply which won't come. Client MUST NOT not assume all numeric messages are sent at once, as server can interleave other messages before the end of the WHOIS response.