Custom Query (44 matches)

According to RFC 3977, section 3.4.1:

Except as an effect of the MODE READER command (Section 5.3) on a mode-switching server, once a server advertises either or both of the IHAVE or READER capabilities, it MUST continue to advertise them for the entire session.

If IHAVE has been advertised, it will not necessarily be advertised for the entire session. innd and nnrpd only advertise the IHAVE capability when it is really available.

Impact: Probably none. It is sort of a weird edge case, since having such basic commands disappear after authentication is a little odd and would require an unusual configuration. It is probably not worth fixing. Besides, such a fix seems to partly defeat the point of the capability system.

According to RFC 2980, section 2.8:

If no articles are in the range specified, a 420 error response is returned by the server.

nnrpd (from the beginning of the XOVER command) has always returned a 224 response with an empty multiline response instead.

Note that the OVER command properly returns 423 (no articles in that range) when that case occurs. 420 is sent when the current article number is invalid.

Impact: Less information is communicated to the client about why there are no overview records returned. An error response indicating there are no valid articles in that range is possibly more informative.

There is probably no way to fix this now. Changing the reply codes would break a few existing implementations: it may confuse some clients that don't expect to get 420 errors back from overview queries. Clients may be relying on the existing behavior (confirmed with Outlook Express/Windows? Mail for instance).

Perl and Python authentication filters for nnrpd should be able to return the new 403 response code (besides 281 and 481).

Keep mapping 502 to 481 for backwards compatibility with INN 2.4 and RFC 2980.