Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>If you have a close look at the messages, you see that all but the last lines have a <code>-</code> behind the status code. The last line has a <code></code>, however, indicating, well, the last line.</p> <p>You can read that in <a href="http://www.faqs.org/rfcs/rfc959.html" rel="nofollow">RFC 959</a>, section 4.2:</p> <blockquote> <p>Thus the format for multi-line replies is that the first line will begin with the exact required reply code, followed immediately by a Hyphen, "-" (also known as Minus), followed by text. The last line will begin with the same code, followed immediately by Space , optionally some text, and the Telnet end-of-line code.</p> </blockquote> <p>There is nothing said about the 2nd to second-last line, but it is logical that they have the same format as the 1st one.</p> <hr> <p>Update: The FTP protocol seems to be badly documented, but I found another reference stating the same as me above:</p> <p>The <a href="http://www.tcpipguide.com/free/t_FTPRepliesReplyCodeFormatandImportantReplyCodes-5.htm" rel="nofollow">TCP/IP Guide</a> mentions that</p> <blockquote> <p>It is possible for a reply to contain more than one line of text. In this case, each line starts with the reply code, and all lines but the last have a hyphen between the reply code and the reply text, to indicate that the reply continues. The last line has a space between the reply code and reply text, just like a single-line reply. This facility is often used to provide additional response information after a user logs in, via the 230 reply code.</p> </blockquote>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload