ietf-nntp Section 7.1 - GREETING step.
rra at stanford.edu
Mon Jul 24 13:09:09 PDT 2000
Andrew Gierth <andrew at erlenstar.demon.co.uk> writes:
> 504 was introduced, bogusly, by INN as a "server too busy" error.
Along with 505.
** Second, if the number of entries now in the table is equal to
** the ``T'' parameter, reject the connection with the ``504''
** error code.
** 504 Server overloaded, try later
** Third, if the number of entries now in the table which match
** the incoming connection's host address is equal to the ``L''
** parameter, reject the connection with the ``505'' error code.
** 505 Connection rejected, you're making too many connects per minute
I don't see any obvious reason why these can't both be 400. I'm more
inclined to change INN than the standard here.
Russ Allbery (rra at stanford.edu) <http://www.eyrie.org/~eagle/>
More information about the ietf-nntp