JP5488349B2 - Relay device, relay method, and relay program - Google Patents

Description

  The present invention relates to a relay device, a relay method, and a relay program.

  In order to enhance security, a relay device called a reverse proxy server may be installed between a web browser and a web server. In this case, the request (Request) of the Web browser is not transmitted directly to the Web server, but is transmitted to the Web server via the relay device.

  When the relay device receives a request from the Web browser, the relay device specifies a URL (Uniform Resource Locator) for acquiring a resource from the Web server. The relay device specifies the URL based on the description of the specific part in the URL included in the request received from the Web browser. When the URL is specified, the relay device rewrites the URL included in the request received from the Web browser with the specified URL. The relay device transmits the rewritten request to the Web server.

  FIG. 21 is an explanatory diagram of a URL rewriting procedure by the relay device. As illustrated in FIG. 21, the relay device 120 is disposed between the Web browser 111 and the Web server 130 of the terminal device 110. In the following, an example in which the Web browser 111 acquires the HTML file “A.html” from the Web server 130 in order to display a Web page based on the HTML file “A.html” on the display unit 112 will be described. Note that the domain name of the relay device 120 is “server” and the domain name of the Web server 130 is “domain1”.

  As shown in FIG. 21, the Web browser 111 of the terminal device 110 transmits a request to the relay device 120 (step S100). In step S100, the URL included in the request transmitted from the Web browser 111 is “http: // server / http: domain1 / A.html”.

  When receiving the request from the Web browser 111, the relay device 120 converts the URL included in the received request by the conversion unit 121 (step S101). Specifically, the relay device 120 converts the URL included in the request from “http: // server / http: domain1 / A.html” to “http: //domain1/A.html” by the conversion unit 121. . The relay device 120 transfers the request whose URL has been converted by the conversion unit 121 to the Web server 130 (step S102).

  When the Web server 130 receives the request from the relay device 120, the Web server 130 reads the HTML file “A.html” based on the URL “http: //domain1/A.html” included in the received request. The Web server 130 transmits a response including the read HTML file “A.html” to the relay device 120 (step S103). The relay device 120 transfers the response received from the Web server 130 to the Web browser 111.

  When receiving the HTML file “A.html”, the Web browser 111 converts the link destination URL included in the received HTML file “A.html” (step S104). The link destination URL is a URL in which a hyperlink is set by an HTML file. As the link destination URL, for example, “http: //domain1/F.html” is described in the HTML file “A.html”. In this case, the Web browser 111 changes “http: //domain1/F.html” to “http: // server / http: domain1 / F.html”. With this change, the transmission destination of the request by the Web browser 111 is changed from the Web server 130 to the relay device 120. That is, the description in the HTML file “A.html” is converted so that the HTML file “F.html” is acquired by the Web browser 111 via the relay device 120.

JP 2004-94805 A

  However, if the link destination URL is described with an incorrect relative path in the HTML file, the request from the Web browser 111 may not be transmitted from the relay device 120 to the Web server 130.

  Specifically, in the HTML file, a relative path indicating a non-existing upper layer is described as a link destination URL. In this case, the request transmitted from the Web browser 111 to the relay device 120 is not transmitted from the relay device 120 to the Web server 130.

  For example, it is assumed that the Web browser 111 specifies the URL “http: // server / http: domain1 / A.html” and acquires the HTML file “A.html” as shown in FIG. Further, it is assumed that “../B.html” is described as a certain link destination URL in the HTML file “A.html” acquired by the Web browser 111. The correct URL for acquiring the HTML file “B.html” from the Web server 130 is “./B.html” when described in a relative path, and “http // server / http: domain1 / B.html ".

  FIG. 22 is an explanatory diagram of a URL rewriting procedure when an incorrect relative path is described as a link destination URL. When the Web browser 111 acquires the HTML file “A.html” from the Web server 130, the Web browser 111 converts the link destination URL described by the absolute path as shown in step S104 of FIG. On the other hand, the link destination URL described by the relative path is not converted. Therefore, “../B.html” in which the link destination URL is described with a relative path is not converted.

  When the link destination URL “../B.html” is designated as a request target, the Web browser 111 converts the link destination URL into a URL described with an absolute path (step S105). Here, the link source URL is “http: // server / http: domain1 / A.html”, and “../” is a description indicating one level higher. Therefore, the Web browser 111 considers the HTML file “B.html” to be in the same hierarchy as “http: domain1”, which is one level higher than the HTML file “A.html”. Therefore, the Web browser 111 converts the relative path “../B.html” of the link destination URL into the absolute path “http: //server/B.html”. Since the correct absolute path of the link destination URL is “http: // server / http: domain1 / B.html” as described above, the Web browser 111 generates an incorrect URL.

  The link destination URL “http: //server/B.html” converted in step S105 is set in the request as a request URL and transmitted from the Web browser 111 to the relay device 120 (step S106). Since the request URL does not include the domain name of the Web server 130, the conversion unit 121 of the relay device 120 cannot convert the URL (step S107). Therefore, the relay apparatus 120 cannot transfer the request because the Web server to which the request is to be transferred is unknown.

  The phenomenon in which a request cannot be transferred in the relay device 120 occurs similarly even when the relay device 120 converts the link destination URL in the HTML file. This is because the conversion method of the relay device 120 is the same as that of the Web browser 111. Therefore, when a relative path indicating a non-existing upper layer is described as a link destination URL, the link destination URL after conversion by the relay device 120 is an incorrect URL. Such an incorrect link destination URL is passed from the relay apparatus 120 to the Web browser 111. Therefore, the Web browser 111 transmits a request including an incorrect link destination URL to the relay device 120, and the same phenomenon as that when the Web browser 111 converts the URL occurs.

  Thus, when a request based on a relative path indicating a non-existing upper layer is transmitted from the Web browser 111, the relay apparatus 120 cannot transfer the request. Accordingly, the Web browser 111 cannot acquire the resource corresponding to the request from the Web server 130 even though the Web browser 111 has transmitted the request.

  The disclosed technology has been made in view of the above, and provides a relay device, a relay method, and a relay program capable of determining a correct transmission destination for a request based on a relative path indicating a non-existing upper layer. For the purpose.

  The relay apparatus which this application discloses is provided with the determination part, the extraction part, and the insertion part in one aspect. The determination unit determines whether the resource identifier included in the request received from the browser conforms to a predetermined format. When the determination unit determines that the resource identifier does not conform to a predetermined format, the extraction unit extracts the domain name of the server included in the resource identifier that is a link source of the resource identifier from the request. The insertion unit inserts the domain name of the server extracted by the extraction unit after the domain part of the resource identifier included in the request.

  According to one aspect of the technology disclosed in the present application, it is possible to determine a correct transmission destination for a request based on a relative path indicating a non-existing upper layer.

FIG. 1 is a diagram illustrating a configuration of a communication system including a relay device according to the first embodiment. FIG. 2 is a diagram illustrating URL conversion processing of the relay device according to the first embodiment. FIG. 3 is a diagram illustrating URL conversion processing of the relay device according to the first embodiment. FIG. 4 is a diagram illustrating URL conversion processing of the relay device according to the first embodiment. FIG. 5 is a diagram illustrating URL conversion processing of the relay device according to the first embodiment. FIG. 6 is a block diagram illustrating the configuration of the relay device according to the first embodiment. FIG. 7 is a diagram for explaining processing of the insertion unit of the relay device according to the first embodiment. FIG. 8 is a diagram illustrating a response transmitted from the response unit of the relay device according to the first embodiment. FIG. 9 is a sequence diagram illustrating processing of the relay device according to the first embodiment. FIG. 10 is a sequence diagram illustrating processing of the relay device according to the first embodiment. FIG. 11 is a sequence diagram illustrating processing of the relay device according to the first embodiment. FIG. 12 is a block diagram illustrating the configuration of the relay device according to the second embodiment. FIG. 13 is a diagram illustrating an example of a communication log stored in the storage unit of the relay device according to the second embodiment. FIG. 14 is a schematic diagram illustrating a process performed by the determination unit of the relay device according to the second embodiment. FIG. 15 is a sequence diagram illustrating processing of the relay device according to the second embodiment. FIG. 16 is a sequence diagram illustrating processing of the relay device according to the second embodiment. FIG. 17 is a block diagram illustrating the configuration of the relay device according to the third embodiment. FIG. 18 is a sequence diagram illustrating the processing of the relay device according to the third embodiment. FIG. 19 is a diagram illustrating a configuration of a communication system including a relay device according to the fourth embodiment. FIG. 20 is a block diagram illustrating the configuration of the relay device according to the fourth embodiment. FIG. 21 is an explanatory diagram of a conventional URL rewriting procedure. FIG. 22 is an explanatory diagram of a conventional URL rewriting procedure.

  Exemplary embodiments of a relay device, a relay method, and a relay program according to the present invention will be described below in detail with reference to the accompanying drawings.

  In the following embodiments, the URL conversion function, configuration, and processing flow of the relay apparatus according to the first embodiment will be described in order, and finally the effects of the first embodiment will be described.

[URL conversion function of relay device]
First, the URL conversion function of the relay device 3 according to the first embodiment will be described with reference to FIGS. FIG. 1 is a diagram illustrating a configuration of a communication system including the relay device 3 according to the first embodiment. 2 to 5 are diagrams illustrating the URL conversion function of the relay device 3 according to the first embodiment. In the following, it is assumed that the domain name of the relay device 3 is “server” and the domain name of the Web server 4 is “domain1”. Further, for communication between the Web browser 2 and the relay device 3 and communication between the relay device 3 and the Web server 4, HTTP (Hypertext Transfer Protocol) or the like is used as a communication protocol.

  As illustrated in FIG. 1, the relay device 3 according to the first embodiment is a local proxy disposed in a terminal device 1 having a Web browser 2. The relay device 3 is also called a reverse proxy and relays a request from the Web browser 2. That is, the request of the Web browser 2 is not transmitted directly to the Web server 4 but is transmitted to the Web server 4 via the relay device 3.

  The request transmitted from the Web browser 2 includes information such as a request line, a message header, and a message body. The request line includes a request URL. The request URL is a URL (Uniform Resource Locator) of a resource to be acquired by the Web browser 2. Examples of resources include an HTML file, image data, moving image data, and music data. The URL is an example of a resource identifier. That is, the URL is a URI (Uniform Resource Identifier), which is a description method that indicates the location of a resource that exists on the network.

  When the relay apparatus 3 receives the request from the Web browser 2, the relay apparatus 3 specifies the URL of the resource from the request URL included in the received request. For example, it is assumed that the request URL is the URL shown in FIG. That is, it is assumed that “http”, “server”, and “http: domain1 / A.html” are described in the scheme part, domain part, and path part of the URL included in the request, respectively. In this case, as illustrated in FIG. 3, the relay device 3 identifies the resource URL “http: //domain1/A.html” from the path portion “http: domain1 / A.html” of the request URL. In the scheme part, a protocol name for acquiring a resource is described. In the domain part, the domain name of a device having resources such as the Web server 4 is described. In the path part, information on the location of the resource in the device designated in the domain part is described. For example, a file name including a directory name and a folder name is described in the path portion.

  When the resource URL is specified, the relay device 3 rewrites the request URL with the resource URL. The relay device 3 transmits the request with the URL rewritten as described above to the Web server 4 via the network 5.

  As described above, when the relay apparatus 3 according to the first embodiment receives a request from the Web browser 2, the domain part of the request URL included in the received request is converted from the domain name of the relay apparatus 3 to the domain name of the Web server 4. To do. By doing so, a request from the Web browser 2 is transmitted to the Web server 4 via the relay device 3.

  In response to a request from the Web browser 2 via the relay device 3, the Web server 4 transmits a response including an HTML file corresponding to the request URL to the relay device 3. The relay device 3 transfers the response received from the Web server 4 to the Web browser 2. When the Web browser 2 receives the HTML file, the Web browser 2 converts the URL described in the absolute path among the link destination URLs included in the received HTML file into a URL having the relay device 3 as a transmission destination. For example, when “http: //domain1/G.html” is described as the link destination URL in the received HTML file, the Web browser 2 changes the link destination URL to “http: // server / http: domain1”. /G.html ".

  As described above, the Web browser 2 rewrites the HTML file so that the domain part of the link destination URL becomes the domain name of the relay device 3. Therefore, the Web browser 2 requests and acquires resources such as image data and HTML files provided by the Web server 4 via the relay device 3.

  Further, the Web browser 2 converts the link destination URL so that the path name of the request URL includes the domain name of the Web server 4 or the resource path name. Therefore, the relay device 3 can rewrite the request URL included in the received request to the URL of the Web server 4 when receiving the request from the Web browser 2. The URL of the Web server 4 is a URL for acquiring a source from the Web server 4.

  By the way, the link destination URL may be described with a relative path. In this case, the Web browser 2 does not convert the link destination URL when acquiring the HTML file, and converts the link destination URL when the link destination URL is designated as a request target. The conversion of the link destination URL is performed based on the link source URL.

  For example, it is assumed that the link source URL is “http: // server / http: domain1 / A.html” and the link destination URL is described as “./B.html” with a relative path. “./” is a description indicating the same level, and the HTML file “B.html” is the same level as the HTML file “A.html”. For this reason, the Web browser 2 converts the link destination URL described in the relative path into the absolute path “http: // server / http: domain1 / B.html”. The Web browser 2 transmits a request with the link destination URL thus converted as a request URL.

  However, when a relative path indicating a non-existing upper layer is described as a link destination URL, the path name of the link destination URL converted by the Web browser 2 does not include the domain name of the Web browser 2.

  For example, assume that the Web browser 2 specifies the URL “http: // server / http: domain1 / A.html” and acquires the HTML file “A.html”. Assume that the relative path “../B.html” is described as the link destination URL in the HTML file “A.html”. “../” is a description indicating one level higher. Therefore, the HTML file “B.html” is regarded by the Web browser 2 to be in the same hierarchy as “http: domain1”, which is one level higher than the HTML file “A.html”.

  Therefore, as shown in FIG. 4, the Web browser 2 converts the link destination relative path “../B.html” based on the link source URL “http: // server / http: domain1 / A.html”. Convert to “http: //server/B.html”. The converted URL path portion does not include the domain name of the Web server 4, and a request including such a URL as a request URL is transmitted from the Web browser 2 to the relay device 3.

  On the other hand, when a request is transmitted from the Web browser 2 to the Web server 4 without going through the relay device 3, such a problem does not occur. This is because the domain name of the Web server 4 is included in the domain part instead of the path part in the link source URL.

  For example, the link source URL is “http: //domain1/A.html”, and the link destination URL is a relative path “../B.html”. In this case, the HTML file “B.html” is one level higher than the HTML file “A.html”. However, the HTML file “A.html” is at the highest level of the path part, and the path part has no higher level than the HTML file “A.html”. For this reason, the Web browser 2 considers the HTML file “B.html” to be at the highest level of the path part, and sets the relative path “../B.html” of the link destination to the correct absolute value as shown in FIG. Convert to the path "http: //domain1/B.html".

  In this way, when a relative path indicating a non-existing upper layer is described as a link destination URL, a phenomenon occurs in which a request from the Web browser 2 cannot be received by the Web server 4 due to the relay device 3 being interposed.

  Thus, in the relay device 3 according to the first embodiment, even if a relative path indicating a non-existing upper layer is described as a link destination URL, a request based on this relative path is sent to the Web by performing URL complement processing. Transmission to the server 4 via the relay device 3 is enabled. Hereinafter, the configuration of the relay device 3 and the processing flow will be specifically described.

