Please Whitelist This Site?
I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)
If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.
If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.
Thanks for your understanding!
Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide
|
NOTE: Using software to mass-download the site degrades the server and is prohibited. If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.
|
|
|
|
NNTP Status Responses and Response Codes
(Page 2 of 3)
Reply Code Structure and Digit Interpretation
As with SMTP and FTP, NNTP reply
codes can be considered to be of the form xyz, where x
is the first digit, y the second and z the third.
First Reply Code Digit (x)
The first digit indicates the success,
failure or progress of the command in general terms, whether a successful
command is complete or incomplete, and the general reason why an unsuccessful
command did not work. The values of this digit are defined slightly
differently than in SMTP and FTP. In some cases, the terminology is
just simplified; for example, the second category is Command OK
instead of Positive Completion Reply. Table 270
shows the specific meaning of the possible values of this digit.
Table 270: NNTP Reply Code Format: First Digit Interpretation
Reply
Code Format
|
Meaning
|
Description
|
1yz
|
Informative
Message
|
General information; used for
help information and debugging.
|
2yz
|
Command
OK
|
The command
was completed successfully.
|
3yz
|
Command OK
So Far, Send The Rest
|
An intermediate reply, sent to
prompt the client to send more information. Typically used for replies
to commands such as IHAVE or POST, where the server acknowledges
the command and then requests that an article be transmitted by the
client.
|
4yz
|
Command
Was Correct, But Couldn't Be Performed
|
The command
was valid but could not be performed. This type of error usually occurs
due to bad parameters, a transient problem with the server, bad command
sequence or similar situations.
|
5yz
|
Command Unimplemented
Or Incorrect, Or Serious Program Error
|
The command was invalid or a
significant program error prevented it from being performed.
|
Second Reply Code Digit (y)
The second digit categorizes messages
into functional groups. This digit is used in the same general way as
in SMTP and FTP, but the functional groups are different; they are described
in Table 271.
Table 271: NNTP Reply Code Format: Second Digit Interpretation
Reply
Code Format
|
Meaning
|
Description
|
x0z
|
Connection,
Setup and Miscellaneous
|
Generic and miscellaneous replies.
|
x1z
|
Newsgroup
Selection
|
Messages related
to commands used to select a newsgroup.
|
x2z
|
Article Selection
|
Messages related to commands
used to select an article.
|
x3z
|
Distribution
Functions
|
Messages related
to the transfer of messages.
|
x4z
|
Posting
|
Messages related to posting messages.
|
x5z
|
Authentication
|
Messages related
to authentication and the AUTHINFO command extension. (This category
is not officially listed in the standard, but these responses have a
middle digit of 5).
|
x8z
|
Nonstandard
Extensions
|
Reserved for private, non-standard
implementation use.
|
x9z
|
Debugging
|
Debugging output
messages.
|
Third Reply Code Digit (z)
This last digit indicates a specific
type of message within each of the functional groups described by the
second digit. The third digit allows each functional group to have 10
different reply codes for each reply type given by the first code digit.
Combining Digit Values to Make Specific Reply Codes
As in FTP and SMTP, these x,
y and z digit meanings are combined to make
specific reply codes. For example, the reply code 435 is
sent by the server if a client issues the IHAVE command but the
server doesn't want the article being offered. The command was correct
but the reply is negative, thus it starts with 4, and the
message is related to message distribution, so the middle digit is 3.
If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support! |
|
|
Home -
Table Of Contents - Contact Us
The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005
© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.
|