Title: Communication protocol
Content:  A text-based protocol or plain text protocol represents its content in human-readable format, often in plain text. The immediate human readability stands in contrast to binary protocols which have inherent benefits for use in a computer environment (such as ease of mechanical parsing and improved bandwidth utilization). Different network applications have different methods of encapsulating data. One method very common with Internet protocols is a text oriented representation that transmits requests and responses as lines of ASCII text, terminated by a newline character (and usually a carriage return character). Examples of protocols that use plain, human-readable text for its commands are FTP (File Transfer Protocol), SMTP (Simple Mail Transfer Protocol), and the finger protocol. Text-based protocols are typically optimized for human parsing and interpretation, and are therefore suitable whenever human inspection of protocol contents is required, such as during debugging and during early protocol development design phases.
Title: File Transfer Protocol
Content:  The File Transfer Protocol (FTP) is a standard communication protocol used for the transfer of computer files from a server to a client on a computer network. FTP is built on a client–server model architecture using separate control and data connections between the client and the server. FTP users may authenticate themselves with a clear-text sign-in protocol, normally in the form of a username and password, but can connect anonymously if the server is configured to allow it. For secure transmission that protects the username and password, and encrypts the content, FTP is often secured with SSL/TLS (FTPS) or replaced with SSH 
Title: File Transfer Protocol
Content:  FTP login uses normal username and password scheme for granting access. The username is sent to the server using the USER command, and the password is sent using the PASS command. This sequence is unencrypted "on the wire", so may be vulnerable to a network sniffing attack. If the information provided by the client is accepted by the server, the server will send a greeting to the client and the session will commence. If the server supports it, users may log in without providing login credentials, but the same server may authorize only limited access for such sessions.
Title: List of HTTP header fields
Content:  HTTP header fields are a list of strings sent and received by both the client program and server on every HTTP request and response. These headers are usually invisible to the end-user and are only processed or logged by the server and client applications. They define how information sent/received through the connection are encoded (as in Content-Encoding), the session verification and identification of the client (as in browser cookies, IP address, user-agent) or their anonymity thereof (VPN or proxy masking, user-agent spoofing), how the server should handle data (as in Do-Not-Track), the age (the time it has resided in a shared cache) of the document being downloaded, amongst others.
Title: File Transfer Protocol
Content:  network, four data types are defined: An expired Internet Draft defined a TYPE U for transferring Unicode text files using UTF-8; although the draft never became an RFC, it has been implemented by several FTP clients/servers. Note these data types are commonly called "modes", although ambiguously that word is also used to refer to active-vs-passive communication mode (see above), and the modes set by the FTP protocol MODE command (see below). For text files (TYPE A and TYPE E), three different format control options are provided, to control how the file would be printed: These formats were mainly relevant to line printers; most contemporary FTP clients/servers only support the default format control of N.
Title: List of HTTP header fields
Content:  In HTTP version 1.x, header fields are transmitted after the request line (in case of a request HTTP message) or the response line (in case of a response HTTP message), which is the first line of a message. Header fields are colon-separated key-value pairs in clear-text string format, terminated by a carriage return (CR) and line feed (LF) character sequence. The end of the header section is indicated by an empty field line, resulting in the transmission of two consecutive CR-LF pairs. In the past, long lines could be folded into multiple lines; continuation lines are indicated by the presence of a space (SP) or horizontal tab (HT) as the first character on the next line. This folding is now deprecated. HTTP/2 and HTTP/3 instead use a binary protocol, where headers are encoded in a single  and zero or more   frames using HPACK (HTTP/2) or QPACK (HTTP/3), which both provide efficient header compression. The request or response line from HTTP/1 has also been replaced by several pseudo-header fields, each beginning with a colon.
Title: FTPS
Content:  Two separate methods were developed to invoke client security for use with FTP clients: Implicit and Explicit. While the implicit method requires that a Transport Layer Security is established from the beginning of the connection, which in turn breaks the compatibility with non-FTPS-aware clients and servers, the explicit method uses standard FTP protocol commands and replies in order to upgrade a plain text connection to an encrypted one, allowing a single control port to be used for serving both FTPS-aware and non-FTPS-aware clients.
Title: Hypertext Transfer Protocol
Content:  The response header fields allow the server to pass additional information beyond the status line, acting as response modifiers. They give information about the server or about further access to the target resource or related resources. Each response header field has a defined meaning which can be further refined by the semantics of the request method or response status code.
Title: Hypertext Transfer Protocol
Content: a status line, consisting of the protocol version, a space, the response status code, another space, a possibly empty reason phrase, a carriage return and a line feed, e.g.: zero or more response header fields, each consisting of the case-insensitive field name, a colon, optional leading whitespace, the field value, an optional trailing whitespace and ending with a carriage return and a line feed, e.g.: an empty line, consisting of a carriage return and a line feed; ; an optional message body. A server sends response messages to the client, which consist of: 
Title: P3P
Content: which information the server stores: ; which kind of information is collected (identifying or not); ; which particular information is collected (IP address, email address, name, etc.); ; use of the collected information: ; how this information is used (for regular navigation, tracking, personalization, telemarketing, etc.); ; who will receive this information (only the current company, third party, etc.); ; permanence and visibility: ; how long information is stored; ; whether and how the user can access the stored information (read-only, optin, optout). 1) specified in the HTTP header of the document ; 2) specified in the HTML head of the document ; 3) if none of the above is specified, the well-known location <tt>/w3c/p3p.xml</tt> is used (for a similar location compare 

Question: what information is displayed in clear text from the ftp header?
Answer: all transmissions.