[Configuration of relay device]
Next, the configuration of the relay device 3 according to the first embodiment will be described with reference to FIG. FIG. 6 is a block diagram illustrating the configuration of the relay device 3 according to the first embodiment. FIG. 7 is a diagram for explaining processing of the insertion unit 14 of the relay device according to the first embodiment. FIG. 8 is a schematic diagram illustrating a response transmitted from the response unit 15 of the relay device according to the first embodiment.

  As illustrated in FIG. 6, the relay device 3 includes a determination unit 11, a conversion unit 12, an extraction unit 13, an insertion unit 14, and a response unit 15. The processing of each of these units will be described below.

  When the determination unit 11 receives a request from the Web browser 2, the determination unit 11 determines whether or not the request URL included in the received request conforms to a format based on a preset URL conversion rule (hereinafter referred to as "URL conversion format"). judge. Specifically, the determination unit 11 determines that the URL conversion format is satisfied when the protocol name and the domain name of the Web server 4 are included in the highest layer of the path portion of the request URL.

  For example, when the request URL is “http: // server / http: domain1 / A.html”, the protocol name “http” and the domain name “domain1” of the Web server 4 are included in the top layer of the path part. ing. Therefore, the determination unit 11 determines that the URL “http: // server / http: domain1 / A.html” conforms to the URL conversion format.

  If the determination unit 11 determines that the request URL conforms to the URL conversion format, the determination unit 11 passes the request received from the Web browser 2 to the conversion unit 12. On the other hand, when determining that the request URL does not conform to the URL conversion format, the determination unit 11 extracts the request URL and the Referer header from the request received from the Web browser 2. Then, the determination unit 11 passes the extracted request URL and Referer header to the extraction unit 13.

  The Referer header is information included in the header message of the request, and describes the link source URL. The link source URL is an example of a resource identifier of the link source. That is, the link source URL is a URL that becomes a link source of the request URL. For example, in the HTML file “A.html” whose URL is “http: // server / http: domain1 / A.html”, the link destination URL is “http: // server / http: domain1 / B.html”. Is described. In this case, the request URL is “http: // server / http: domain1 / B.html”, and the link source URL is “http: // server / http: domain1 / A.html”.

  The conversion unit 12 rewrites the request URL in the information included in the request received from the determination unit 11 to the URL of the Web server 4. Specifically, the conversion unit 12 rewrites the scheme part and the domain part of the request URL based on the description of the highest hierarchy of the path part of the request URL. Further, the conversion unit 12 rewrites the path part of the request URL based on the hierarchy lower than the highest part of the path part of the request URL.

  For example, it is assumed that the request URL is “http: // server / http: domain1 / A.html”. In this case, the conversion unit 12 sets the converted scheme part to “http” and sets the converted domain part to “domain1” based on “http: domain1” described in the highest hierarchy of the path part. . Further, the conversion unit 12 sets the converted path part to “A.html” based on “A.html” described in the hierarchy lower than the top of the path part of the request URL. Therefore, the request URL is rewritten from “http: // server / http: domain1 / A.html” to “http: //domain1/A.html”.

  The conversion unit 12 transmits a request including the request URL “http: //domain1/A.html” rewritten in this way to the Web server 4 via the network 5. Note that the conversion unit 12 rewrites the request URL included in the request line among the information included in the request received from the Web browser 2, and does not rewrite the message header, the message body, or the like.

  The extraction unit 13 extracts the domain name of the Web server 4 from the link source URL included in the Referer header received from the determination unit 11. Specifically, the extraction unit 13 extracts the description after “:” in the highest hierarchy among the descriptions of the path part of the link source URL as the domain name of the Web server 4. For example, when the link source URL is “http: // server / http: domain1 / A.html”, the extraction unit 13 sets “domain1” in the description “http: domain1” of the highest hierarchy to the Web server 4. Extract as a domain name. Further, the extraction unit 13 extracts the protocol name “http” from the description before “:” in the highest hierarchy in the description of the path part of the link source URL. The extraction unit 13 passes the extracted domain name and protocol name of the Web server 4 to the insertion unit 14. Further, the extraction unit 13 passes the request URL received from the determination unit 11 to the insertion unit 14.

  The insertion unit 14 inserts the domain name and protocol name of the Web server 4 extracted by the extraction unit 13 behind the domain part of the request URL. Specifically, the insertion unit 14 inserts “/”, shifts the description of the path part of the request URL to the lower layer, and inserts the domain name and protocol name of the Web server 4 in the highest hierarchy of the path part. . The URL in which the domain name and protocol name of the Web server 4 are inserted in this way is passed from the insertion unit 14 to the response unit 15.

  For example, it is assumed that the request URL is “http: //server/B.html” and the domain name of the Web server 4 extracted by the extraction unit 13 is “domain1”. Further, it is assumed that the protocol name extracted by the extraction unit 13 is “http”. In this case, as illustrated in FIG. 7, the insertion unit 14 shifts “B.html” described in the path portion of the request URL to “/B.html” one level lower. Further, the insertion unit 14 inserts the protocol name “http” and the domain name “domain1” of the Web server 4 in the highest layer. As a result, the request URL is converted from “http: //server/B.html” to “http: // server / http: domain1 / B.html”. The protocol name “http” and the domain name “domain1” of the Web server 4 are separated by a colon “:”.

  The response unit 15 generates a response including the URL received from the insertion unit 14 and transmits this response to the Web browser 2. This response is a response for requesting the Web browser 2 to perform a redirect process for the URL for which the insertion process has been performed by the insertion unit 14. For example, it is assumed that the URL subjected to the insertion processing by the insertion unit 14 is “http: // server / http: domain1 / B.html”. In this case, the response unit 15 generates a response including “301 Moved Permanently” and “Location: http: // server / http: domain1 / B.html” as shown in FIG. Send. “301 Moved Permanently” is included in the response as the status line status code. “Location: http: // server / http: domain1 / B.html” is included in the response as a header message. When the Web browser 2 receives the response from the response unit 15, the Web browser 2 performs a redirect process of transmitting a request having “http: // server / http: domain1 / B.html” as the request URL to the relay device 3.

