JP2016038664A - Http client, http server, and http communication method - Google Patents

Abstract

An HTTP client, an HTTP server, and an HTTP communication method are provided that enable high-speed delivery of Web contents only by cooperative operation of a server and a client without causing unnecessary communication. At time t1, connection processing by a three-way handshake is performed, and at time t2, a request message in which an HTTP specific version HTTP / 1.XX is described in the first request line is transmitted. At time t3, “HTTP / 1.XX 200 OK” is described in the first status line, and a response message in which the requested Web content is described in the message body is transmitted. At time t4, a Magic code is transmitted from the client to the server as preparation for connection using HTTP / 2.0. At time t5, a SETTINGS frame is transmitted from the server to the client, and initial information of HTTP / 2.0 is exchanged. [Selection] Figure 2

Description

  The present invention provides an HTTP client, an HTTP server, and an HTTP communication method that enable high-speed Web content distribution by utilizing, for content distribution, negotiation for HTTP version setting executed prior to Web content distribution by HTTP. About.

  HTTP (Hypertext Transfer Protocol) was developed to download Web content described in HTML from the server to the browser (client). The server mainly requests the Web content from the browser to the server, and the server uses the browser. And a procedure for responding to the Web content requested by the user.

  In HTTP / 1.0, connection / disconnection of a TCP connection is repeated each time content is acquired, so the efficiency is lowered particularly when a large number of contents are included in an HTML file. In contrast, HTTP / 1.1 speeds up the display of Web pages containing a large number of image contents, mainly by the keep-alive function.

  Since HTTP / 1.1 initially had fewer connections than HTTP / 1.0 at the same time, a multi-domain web page was developed to supplement this. However, when trying to download a multi-domain web page using HTTP / 1.1, HTTP simultaneous requests are generated, which causes a new problem of increasing the load on the server and network devices.

  In order to solve such technical problems, HTTP / 2.0 has been studied as a next generation version of HTTP. This HTTP / 2.0 solves the above technical problem by realizing multiple HTTPs with a single TCP connection.

  In non-patent literature, integration of TCP connections, push delivery from a web server, multiplexed transmission of requests, deletion of redundant headers, and compression of communication data are essential as background technologies for realizing high-speed web content distribution. HTTP / 2.0 has been disclosed that realizes high-speed Web by making it easier.

  Since HTTP / 2.0 is implemented in the session layer, which is a lower layer of the application layer where the existing HTTP / 1.1 is implemented, there is no need to modify HTTP itself such as methods and headers specified in HTTP / 1.1. There is an advantage.

IETF, M. Belshe, R. Peon, M. Thomson, Ed. "Hypertext Transfer Protocol version 2" draft-ietf-httpbis-http2-10, Feb. 2014.

  Non-patent literature is a communication technology aimed at speeding up Web access. Specifically, the speed of Web content delivery is improved by efficiently using a TCP connection established between a client and a Web server. Is to do.

  At this time, since the communication format of the non-patent document is not compatible with the communication format of HTTP / 1.1, both the client and the Web need to support the communication format of the non-patent document. Therefore, it is essential to confirm (negotiate) whether the target Web server is compatible with the communication format of the non-patent document after the TCP connection is established, and the three types of negotiation procedures shown in FIG. 9 are discussed.

  Procedure 1: After establishing a TCP connection, determine the communication method using ALPN when establishing an SSL session.

  Procedure 2: After the TCP connection is established, when a request is transmitted from the client using HTTP, the communication is upgraded to the non-patent literature communication format using the Upgrade header.

  Procedure 3: Connection to a server that understands the use of non-patent documents in advance using a communication format of non-patent documents is started.

  In Procedure 1, it is essential to establish an SSL session. Therefore, for Web servers that do not support non-patent literature communication formats, additional communication required to establish an SSL session between the Web server and the client occurs in comparison with communication using HTTP / 1.1. End up.

  In step 2, instead of establishing an SSL session, an HTTP upgrade is performed using the Upgrade header and 101 status code defined in HTTP / 1.1. However, along with the occurrence of the upgrade procedure, one round trip of communication between the Web server and the client occurs before the shift to the communication format of the non-patent literature.

  In step 3, the client needs to recognize in advance that the Web server is compatible with the communication format of non-patent literature, and a new implementation is required for the server and a third node other than the client (for example, DNS). End up.

  SUMMARY OF THE INVENTION An object of the present invention is to solve the above technical problem, and to enable high-speed delivery of Web contents by only the cooperative operation of the server and client without causing unnecessary communication, HTTP client, HTTP server, and HTTP communication method Is to provide.

  (1) The HTTP client of the present invention corresponds to the relatively higher and lower versions of HTTP, and generates a request message for requesting HTTP communication by a minor version of the lower version, and sends the request message to the server. A means for sending and receiving a response message, a means for acquiring content registered in a response message for accepting HTTP communication by a minor version, and a communication by a higher version for a response message for accepting HTTP communication by a minor version And a means to lead.

  (2) The HTTP server according to the present invention corresponds to relatively higher and lower versions of HTTP, and includes a means for receiving a request message from an HTTP client and a request message for requesting HTTP communication by a minor version of the lower version. On the other hand, there is provided means for generating a response message for registering the requested content and accepting the communication by the minor version, and means for returning the response message to the HTTP client.

  (3) The HTTP communication method of the present invention is a communication method by a client and a server corresponding to relatively higher and lower versions of HTTP, and the client requests HTTP communication by a minor version of the lower version. And sending a response message confirming that the requested content has been registered to the client and confirming communication with the minor version, and the client performing HTTP communication with the minor version. And a procedure for leading communication by an upper version of HTTP for the response message to be understood.

