Response Code Separation (was: ietf-nntp DEBUG command x9x)

Lee Kindness lkindness at csl.co.uk
Mon Aug 7 05:59:40 PDT 2000


Clive D.W. Feather writes:
 > Lee Kindness said:
 > > I admit it's not very clear, however all current implementations
 > > separate the response code from any parameters (or commentary) by a
 > > single space.
 > So we *could* document it as current practice if we wanted.

It is in the current draft (page 4, 4.1 Response Codes):

  Parameters MUST be separated from the numeric status indicator
  and from each other by a single US-ASCII space. All numeric
  parameters MUST be in base 10 (decimal) format, and MAY have
  leading zeros. All string parameters MUST begin after the
  separating space, and MUST end before the following separating
  space or the US-ASCII CRLF pair at the end of the line.
  (Therefore, string parameters MUST NOT contain US-ASCII
  spaces.) All text, if any, in the response which is not a
  parameter of the response must follow and be separated from
  the last parameter by an US-ASCII space.  Also, note that the
  text following a response number may vary in different
  implementations of the server. The 3-digit numeric status
  indicator should be used to determine what response was sent.



More information about the ietf-nntp mailing list