[Processing by relay device]
Next, processing performed by the relay device 3 according to the first embodiment will be described with reference to FIGS. FIG. 9 to FIG. 11 are sequence diagrams illustrating the processing flow of the relay device 3 according to the first embodiment.

  First, with reference to FIG. 9, the flow of processing in which the Web browser 2 acquires the HTML file “A.html” via the relay device 3 will be described. When the URL “http: // server / http: domain1 / A.html” is designated as the request target, the Web browser 2 includes “http: // server / http: domain1 / A.html” as the request URL. Send a request. Since the domain name of the relay device 3 is described in the domain portion of the request URL, the Web browser 2 transmits this request to the relay device 3 (step S1).

  When receiving the request from the Web browser 2, the determination unit 11 of the relay device 3 determines whether the request URL included in the received request is compatible with the URL conversion format (step S2). The top layer of the path portion of the request URL “http: // server / http: domain1 / A.html” includes the protocol name “http” and the domain name “domain1” of the Web server 4. Therefore, the determination unit 11 determines that the request URL is compatible with the URL conversion format. When the request URL matches the URL conversion format, the determination unit 11 passes the request received from the Web browser 2 to the conversion unit 12.

  The conversion unit 12 converts the URL. That is, the conversion unit 12 rewrites the request URL in the information included in the request received from the determination unit 11 to the URL of the Web server 4 (step S3). Since “http: domain1” is described in the highest hierarchy of the path portion of the request URL, the conversion unit 12 sets “domain1” after “:” in “http: domain1” of the Web server 4. Identifies as a domain name. Further, the conversion unit 12 identifies “http” before “:” in “http: domain1” as the protocol name. Further, since the hierarchy below the highest hierarchy in the path portion of the request URL is described as “A.html”, the conversion unit 12 identifies “A.html” as the resource path name in the Web server 4.

  Based on the specified protocol name, domain name, and path name, the conversion unit 12 changes the request URL from “http: // server / http: domain1 / A.html” to “http: //domain1/A.html”. To "". Note that, when the upper proxy is not set, the conversion unit 12 sets the request URL as “A.html” which is a description of the relative path.

  The conversion unit 12 transmits a request with the request URL rewritten as described above. Since the domain name of the Web server 4 is described in the domain part of the request URL “http: //domain1/A.html”, the conversion part 12 transmits this request to the relay device 3 (step S4). .

  When receiving the request from the relay device 3, the Web server 4 reads the resource specified by the request URL included in the received request. Thereafter, the Web server 4 transmits a response including the read resource. Here, since the request URL is “http: //domain1/A.html”, the Web server 4 reads the HTML file “A.html” stored in the directory of the highest hierarchy. Thereafter, the Web server 4 transmits a response including the description of the HTML file “A.html” in the message body to the relay apparatus 3 that is the transmission source of the request (step S5).

  When the relay device 3 receives a response to the request transmitted in step S4 from the Web server 4, the relay device 3 transfers the received response to the Web browser 2. As a result, the Web browser 2 acquires a response including the description of the HTML file “A.html” in the message body from the Web server 4 via the relay device 3.

  Next, a flow of processing for accessing the link destination URL described in the HTML file “A.html” from the Web browser 2 will be described with reference to FIG. As shown in FIG. 10, it is assumed that this link destination URL is the value of the href attribute value of the anchor tag, and is described by a relative path “../B.html” indicating a non-existing upper layer.

  Based on the link destination URL “http: // server / http: domain1 / A.html”, the Web browser 2 describes the link destination URL described in the relative path “../B.html” with an absolute path. Is converted to a URL. The URL after conversion by the Web browser 2 is “http: //server/B.html”. The absolute path of the correct URL of the HTML file “B.html” is “http: // server / http: domain1 / B.html”. Therefore, the Web browser 2 converts the link destination URL into an incorrect URL.

  The Web browser 2 generates a request including the URL converted in this way as a request URL. The request generated by the Web browser 2 includes a link source URL “http: // server / http: domain1 / A.html” as a Referer header.

  Next, the Web browser 2 transmits the generated request. Since the domain name of the relay device 3 is described in the domain portion of the request URL, the Web browser 2 transmits this request to the relay device 3 (step S6).

  When receiving the request from the Web browser 2, the determination unit 11 of the relay device 3 determines whether the request URL included in the received request is compatible with the URL conversion format (step S7). The path part of the request URL “http: //server/B.html” does not include the protocol name or the domain name of the Web server 4. Therefore, the determination unit 11 determines that the request URL does not conform to the URL conversion format. When the request URL does not conform to the URL conversion format, the determination unit 11 passes the request URL and Referer header included in the request received from the Web browser 2 to the extraction unit 13.

  The extraction unit 13 extracts the domain name of the Web server 4 from the Referer header received from the determination unit 11 (step S8). Specifically, the extraction unit 13 extracts the description “domain1” after “:” in the path of the link source URL included in the Referer header as the domain name of the Web server 4. To do. In addition, the extraction unit 13 extracts the description “http” preceding “:” from the description of the highest hierarchy as the protocol name. The extraction unit 13 passes the extracted domain name and protocol name of the Web server 4 to the insertion unit 14. Further, the extraction unit 13 passes the request URL received from the determination unit 11 to the insertion unit 14.

  The insertion unit 14 inserts the protocol name “http” extracted by the extraction unit 13 and the domain name “domain1” of the Web server 4 behind the domain part of the request URL (step S9). Specifically, the insertion unit 14 shifts the description “B.html” in the path part of the request URL to “/B.html” one level lower than the highest level, and sets the protocol name “http” in the highest level. The domain name “domain1” of the Web server 4 is inserted. As a result, the request URL is converted from “http: //server/B.html” to “http: // server / http: domain1 / B.html”. The protocol name “http” and the domain name “domain1” of the Web server 4 are separated by a colon “:”.

  The response unit 15 generates a response for requesting the Web browser 2 to perform a redirect process for the request URL subjected to the insertion process by the insertion unit 14, and transmits the generated response to the Web browser 2 (step S10). As shown in FIG. 8, this response includes “301 Moved Permanently” as the status code of the status line, and includes “Location: http: // server / http: domain1 / B.html” in the header message.

  Next, with reference to FIG. 11, the flow of processing for the response transmitted from the relay device 3 to the Web browser 2 in step S10 will be described.

  When receiving a response from the relay device 3, the Web browser 2 performs a redirect process for transmitting a request including the request URL complemented by the relay device 3 to the relay device 3. Specifically, the Web browser 2 specifies the request URL to be redirected as “http: // server / http: domain1 / B.html” based on the Location header. The Location header is a header included in the header message of the response from the relay device 3. The web browser 2 transmits a request including the request URL specified in this way (step S11). Since the domain name of the relay device 3 is described in the domain portion of the request URL, the Web browser 2 transmits the request to the relay device 3.

  When receiving the request from the Web browser 2, the determination unit 11 of the relay device 3 determines whether the request URL included in the received request is compatible with the URL conversion format (step S12). The domain part of the request URL “http: //server/domain1/B.html” includes the domain name “server” of the relay device 3, and the protocol name “http” and the Web are included in the highest hierarchy of the path part of the request URL. The domain name “domain1” of the server 4 is included. Therefore, the determination unit 11 determines that the request URL conforms to a predetermined format. When the request URL conforms to a predetermined format, the determination unit 11 passes the request from the Web browser 2 to the conversion unit 12.

  The conversion unit 12 converts the URL in the same manner as the processing in step S3. That is, the conversion unit 12 rewrites the request URL included in the request received from the determination unit 11 with the URL of the Web server 4 (step S13). “Http: domain1” is described in the uppermost layer of the path portion of the request URL, and “A.html” is described in a layer lower than the uppermost layer of the path portion. Therefore, the conversion unit 12 rewrites the request URL from “http: // server / http: domain1 / B.html” to “http: //domain1/B.html”.

  The conversion unit 12 transmits a request with the request URL rewritten. Since the domain name of the Web server 4 is described in the domain part of this request URL, the conversion part 12 transmits this request to the relay device 3 (step S14).

  The Web server 4 receives a request from the relay device 3. Since the request URL included in the received request is “http: //domain1/B.html”, the Web server 4 reads the HTML file “B.html” stored in the directory of the highest hierarchy. Thereafter, the Web server 4 transmits a response including the description of the HTML file “B.html” in the message body to the relay apparatus 3 that is the transmission source of the request (step S15).

  When the relay device 3 receives a response to the request transmitted in step S11 from the Web server 4, the relay device 3 transfers the received response to the Web browser 2. As a result, the Web browser obtains a response including the description of the HTML file “B.html” in the message body from the Web server 4 via the relay device 3.

[Effect of Example 1]
As described above, the relay device 3 determines whether or not the request URL included in the request received from the Web browser 2 conforms to a predetermined format. When the request URL does not conform to the predetermined format, the relay device 3 extracts the domain name of the Web server 4 from the link source URL included in the request. The relay device 3 inserts the extracted domain name of the Web server 4 behind the domain part of the request URL. Thereby, the request URL can be complemented with a correct URL.

  In addition, the relay device 3 transmits a response requesting the redirect process to the Web browser 2. This response is a response for requesting the Web browser 2 to perform a redirect process for the request URL supplemented by the insertion process. The web browser 2 can acquire resources from the web server 4 by performing a redirect process based on the received response. As described above, the relay device 3 can cause the Web browser 2 to transmit a request with a correct absolute path even when a request based on a relative path indicating an upper layer that does not exist is transmitted from the Web browser 2. .

  In the first embodiment described above, when the request URL does not conform to the URL conversion format, the domain name of the Web server 4 is extracted from the Referer header to complement the request URL. However, the Referer header may not be included in the request transmitted from the Web browser 2.

  Therefore, in the relay apparatus according to the second embodiment, the request URL can be complemented by referring to the communication log that is the history of the request received from the Web browser 2 even when the Referer header cannot be obtained. Hereinafter, the configuration of the relay apparatus according to the second embodiment and the flow of processing will be specifically described.

[Configuration of relay device]
Next, the configuration of the relay device 3A according to the second embodiment will be described with reference to FIGS. FIG. 12 is a block diagram illustrating the configuration of the relay device 3A according to the second embodiment. FIG. 11 is a diagram illustrating an example of a communication log stored in the storage unit 16A of the relay device 3A according to the second embodiment. FIG. 12 is a schematic diagram illustrating processing performed by the determination unit 11A of the relay device 3A according to the second embodiment.

  As illustrated in FIG. 12, the relay device 3A according to the second embodiment includes a determination unit 11A, a conversion unit 12A, an extraction unit 13A, an insertion unit 14A, a response unit 15A, and a storage unit 16A. The processing of each of these units will be described below.

  The determination unit 11A stores the request history received from the Web browser 2 in the storage unit 16A as a communication log. FIG. 13 shows an example of a communication log stored in the storage unit 16A. As illustrated in FIG. 13, in the storage unit 16 </ b> A, information in which the request URL and the content of the request are associated with each other is stored as a communication log for each request received from the Web browser 2. The request content includes information on the request line and the header message.

  FIG. 14 is a diagram illustrating a processing procedure performed by the determination unit 11A. As illustrated in FIG. 14, the determination unit 11A determines whether a request has been received from the Web browser 2 (step S20). If it is determined that a request has not been received from the Web browser 2 (No at Step S20), the determination unit 11A returns the process to Step S20. On the other hand, if it is determined that a request has been received from the Web browser 2 (Yes at Step S20), the determination unit 11A stores information on the received request in the storage unit 16A as a communication log (Step S21).

  Next, the determination unit 11A determines whether or not the request URL included in the request received from the Web browser 2 conforms to the URL conversion format (step S22). This process is the same process as the determination unit 11 of the first embodiment.

  If it is determined that the request URL is compatible with the URL conversion format (Yes at Step S22), the determination unit 11A passes the request to the conversion unit 12A (Step S23). On the other hand, if it is determined that the request URL does not conform to the URL conversion format (No at Step S22), the determination unit 11A determines whether the Referer header is included in the request received from the Web browser (Step S24). .

  If it is determined that the Referer header is included in the request (Yes at Step S24), the determination unit 11A passes the request URL and the link source URL to the extraction unit 13A (Step S25). The request URL passed to the extraction unit 13A is a request URL included in the request received in step S20. The link source URL passed to the extraction unit 13A is information included in the Referer header. On the other hand, when determining that the Referer header is not included in the request (No at Step S24), the determination unit 11A reads the communication log URL from the storage unit 16A (Step S26). The communication log URL is the request URL with the newest date stored in the storage unit 16A among the request URLs according to the URL conversion format. For example, when a communication log as shown in FIG. 13 is stored in the storage unit 16A, the request URL read by the determination unit 11A as the communication log URL is “http: // server / http: domain1 / E.html”. It is.

  When the process of step S26 ends, the determination unit 11A passes the request URL and the communication log URL read from the storage unit 16A to the extraction unit 13A (step S27). The request URL passed to the extraction unit 13A is a request URL included in the request received in step S20. When the processes of steps S23, S25, and S27 are completed, the determination unit 11A returns the process to step S20.

  The conversion unit 12A performs the same processing as the conversion unit 12 of the first embodiment. That is, the conversion unit 12A rewrites the request URL in the information included in the request received from the determination unit 11A to the URL of the Web server 4. The conversion unit 12 transmits a request including the request URL rewritten in this way to the Web server 4 via the network 5.

  When receiving the request URL and the Referer header from the determination unit 11A, the extraction unit 13A extracts the protocol name and the domain name of the Web server 4 from the Referer header, similarly to the processing of the extraction unit 13 of the first embodiment. Further, the extraction unit 13 passes the request URL, the extracted protocol name, and the domain name of the Web server 4 to the insertion unit 14 as in the processing of the extraction unit 13 of the first embodiment.

  On the other hand, when the request URL and the communication log URL are received from the determination unit 11, the extraction unit 13A extracts the domain name of the Web server 4 from the communication log URL. Specifically, the extraction unit 13A extracts a description after “:” in the description of the highest hierarchy in the path part of the communication log URL as the domain name of the Web server 4. For example, when the communication log URL is “http: // server / http: domain1 / A.html”, the extraction unit 13A sets “domain1” in the description “http: domain1” of the highest hierarchy to the Web server 4. Extract as a domain name. Further, the extraction unit 13A extracts the description preceding “:” from the description of the highest hierarchy as the protocol name. For example, when the communication log URL is “http: // server / http: domain1 / A.html”, the extraction unit 13A extracts “http” as a protocol name. The extraction unit 13A passes the extracted domain name and protocol name of the Web server 4 to the insertion unit 14. Further, the extraction unit 13A passes the request URL received from the determination unit 11A to the insertion unit 14A.

  The insertion unit 14A inserts the domain name and protocol name of the Web server 4 extracted by the extraction unit 13A after the domain part of the request URL, as in the processing of the insertion unit 14 of the first embodiment.

  Similar to the response unit 15 of the first embodiment, the response unit 15A transmits to the Web browser 2 a response requesting the Web browser 2 to perform a redirect process for the request URL that has been inserted by the insertion unit 14A.