According to the present invention, the following effects are achieved.
(1) When a client sends a unique minor version "HTTP / 1.XX" as an HTTP version in the request line of an HTTP request message that requests content delivery, the server that received it sends the requested content. Register at least a part of HTTP response message and deliver it. Therefore, content can be distributed even during negotiation without modifying the existing HTTP, so high-speed distribution of Web content is realized.

  (2) If only the client is compatible with the HTTP communication method of the present invention and the server is not compatible with the conventional HTTP / 1.1, content distribution by HTTP / 1.1 becomes possible.

  (3) If only the client supports the HTTP communication method of the present invention and the server does not support HTTP / 2.0, content distribution by HTTP / 2.0 becomes possible.

It is the functional block diagram which showed the structure of the principal part of the HTTP client and HTTP server to which the HTTP communication method which concerns on one Embodiment of this invention is applied. It is the sequence flow which showed the HTTP connection procedure in case both a client and a server respond | correspond to the HTTP communication system of this invention. It is the figure which showed an example of the HTTP request message transmitted / received in the sequence of FIG. It is the figure which showed an example of the HTTP response message transmitted / received in the sequence of FIG. It is the sequence flow which showed the HTTP connection procedure in case only a client respond | corresponds to the HTTP communication system of this invention, and a server does not respond | correspond. It is the figure which showed an example of the HTTP response message transmitted / received in the sequence of FIG. It is the sequence flow which showed the HTTP connection procedure in case only a client respond | corresponds to the HTTP communication system of this invention, and a server does not respond | correspond but HTTP / 2.0. It is the figure which showed an example of the HTTP response message transmitted / received in the sequence of FIG. It is the sequence flow which showed the HTTP connection procedure of the prior art.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. FIG. 1 is a functional block diagram showing a configuration of main parts of an HTTP client 1 and an HTTP server 2 to which an HTTP communication method according to an embodiment of the present invention is applied. Here, configurations unnecessary for the description of the present invention are shown. The illustration is omitted.

  The HTTP client 1 corresponds to HTTP / 1.1 and HTTP / 2.0 as relatively lower and upper major versions of HTTP, respectively. As will be described in detail later, the request message generation unit 101 is an HTTP / 1.1 minor version HTTP / 1.XX (the major number is “1” and the minor number is “XX” unique to the present invention. For example, an HTTP request message for requesting communication conforming to HTTP / 1.2) to the HTTP server 2 is generated.

  The message transmission / reception unit 102 transmits the HTTP request message to the HTTP server 2 by communication conforming to HTTP / 1.1, and receives an HTTP response message returned from the HTTP server 2 in response thereto.

  Similar to the HTTP client 1, the HTTP server 2 corresponds to HTTP / 1.1 and HTTP / 2.0, respectively, as relatively lower and upper major versions of HTTP. The message transmission / reception unit 201 receives a request message transmitted from the HTTP client 1 and returns a response message in response thereto.

  The response message generation unit 202 of the HTTP server 2 includes a content registration unit 202a, and generates a response message that responds to an HTTP request message that requests HTTP communication using the minor version HTTP / 1.XX. In the present embodiment, as will be described in detail later, a message indicating that communication by the minor version HTTP / 1.XX is accepted is described in response to the response message, and further requested by the content registration unit 202a. The Web content is read from the content DB 204 and registered in the message body of the response message.

  When the content extraction unit 103 of the HTTP client 1 receives an HTTP response message that accepts HTTP communication according to the minor version HTTP / 1.XX, the content extraction unit 103 acquires Web content registered in the message body.

  The communication execution units 104 and 203 of the HTTP client 1 and HTTP server 2 correspond to HTTP major versions HTTP / 1.1, HTTP / 2.0, and minor versions HTTP / 1.XX. The communication execution unit 104 leads the communication by HTTP / 2.0 in cooperation with the communication execution unit 203 of the HTTP server 2 in response to the HTTP response message for accepting the HTTP communication by the minor version HTTP / 1.XX, The remaining Web content is acquired at high speed from the content DB 204 of the HTTP server 2 by communication conforming to HTTP / 2.0.

  FIG. 2 is a sequence flow showing an HTTP connection procedure when both the client and the server are compatible with the HTTP communication method of the present invention, and FIGS. 3 and 4 are HTTP flows transmitted from the client to the server, respectively. 2 shows an example of a request message and an HTTP response message transmitted from the server to the client.

  In FIG. 2, at time t1, a well-known connection process is performed between the client and the server by a three-way handshake, the SYN packet is transmitted from the client to the server, the SYN ACK packet is transmitted from the server to the client, and the client to the server. A connection is established through the transmission of an ACK packet to.

  At time t2, an HTTP request message is transmitted from the client to the server. In this HTTP request message, as shown in FIG. 3, HTTP / 1. Is the HTTP version in the first request line, the major number is “1”, and the minor number is “XX” unique to the present invention. XX (for example, HTTP / 1.2) is described and transmitted in accordance with the latest version of HTTP / 1.1 corresponding to the major number “1”.

  The server that received the HTTP request message refers to the HTTP version described in the request line, and here it is determined that it corresponds to the requested version "HTTP / 1.XX". At t3, the HTTP response message shown in FIG. 4 is transmitted. In this embodiment, “HTTP / 1.XX 200 OK” is described in the status line of the HTTP response message as a message “HTTP / 1.XX communication is possible”, and the request Content (HTML file) is described in the message body.

  At the time t4, the client that has received the HTTP response message recognizes that the server also supports HTTP / 2.0 because “HTTP / 1.XX 200 OK” is described in the status line. , Send a 24-byte Magic code to the server to prepare for HTTP / 2.0 connection.

  At time t5, a SETTINGS frame including information such as the initial window size and the maximum number of simultaneous open streams is transmitted from the server to the client, and HTTP / 2.0 initial information is exchanged. At time t6, a content request according to HTTP / 2.0 is transmitted from the client to the server, and content distribution conforming to HTTP / 2.0 is continued.

  According to the present embodiment, when a client describes a minor version “HTTP / 1.XX” as an HTTP version in the request line of an HTTP request message for requesting content delivery, the server that has received this transmits Register and distribute at least part of the requested content in the HTTP response message. Therefore, content can be distributed even during negotiation without modifying the existing HTTP, so high-speed distribution of Web content is realized.

  FIG. 5 is a sequence flow showing an HTTP connection procedure when only the client supports the HTTP communication method of the present invention and the server does not support. FIG. 6 shows an HTTP response message transmitted from the server to the client. An example is shown.

  At time t1, connection processing by three handshakes is executed, and at time t2, an HTTP request message in which HTTP / 1.XX is described as the HTTP version in the first request line is HTTP / Sent from the client to the server in accordance with 1.1.

  The server that has received the HTTP request message does not support the requested version HTTP / 1.XX. Therefore, at time t3, a message “HTTP / 1.1 communication is possible” is displayed as an HTTP / 1.1 200 message. When the HTTP response message is transmitted, the client transmits a content request according to HTTP / 1.1 at time t4, so that content distribution conforming to HTTP / 1.1 is started.

  As described above, according to the present embodiment, only the client supports the HTTP communication method of the present invention, and even if the server is not compatible, if the conventional HTTP / 1.1 is supported, content distribution by HTTP / 1.1 is possible. Is possible.

  FIG. 7 is a sequence flow showing an HTTP connection procedure when only the client corresponds to the HTTP communication method of the present invention, the server does not support HTTP / 2.0, and FIG. 8 shows transmission from the server to the client. An example of the HTTP response message to be executed is shown.

  At time t1, connection processing by three handshakes is executed, and at time t2, an HTTP request message in which HTTP / 1.XX is described as the HTTP version in the first request line is HTTP / Sent from the client to the server in accordance with 1.1.

  The server that has received the HTTP request message does not support the requested version HTTP / 1.XX. Therefore, at time t3, as shown in FIG. “101 Switching Protocols” is described, and an HTTP response message in which “Upgrade: HTTP / 2.0” is described is transmitted as a message requesting an upgrade to HTTP / 2.0 in the message body.

  The client that has received the HTTP response message recognizes that the server is compatible with “HTTP / 2.0”, and transmits a 24-byte Magic code to the server as a connection preparation by HTTP / 2.0 at time t4.

  At time t5, a SETTINGS frame including information such as the initial window size and the maximum number of simultaneous open streams is transmitted from the server to the client, and HTTP / 2.0 initial information is exchanged. At time t6, a content request according to HTTP / 2.0 is transmitted from the client to the server, and content distribution conforming to HTTP / 2.0 is continued.

  According to this embodiment, even if only the client supports the HTTP communication method of the present invention and the server does not support it, content distribution by HTTP / 2.0 becomes possible if it supports conventional HTTP / 2.0. .

  DESCRIPTION OF SYMBOLS 1 ... HTTP client, 2 ... HTTP server, 101 ... Request message generation part, 102 ... Message transmission / reception part, 103 ... Content extraction part, 104, 203 ... Communication execution part, 201 ... Message transmission / reception part, 202 ... Response message generation part, 202a ... content registration unit, 204 ... content DB

Claims (11)

In HTTP clients that support relatively higher and lower versions of HTTP,
Means for generating an HTTP request message for requesting HTTP communication by a minor version of the lower version;
Means for transmitting the HTTP request message to a predetermined server and receiving an HTTP response message;
Means for acquiring content registered in an HTTP response message for accepting HTTP communication by the minor version;
An HTTP client comprising: means for leading communication by the higher version in response to an HTTP response message for accepting HTTP communication by the minor version.   The HTTP client according to claim 1, wherein the minor version has the same major number as the lower version and a unique minor number.   The HTTP client according to claim 2, wherein the upper version is HTTP / 2.0 and the lower version is HTTP / 1.1.   4. The HTTP client according to claim 1, wherein the means for initiating communication leads the communication by the lower version in response to an HTTP response message for accepting the HTTP communication by the lower version.   4. The HTTP client according to claim 1, wherein the means for initiating communication leads the communication by the higher version in response to an HTTP response message for accepting the HTTP communication by the higher version. In the HTTP server corresponding to each upper and lower version of HTTP,
Means for receiving an HTTP request message from an HTTP client;
Means for generating an HTTP response message for registering the requested content and accepting the communication by the minor version for the HTTP request message requesting the HTTP communication by the minor version of the lower version;
An HTTP server comprising: means for returning the HTTP response message to the HTTP client.   The HTTP server according to claim 6, wherein the minor version has the same major number as the lower version and a unique minor number.   8. The HTTP server according to claim 7, wherein the upper version is HTTP / 2.0 and the lower version is HTTP / 1.1. In the HTTP communication method by the client and server corresponding to the relatively higher and lower versions of HTTP,
A procedure for a client to generate an HTTP request message for requesting HTTP communication by a minor version of the lower version and send it to a server;
A procedure in which an HTTP response message requesting HTTP communication by the minor version of the lower version is sent back to the HTTP response message in which the requested content is registered and the communication by the minor version is accepted;
A procedure for the client to acquire the content registered in the HTTP response message for accepting HTTP communication by the minor version;
The HTTP communication method comprising: a procedure in which a client leads communication by the higher version in response to an HTTP response message for accepting HTTP communication by the minor version.   The HTTP communication method according to claim 9, wherein the minor version has the same major number as the lower version and a unique minor number.   11. The HTTP communication method according to claim 10, wherein the upper version is HTTP / 2.0 and the lower version is HTTP / 1.1.