TML). HTTP was initially standardized with HTTP/1.0 version, which uses a new HTTP connection for each object transfer (non-persistent mode), where an object can be the text, a picture, etc. However, the widely spread standard over the years was HTTP/1.1, in which one HTTP connection is used for transfer of multiple objects between a client and a server (called persistent mode, or pipelining). It was standardized with RFC 2616 in 1999 [18]. After more than 15 years of HTTP 1.1 the IETF published HTTP version 2 (HTTP/2) in 2015, standardized with RFC 7540 [19]. HTTP/2 addresses several issues that were considered to be disadvantages in HTTP/ 1.0 and HTTP/1.1 regarding performance of the HTTP connection and Web traffic in general. HTTP/2 defines an optimized mapping of HTTP semantics to an underlying TCP connection. Also, it allows interleaving of request and response messages on the same connection and uses an efficient coding for HTTP header fields. Further, HTTP2 provides the possibility for prioritization of HTTP requests (from HTTP clients, i.e. Web browsers) by allowing more important requests to complete more quickly, which should result in improved performance of Web-based applications. 2.1.5.2 File Transfer Protocol (FTP) FTP is an application for copying files from one machine (i.e. host) to another. It was one of the first important application-layer protocols on the Internet (the first file transfer mechanisms were proposed in 1971 with RFC 114) [17]. It is also a client-server protocol that uses TCP/IP protocol stack. It consumes more resources on the computer than HTTP because FTP requires two processes to be estab- lished for file transfer (e.g. file upload or download), a control process (e.g. for user authentication, file administration), and data process (for file transfer). Therefore, it was rarely used after the global spread of HTTP and WWW, which are also used for file upload and download (among other possibilities) and hence make FTP redundant. Nevertheless, even in the second decade of the t