[Processing by relay device]
Next, processing performed by the relay device 3A according to the second embodiment will be described with reference to FIGS. 15 and 16 are sequence diagrams illustrating the flow of processing of the relay device 3A according to the second embodiment.

  First, the flow of processing in which the Web browser 2 acquires the HTML file “A.html” via the relay device 3A will be described with reference to FIG. In addition, the process of step S30, S31, S33-S35 shown in FIG. 15 is a process similar to step S1-S5 of Example 1 shown in FIG.

  As shown in FIG. 15, when the URL “http: // server / http: domain1 / D.html” is designated as a request target, the Web browser 2 transmits the request to the relay device 3A (step S30). This request includes “http: // server / http: domain1 / D.html” as a request URL.

  When receiving the request from the Web browser 2, the determination unit 11A of the relay device 3A determines whether the request URL included in the received request is compatible with the URL conversion format (step S31). When the request URL conforms to the URL conversion format, the determination unit 11A passes the request from the Web browser 2 to the conversion unit 12A.

  Further, upon receiving a request from the Web browser 2, the determination unit 11A stores information on the received request in the storage unit 16A as a communication log (step S32). As shown in FIG. 13, the communication log is information in which the received date and time of the received request, the request URL included in the received request, and the content of the request are associated with each other.

  The conversion unit 12A converts the URL. That is, the conversion unit 12A rewrites the request URL in the information included in the request received from the determination unit 11A to the URL of the Web server 4 (step S33). The conversion unit 12A transmits the request with the request URL rewritten to the relay device 3A (step S34).

  When receiving the request from the relay device 3A, the Web server 4 reads the HTML file “D.html” specified by the request URL included in the received request. Thereafter, the Web server 4 transmits a response including the description of the read HTML file “D.html” to the relay device 3A (step S35).

  When the relay device 3A receives a response to the request transmitted in step S35 from the Web server 4, the relay device 3A transfers the received response to the Web browser 2. Thereby, the Web browser acquires a response including the description of the HTML file “D.html” in the message body from the Web server 4 via the relay device 3A.

  Next, a flow of processing for accessing the link destination URL described in the HTML file “D.html” from the Web browser 2 will be described with reference to FIG. Note that the processes in S39 and S40 shown in FIG. 16 are the same as steps S9 and S10 in the first embodiment shown in FIG.

  As shown in FIG. 16, it is assumed that a refresh meta tag is described in the HTML file “D.html”. In this case, the Web browser 2 transmits a request using the link destination URL defined in the refresh meta tag as a request URL (step S36). In the refresh meta tag shown in FIG. 16, the URL “../E.html” described in the relative path is defined as the link destination URL, and the waiting time is defined as 0 seconds. Therefore, the Web browser 2 transmits a request including “http: //server/E.html” as the request URL to the relay device 3. Note that the waiting time is a waiting time from when the HTML file “D.html” is acquired until a process of transmitting a request including the link destination URL in the request URL.

  When receiving the request from the Web browser 2, the determination unit 11A of the relay device 3A determines whether the request URL included in the received request conforms to the URL conversion format (step S37). The path name of the request URL “http: //server/E.html” does not include the domain name “domain1” of the Web server 4. Therefore, the determination unit 11A determines that the request URL does not conform to the URL conversion format.

  When the request URL does not conform to the URL conversion format, the determination unit 11A reads the communication log URL from the storage unit 16A. The determination unit 11A passes the read communication log URL and the request URL of the received request to the extraction unit 13A. The communication log URL is the request URL with the newest date stored in the storage unit 16A among the request URLs according to the URL conversion format. Here, it is assumed that a communication log as shown in FIG. 13 is stored in the storage unit 16A. Therefore, the request URL read from the storage unit 16A as the communication log URL by the determination unit 11A is “http: // server / http: domain1 / D.html”.

  The extraction unit 13A extracts the domain name of the Web server 4 from the communication log URL received from the determination unit 11A (step S38). Specifically, the extraction unit 13A extracts the description “domain1” after “:” in the description of the highest hierarchy in the path part of the communication log URL as the domain name of the Web server 4. Further, the extraction unit 13A extracts the description “http” that precedes “:” from the description of the highest hierarchy as the protocol name. The extraction unit 13A passes the extracted protocol name and the domain name of the Web server 4 to the insertion unit 14A. Further, the extraction unit 13A passes the request URL received from the determination unit 11A to the insertion unit 14A.

  Similarly to the insertion unit 14A of the first embodiment, the insertion unit 14A inserts the protocol name “http” extracted by the extraction unit 13A and the domain name “domain1” of the Web server 4 behind the domain part of the request URL. (Step S39). As a result, the request URL is converted from “http: //server/E.html” to “http: // server / http: domain1 / E.html”.

  The response unit 15A transmits a response requesting the web browser 2 to perform a redirect process for the request URL supplemented by the insertion process (step S40). This response includes “301 Moved Permanently” as the status code of the status line, and further includes “Location: http: // server / http: domain1 / E.html” in the header message.

  Upon receiving the response from the relay device 3, the Web browser 2 transmits a request including the request URL “http: // server / http: domain1 / E.html” supplemented by the relay device 3 to the relay device 3. As a result, the Web browser 2 can acquire the HTML file “E.html” from the Web server 4.

  As described above, the relay device 3A includes the storage unit 16A that stores the request information received from the Web browser 2 as a communication log. Then, when the Referer header is not included in the request, the relay device 3A extracts the domain name of the Web server 4 from the request URL stored in the storage unit 16A. Therefore, in the relay device 3A, even when the request does not include the Referer header, the Web browser 2 can retransmit the request with the correct absolute path.

  In the first and second embodiments described above, the relay device supplements an incorrect request URL to convert it to a correct request URL, and causes the Web browser to perform a redirect process to the correct request URL.

  On the other hand, in the relay apparatus according to the third embodiment, instead of performing the redirect process on the Web browser, the relay apparatus converts the request and transmits the request directly to the Web server. By doing so, it is possible to save time required for the redirection process, and it is possible to quickly acquire resources from the Web server. Hereinafter, the configuration of the relay apparatus according to the third embodiment and the flow of processing will be specifically described.

[Configuration of relay device]
Next, the configuration of the relay device 3B according to the third embodiment will be described with reference to FIG. FIG. 17 is a block diagram illustrating the configuration of the relay device 3B according to the third embodiment.

  As illustrated in FIG. 17, the relay device 3B according to the third embodiment includes a determination unit 11B, a conversion unit 12B, an extraction unit 13B, an insertion unit 14B, and a storage unit 16B. The processing of each of these units will be described below.

  In addition to the process of the determination unit 11A of the second embodiment, the determination unit 11B further performs a process of passing the request received from the Web browser 2 to the insertion unit 14B. The extraction unit 13B performs the same processing as the extraction unit 13B of the second embodiment.

  The conversion unit 12B converts the request received from the insertion unit 14B in addition to the processing of the conversion unit 12B of the second embodiment. That is, the conversion unit 12B converts the request received from the insertion unit 14B in addition to the conversion of the request received from the determination unit 11B. The request is converted by replacing the request URL with the URL of the Web server 4. The conversion for the request received from the insertion unit 14B is performed by the same process as the conversion for the request received from the determination unit 11B. The conversion unit 12B transmits the request thus converted to the Web server 4.

  The insertion unit 14B generates a request including the converted request URL in addition to the processing of the insertion unit 14A of the second embodiment. Specifically, the insertion unit 14B replaces the request URL in the information included in the request received from the determination unit 11B with the converted request URL. The insertion unit 14B passes the request with the request URL replaced in this way to the conversion unit 12B.

[Processing by relay device]
Next, processing performed by the relay device 3B according to the third embodiment will be described with reference to FIG. FIG. 18 is a sequence diagram illustrating the processing flow of the relay device 3B according to the third embodiment. Note that the processing of S60 to S63 shown in FIG. 18 is the same as the processing of steps S36 to S39 of the second embodiment shown in FIG.

  FIG. 18 describes the flow of processing for accessing from the Web browser 2 the link destination URL described in the HTML file “D.html”. As shown in FIG. 18, it is assumed that a refresh meta tag is described in the HTML file “D.html”. The Web browser 2 converts the link destination URL defined in the meta tag from a description using a relative path to a description using an absolute path. Thereafter, the Web browser 2 transmits a request including the request URL “http: //server/E.html” converted in this way (step S60).

  When receiving the request from the Web browser 2, the determination unit 11B of the relay device 3B determines whether the request URL included in the received request is compatible with the URL conversion format (step S61). The path name of the request URL “http: //server/E.html” does not include the domain name “domain1” of the Web server 4. Therefore, the determination unit 11B determines that the request URL does not conform to the URL conversion format. Next, the determination unit 11B reads “http: // server / http: domain1 / D.html” as the communication log URL from the storage unit 16B. The determination unit 11B passes the read communication log URL and request URL to the extraction unit 13B.

  The extraction unit 13B extracts the protocol name and the domain name of the Web server 4 from the communication log URL received from the determination unit 11B (step S62). The domain name extracted here is “domain1”, and the protocol name is “http”. The extraction unit 13B passes the request URL, domain name, and protocol name to the insertion unit 14B.

  The insertion unit 14B inserts the protocol name “http” extracted by the extraction unit 13B and the domain name “domain1” of the Web server 4 behind the domain part of the request URL (step S63). As a result, the request URL is converted from “http: //server/E.html” to “http: // server / http: domain1 / E.html”.

  Further, the insertion unit 14B replaces the request URL in the information included in the request received from the determination unit 11B with the converted request URL “http: // server / http: domain1 / E.html”. Thereafter, the insertion unit 14B passes the request with the request URL replaced to the conversion unit 12B.

  The conversion unit 12B converts the URL. That is, the conversion unit 12B rewrites the request URL in the information included in the request received from the determination unit 11B to the URL of the Web server 4 (step S64). Since “http: domain1” is described in the highest hierarchy of the path portion of the request URL, the conversion unit 12 sets “domain1” after “:” in “http: domain1” of the Web server 4. Identifies as a domain name. Further, the conversion unit 12 identifies “http” before “:” in “http: domain1” as the protocol name. Further, since the hierarchy below the highest hierarchy in the path portion of the request URL is described as “A.html”, the conversion unit 12 identifies “E.html” as the path name of the resource in the Web server 4.

  Based on the specified protocol name, domain name, and path name, the conversion unit 12B changes the request URL from “http: // server / http: domain1 / E.html” to “http: //domain1/E.html”. To "". Note that, when the upper proxy is not set, the conversion unit 12B sets the request URL to “E.html” which is a description of the relative path.

  The conversion unit 12B transmits a request with the request URL rewritten. Since the domain name of the Web server 4 is described in the domain part of the request URL, the conversion unit 12B transmits this request to the Web server 4 (step S65).

  When receiving the request from the relay device 3, the Web server 4 transmits a response including the description of the HTML file “E.html” in the message body to the relay device 3 that is the transmission source of the request (step S 66). The relay device 3 transfers this response to the Web browser 2. Thereby, the Web browser 2 acquires the HTML file “E.html”.

  As described above, in the relay device 3B according to the third embodiment, the request URL included in the request based on the relative path indicating the non-existing upper layer is complemented and directly transmitted to the Web server. Therefore, the time required for the redirect process can be saved, and resources can be quickly acquired from the Web server.

  Although the first to third embodiments have been described so far, the present invention may be implemented in various different forms other than the above-described embodiments. Therefore, another embodiment will be described below as a fourth embodiment.

(1) System Configuration, etc. Further, each component of each illustrated apparatus is functionally conceptual and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured. For example, as illustrated in FIG. 19, the relay device 3 </ b> C may be an external proxy without arranging a relay device as a local proxy in the terminal device 1 ′. Further, all or any part of each processing function performed in each device may be realized by a CPU and a program analyzed and executed by the CPU, or may be realized as hardware by wired logic.

(2) Program When the processing of the relay devices 3, 3 </ b> A to 3 </ b> C in FIGS. 6, 12, 17, and 19 is executed by a program, an information processing device (computer) as shown in FIG. 20 is used. 20 includes a central processing unit (CPU) 51, a memory 52, an input device 53, an output device 54, an external storage device 55, a portable storage medium drive device 56, and a network connection device 57. Are connected to each other.

  The memory 52 includes, for example, a read only memory (ROM), a random access memory (RAM), and the like, and stores programs and data used for processing. The CPU 51 performs the same processing as the relay device by executing the program using the memory 52.

  The input device 53 is, for example, a keyboard, a pointing device, and the like, and is used for inputting instructions and information from an operator. The output device 54 is, for example, a display, a printer, a speaker, or the like, and is used to output an inquiry to an operator or a processing result.

  The external storage device 55 is, for example, a magnetic disk device, an optical disk device, a magneto-optical disk device, a tape device, or the like. The information processing apparatus stores programs and data in the external storage device 55, and loads them into the memory 52 for use as necessary.

  The portable storage medium driving device 56 accesses the recorded contents of the portable recording medium 58. The portable recording medium 58 is an arbitrary computer-readable recording medium such as a memory card, a flexible disk, an optical disk, or a magneto-optical disk. The operator stores programs and data in the portable recording medium 58 and loads them into the memory 52 for use as necessary.

  The network connection device 57 is connected to a communication network such as the Internet, and performs data conversion accompanying communication with the Web browser 2 and the Web server 4. When the information processing apparatus includes the function of the Web browser 2 and the function of the relay apparatus 3, communication between the Web browser 2 and the relay apparatus 3 is performed via the network connection apparatus 57. Further, the information processing apparatus receives programs and data from an external device via the network connection device 57 as necessary, and loads them into the memory 52 for use.

(3) Others In Embodiments 1 to 3, when an HTML file is received from a Web server, the link destination URL included in the HTML file is converted by a Web browser. Thereby, the request from the Web browser is transmitted to the Web server via the relay device. However, instead of converting the link destination URL with the Web browser, the link destination URL may be converted with the relay device. That is, when the relay device receives an HTML file transmitted from the Web server, the link destination URL included in the received HTML file is converted by the relay device. Thereafter, the converted HTML file is transmitted to the Web browser.

  In the first to third embodiments, as an example of the URL conversion format, an example is shown in which the highest layer of the path portion of the request URL is “protocol name: domain name of the Web server”. However, the URL conversion format is not limited to this. For example, the highest level of the path portion of the request URL may be “Web server domain name: protocol name” or “protocol name−Web server domain name” ”as the URL conversion format.

  The following supplementary notes are further disclosed with respect to the embodiments including the above examples.

(Supplementary Note 1) A determination unit that determines whether or not a resource identifier included in a request received from a browser conforms to a predetermined format;
An extraction unit that extracts a domain name of a server included in a resource identifier that is a link source of the resource identifier from the request when the determination unit determines that the resource identifier does not conform to a predetermined format;
An insertion unit that performs an insertion process for inserting the domain name of the server extracted by the extraction unit after the domain part of the resource identifier included in the request;
A relay device comprising:

(Additional remark 2) The storage part which memorize | stores the resource identifier contained in the said request is further provided,
When the resource identifier which is the link source is not included in the request, the extraction unit is stored in the storage unit, and among the resource identifiers conforming to the predetermined format, the storage unit stores the latest The relay apparatus according to appendix 1, wherein a domain name of the server is extracted from a resource identifier.

(Supplementary note 3) The relay device according to Supplementary note 1 or 2, further comprising: a response unit that transmits a response requesting a redirect process for the resource identifier subjected to the insertion process to the browser.

(Supplementary Note 4) The request is converted by replacing the domain part of the resource identifier subjected to the insertion processing with the domain name of the server included in the resource identifier subjected to the insertion processing from the domain name of the relay device. The relay device according to appendix 1 or 2, further comprising a conversion unit.

(Appendix 5) A relay method executed by a computer,
Determine whether the resource identifier included in the request received from the browser conforms to the predetermined format,
When it is determined that the resource identifier does not conform to a predetermined format, a server domain name included in the resource identifier that is a link source of the resource identifier is extracted from the request;
The relay method, wherein the extracted domain name of the server is inserted after the domain part of the resource identifier.

(Supplementary Note 6) A resource identifier included in the request is stored in a storage unit,
When the resource identifier that is the link source is not included in the request, the storage unit stores the resource identifier that is stored in the storage unit and conforms to the predetermined format from the latest resource identifier to the server. 6. The relay method according to appendix 5, wherein the domain name is extracted.

(Supplementary note 7) The relay method according to Supplementary note 5 or 6, wherein a response requesting a redirect process for the resource identifier subjected to the insertion process is transmitted to the browser.

(Supplementary note 8) The request is converted by replacing the domain part of the resource identifier subjected to the insertion processing with the domain name of the server included in the resource identifier subjected to the insertion processing from the domain name of the relay device. The relay method according to appendix 5 or 6, characterized in that:

(Appendix 9)
Determine whether the resource identifier included in the request received from the browser conforms to the predetermined format,
When the determination step determines that the resource identifier does not conform to a predetermined format, a server domain name included in the resource identifier that is a link source of the resource identifier is extracted from the request,
A relay program for executing a process of inserting the extracted domain name of the server after the domain part of the resource identifier.

(Supplementary Note 10) In a computer, a resource identifier included in the request is stored in a storage unit,
When the resource identifier that is the link source is not included in the request, the storage unit stores the resource identifier that is stored in the storage unit and conforms to the predetermined format from the latest resource identifier to the server. The relay program according to appendix 9, wherein a process for extracting the domain name is executed.

(Additional remark 11) The relay program of Additional remark 9 or 10 which makes a computer perform the process which transmits the response which requests | requires the redirect process with respect to the resource identifier in which the said insertion process was performed to the said browser.

(Supplementary Note 12) The computer replaces the domain part of the resource identifier subjected to the insertion processing with the domain name of the server included in the resource identifier subjected to the insertion processing from the domain name of the relay device. The relay program according to appendix 9 or 10, wherein the relay program is converted.

1, 1 'terminal device 2 Web browser 3, 3A, 3B, 3C Relay device 4 Web server 5 Network 11, 11A, 11B Determination unit 12, 12A, 12B Conversion unit 13, 13A, 13B Extraction unit 14, 14A, 14B Insertion Unit 15, 15A Response unit 16A Storage unit

Claims (6)

A determination unit that determines whether or not a resource identifier included in a request received from a browser conforms to a predetermined format;
An extraction unit that extracts a domain name of a server included in a resource identifier that is a link source of the resource identifier from the request when the determination unit determines that the resource identifier does not conform to a predetermined format;
An insertion unit that performs an insertion process for inserting the domain name of the server extracted by the extraction unit after the domain part of the resource identifier included in the request;
A relay device comprising: A storage unit for storing a resource identifier included in the request;
When the resource identifier which is the link source is not included in the request, the extraction unit is stored in the storage unit, and among the resource identifiers conforming to the predetermined format, the storage unit stores the latest The relay apparatus according to claim 1, wherein a domain name of the server is extracted from a resource identifier.   The relay apparatus according to claim 1, further comprising: a response unit that transmits a response requesting a redirect process for the resource identifier subjected to the insertion process to the browser.   A conversion unit for converting the request by replacing the domain part of the resource identifier subjected to the insertion process with the domain name of the server included in the resource identifier subjected to the insertion process from the domain name of the relay apparatus; The relay device according to claim 1, wherein the relay device is provided. A relay method executed by a computer,
Determine whether the resource identifier included in the request received from the browser conforms to the predetermined format,
When it is determined that the resource identifier does not conform to a predetermined format, a server domain name included in the resource identifier that is a link source of the resource identifier is extracted from the request;
The relay method, wherein the extracted domain name of the server is inserted after the domain part of the resource identifier. On the computer,
Determine whether the resource identifier included in the request received from the browser conforms to the predetermined format,
When it is determined that the resource identifier does not conform to a predetermined format, a server domain name included in the resource identifier that is a link source of the resource identifier is extracted from the request;
A relay program for executing a process of inserting the extracted domain name of the server after the domain part of the resource identifier.

Images