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

Abstract

PROBLEM TO BE SOLVED: To provide a relay device which performs reproduction at a high speed when reproducing an operation.SOLUTION: A relay device 1 comprises: a communication record table 111 which stores a communication history in which a request from a web browser to a web server is correlated with a response from the web server for an operation performed by the web browser; an authentication state extraction unit 131 which extracts the communication history correlated with a response in which information used in session management exists on the basis of the communication history stored in the communication record table 111; screen transition extraction unit 132 which extracts a series of communication histories obtained by tracking back information which is included in the request and is used to manage transition of a screen outputted on the web browser, on the basis of the communication history stored in the communication record table 111; and a communication reproduction unit 14 which reproduces the operation using a union of the communication history extracted by the authentication state extraction unit 131 and the communication history extracted by the screen transition extraction unit 132.

Description

  The present invention relates to a relay device and the like.

  In a computer system, a technique for reproducing the operation of the system based on an operation history such as a user operation is disclosed.

  There is also a technique for reproducing user operations in a web system. In the web system, a web server exchanges data with the web browser using HTTP (Hyper Text Transfer Protocol) under the operation of the web browser to provide a corresponding service. At this time, a relay server that relays data may be installed between the web server and the web browser.

  Such a relay server records a communication message between the web server and the web browser as a communication history, and reproduces the communication using the recorded communication history. As a result, when the user wants to reproduce the operation to the web server, the relay server automatically reproduces the communication using the communication history instead of performing the operation to the web server again by the web browser. You can reproduce the operation to the service.

JP-A-7-84838

  However, the conventional technique has a problem in that it takes time to reproduce the operation when reproducing the operation based on the communication history. That is, there is a case where it is desired to reproduce only that a search result for an input of a certain search condition is returned from the web server. In such a case, if the relay server simply reproduces communication using the communication history, it reproduces parts other than the part to be reproduced. For example, when the search condition is input from a frame included in the search screen, the relay server only needs to reproduce the frame in which the search condition is input. The search screen itself will also be reproduced. That is, since the relay server reproduces even unnecessary communication, it takes time to reproduce.

  An object of the disclosed technique is to enable high-speed reproduction when reproducing an operation.

  In one aspect, the relay device stores a communication history in which request data transmitted from the web browser to the web server and response data received from the web server are associated with each other for an operation performed by the web browser; A first extraction unit for extracting a communication history associated with the response data in which information used for session management exists based on the communication history stored in the storage unit; and the storage unit stored in the storage unit Based on the communication history, a second series of communication history information that is obtained by tracing information that is included in the request data and that is used to manage screen transitions output on the web browser side is extracted. An extraction unit, a communication history extracted by the first extraction unit, and a communication history extracted by the second extraction unit Using the union, and a reproducing unit for reproducing the operation.

  According to one aspect of the relay device disclosed in the present application, when the operation is reproduced, the reproduction can be performed at high speed.

FIG. 1 is a functional block diagram illustrating the configuration of the web relay system according to the first embodiment. FIG. 2 is a functional block diagram illustrating the configuration of the relay device according to the first embodiment. FIG. 3 is a diagram illustrating an example of a data structure of the communication record table. FIG. 4 is a flowchart illustrating the procedure of the authentication state extraction process according to the first embodiment. FIG. 5 is a flowchart illustrating the procedure of the screen transition extraction process according to the first embodiment. FIG. 6 is a flowchart illustrating the procedure of the reproduction extraction process according to the first embodiment. FIG. 7 is a diagram illustrating a specific example of the communication record. FIG. 8 is a diagram illustrating a specific example of the screen transition displayed on the web browser. FIG. 9 is a diagram illustrating a specific example of the authentication state extraction process. FIG. 10 is a diagram illustrating a specific example of the screen transition extraction process. FIG. 11 is a diagram illustrating a specific example of the reproduction extraction process. FIG. 12 is a diagram illustrating a specific example of the communication reproduction process. FIG. 13 is a functional block diagram illustrating the configuration of the relay device according to the second embodiment. FIG. 14A is a diagram showing HTML of the main screen of the login screen. FIG. 14B is a diagram showing HTML corresponding to each small screen. FIG. 14C is a diagram showing an example of a screen composed of small screens. FIG. 15 is a flowchart illustrating the procedure of the small screen extraction process according to the second embodiment. FIG. 16 is a diagram illustrating a specific example of communication recording. FIG. 17 is a diagram illustrating a specific example of the screen transition displayed on the web browser. FIG. 18 is a diagram illustrating a specific example of the communication record extracted by the screen transition extraction process. FIG. 19 is a diagram illustrating a specific example of the small screen extraction process. FIG. 20 is a diagram illustrating a specific example of the reproduction extraction process. FIG. 21 is a diagram illustrating a specific example of the communication reproduction process. FIG. 22 is a diagram illustrating a computer that executes a relay program.

  Hereinafter, embodiments of a relay device, a relay program, and a relay method disclosed in the present application will be described in detail with reference to the drawings. The present invention is not limited to the embodiments.

[Configuration of Web Relay System According to Embodiment 1]
FIG. 1 is a functional block diagram illustrating the configuration of the web relay system 9 according to the first embodiment. As shown in FIG. 1, the web relay system 9 includes a relay device 1, a web browser 2, and a web server 3. The relay device 1 relays communication between the web browser 2 and the web server 3. The web browser 2 is a user terminal such as a personal computer that uses a web service. The web server 3 implements a web service. In the web relay system 9, the web server 3 may be applied to the same network as the relay device 1 and the web browser 2, or the web server 3 may be applied to a different network as an external device. There may be.

[Configuration of Relay Device According to Embodiment 1]
FIG. 2 is a functional block diagram illustrating the configuration of the relay device according to the first embodiment. As illustrated in FIG. 2, the relay device 1 includes a control unit 10 and a storage unit 11.

  The control unit 10 includes a proxy unit 12, a communication extraction unit 13, and a communication reproduction unit 14. The proxy unit 12 records communication data related to a series of operations performed by the web browser 2 between the web browser 2 and the web server 3 as a communication history. Further, the proxy unit 12 includes a request recording unit 121, a request transmission unit 122, a response transmission unit 123, and a response recording unit 124. The communication extraction unit 13 extracts communication data used for reproduction from the recorded communication history, and records the extracted communication data. Furthermore, the communication extraction unit 13 includes an authentication state extraction unit 131, a screen transition extraction unit 132, and a reproduction extraction unit 133. The communication reproduction unit 14 reproduces an operation using communication data used for reproduction. The control unit 10 is, for example, an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array) or an electronic circuit such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit).

  The storage unit 11 has a communication recording table 111. The communication record table 111 stores a communication history and finally stores a communication history used for reproduction. The storage unit 11 is, for example, a semiconductor memory device such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk.

  The request recording unit 121 sequentially records request data transmitted from the web browser 2 in the communication recording table 111. The request transmission unit 122 transmits the request data transmitted from the web browser 2 to the web server.

  The response recording unit 124 sequentially records response data corresponding to the request data transmitted from the web server 2 in the communication recording table 111. The response transmission unit 123 transmits response data corresponding to the request data transmitted from the web server 2 to the web browser 2.

  Here, the data structure of the communication record table 111 will be described with reference to FIG. FIG. 3 is a diagram illustrating an example of the data structure of the communication record table 111. As shown in FIG. 3, the communication record table 111 stores request data 111b and response data 111c in association with each identification number 111a. The request data 111b indicates data related to a request transmitted from the web browser 2. The response data 111c indicates data related to the response to the request. The identification number 111a indicates a number for identifying a set of communication histories in which the request data 111b and the response data 111c are associated with each other. The identification number 111a is assigned in the order received.

  As an example, when the identification number 111a is “1”, request data “GET / login HTTP / 1.0 Host: sample.com” for acquiring a login screen is stored as the request data 111b. Response data “HTTP 1.0 200 OK... <Html> login screen... </ Html>” that displays a login screen is stored as response data 111c.

  Returning to FIG. 2, the authentication status extraction unit 131 operates the communication history associated with the response data 111 c in which information used for session management exists based on the communication history stored in the communication record table 111. Extract as communication to reproduce. The information used for session management refers to, for example, a session id (identification) set in the Set-Cookie header.

  Here, communication using the session id will be described. The session id is set by the web server 3 when the authentication state is changed by an operation (for example, login or logout) of the web browser 2. When the session id set in the Set-Cookie header by the web server 3 is transmitted to the web browser 2, the web browser 2 performs session management using the transmitted session id. For example, the web browser 2 transmits request data in which the transmitted session id is added to the Cookie header to the web server 3. Thereby, on the web server 3 side, the authentication information can be confirmed using the transmitted session id. Further, the web browser 2 can access the screen after the login screen in which the authentication is confirmed using the session id. For this reason, in order to reproduce the operation, it is determined that the communication in which the cookie header capable of knowing the session id is set as the minimum necessary communication. If the communication in which the Set-Cookie header is set is omitted, since the session id cannot be known, the reproduction result changes. That is, it is determined that the communication whose result is changed when the operation is reproduced without reproduction is the minimum necessary communication. Therefore, the authentication state extraction unit 131 operates the communication history associated with the response data 111c in which the session id set in the Set-Cookie header exists based on the communication history stored in the communication record table 111. Extract as communication to reproduce.

  Based on the communication history stored in the communication record table 111, the screen transition extraction unit 132 obtains a series of communication histories obtained by tracing information used to manage screen transitions displayed on the web browser 2 side. Extract. For example, the URL of an image embedded in an HTML sentence is a URL that does not affect the result even if it is omitted and reproduced. Therefore, the screen transition extraction unit 132 omits the communication history including the URL, and extracts the communication history that affects the result if the communication history is omitted and reproduced as communication for reproducing the operation. Here, the information used for managing the transition of the screen refers to a referer indicating the URL of the screen before the transition, and is information set in the request data 111b.

  Specifically, the screen transition extraction unit 132 extracts a communication history obtained by following screen transitions until reaching the last screen to be reproduced. The method of following the screen transition uses that the web browser 2 adds a Referer to the Referer header of the request data. By using this, the screen transition extraction unit 132 refers to the URL of the Referer header from the communication history of accessing the last screen to be reproduced, and specifies the communication of the screen accessed before that, so that a series of Follow screen transitions. As an example, the screen transition extraction unit 132 refers to the Referer set in the request data, and selects request data that is equivalent to the Referer referred to by the request destination URL from among the request data before the request data. Then, the screen transition extraction unit 132 extracts a communication history associated with the selected request data.

  The reproduction extraction unit 133 extracts the communication history extracted by the authentication state extraction unit 131 and the communication history extracted by the screen transition extraction unit 132 while maintaining the order as communication for reproducing the operation. For example, the reproduction extraction unit 133 takes the union of the communication history extracted by the authentication state extraction unit 131 and the communication history extracted by the screen transition extraction unit 132. Then, the reproduction extraction unit 133 deletes communication histories other than the union from communication histories stored in the communication record table 111 as unnecessary communication, and extracts communication histories that omit communication unnecessary for reproduction.

  The communication reproduction unit 14 reproduces the operation using the communication history stored in the communication record table 111. For example, the communication reproduction unit 14 reads a communication history from the communication record table 111 from which unnecessary communication has been deleted by the reproduction extraction unit 133, and reproduces an operation using the read communication history.

[Authentication status extraction process]
Next, the procedure of the authentication status extraction process by the authentication status extraction unit 131 will be described with reference to FIG. FIG. 4 is a flowchart illustrating the procedure of the authentication state extraction process according to the first embodiment. It is assumed that a communication history is recorded in the communication record table 111 for a series of operations performed by the web browser 2.

  First, the authentication state extraction unit 131 acquires the communication history array R [n] from the communication record table 111 (step S11). Here, n indicates the number of communication histories up to the screen desired to be reproduced. Then, the authentication state extraction unit 131 prepares a set S of output communication histories (step S12).

  Subsequently, the authentication state extraction unit 131 sets an initial value 0 to the index i indicating the subscript of the array (step S13). Then, the authentication status extraction unit 131 sets the communication history array R [i] in the variable r (step S14).

  Then, the authentication state extraction unit 131 determines whether or not there is a Set-Cookie header in the response data of the communication history set in the variable r (step S15). If it is determined that there is a Set-Cookie header (step S15; Yes), the authentication state extraction unit 131 adds a variable r to the set S as communication for reproducing the operation (step S16). That is, when the Set-Cookie header is included in the response data, it means that the authentication state has been changed by the operation of the web browser 2. Therefore, the authentication state extraction unit 131 extracts communication having the Set-Cookie header as communication that reproduces the operation.

  On the other hand, when it determines with there being no Set-Cookie header (step S15; No), the authentication state extraction part 131 transfers to step S17. Then, the authentication state extraction unit 131 adds 1 to the index i (step S17).

  Subsequently, the authentication state extraction unit 131 determines whether or not the index i is larger than n−1 (step S18). When it determines with the index i not being larger than n-1 (step S18; No), the authentication state extraction part 131 transfers to step S14 in order to determine the next communication history. On the other hand, when it determines with the index i being larger than n-1 (step S18; Yes), the authentication state extraction part 131 outputs the set S to the reproduction extraction part 133 (step S19). Then, the authentication state extraction unit 131 ends the process.

[Screen transition extraction procedure]
Next, a procedure of screen transition extraction processing by the screen transition extraction unit 132 will be described with reference to FIG. FIG. 5 is a flowchart illustrating the procedure of the screen transition extraction process according to the first embodiment. It is assumed that a communication history is recorded in the communication record table 111 for a series of operations performed by the web browser 2.

  First, the screen transition extraction unit 132 acquires the communication history array R [n] from the communication record table 111 (step S21). Here, n indicates the number of communication histories up to the screen desired to be reproduced. Then, the screen transition extraction unit 132 prepares an output communication history set T (step S22).

  Subsequently, the screen transition extraction unit 132 sets the array R [n] of the communication history accessed last to the variable t (step S23). Then, the screen transition extraction unit 132 sets the last communication history subscript n-1 to the index i indicating the subscript of the array (step S24). The screen transition extraction unit 132 sets the communication history array R [i] in the variable r (step S25).

  Then, the screen transition extraction unit 132 determines whether or not the value of the Refer header of the variable t and the request destination URL of the variable r are equal (step S26). When it is determined that the Referrer header value of the variable t and the request destination URL of the variable r are equal (step S26; Yes), the screen transition extraction unit 132 adds the variable r to the set T (step S27). . That is, when the value of the Referer header of the variable t and the request destination URL of the variable r are equal, the transition from the screen displayed by the communication of the variable r to the screen displayed by the communication of the variable t means. Therefore, the screen transition extraction unit 132 extracts the communication of the variable r as a communication history that reproduces the operation.

  Then, the screen transition extraction unit 132 updates the variable t to the variable r (Step S28). That is, the screen transition extraction unit 132 further updates the variable t indicating the communication history accessed last to the variable r so as to trace the screen transition from the communication history of the variable r.

  On the other hand, when it is determined that the value of the Referer header of the variable t and the request destination URL of the variable r are not equal (step S26; No), the screen transition extraction unit 132 proceeds to step S29. Then, the screen transition extraction unit 132 subtracts 1 from the index i (step S29).

  Subsequently, the screen transition extraction unit 132 determines whether the index i is smaller than 0 (step S30). If it is determined that the index i is not smaller than 0 (step S30; No), the screen transition extraction unit 132 proceeds to step S25 to determine the next communication history. On the other hand, when it is determined that the index i is smaller than 0 (step S30; Yes), the screen transition extraction unit 132 outputs the set T to the reproduction extraction unit 133 (step S31). Then, the screen transition extraction unit 132 ends the process.

[Reproduction extraction procedure]
Next, the procedure of the reproduction extraction process by the reproduction extraction unit 133 will be described with reference to FIG. FIG. 6 is a flowchart illustrating the procedure of the reproduction extraction process according to the first embodiment. It is assumed that a communication history is recorded in the communication record table 111 for a series of operations performed by the web browser 2.

  The reproduction extraction unit 133 acquires the communication set S extracted by the authentication state extraction unit 131 and the communication set T extracted by the screen transition extraction unit 132. Furthermore, the reproduction extraction unit 133 acquires the communication history array R [n] from the communication record table 111 (step S41). Here, n indicates the number of communication histories up to the screen desired to be reproduced.

  Then, the reproduction extraction unit 133 sets an initial value 0 to the index i indicating the array subscript (step S42). Then, the reproduction extraction unit 133 sets the communication history array R [i] in the variable r (step S43).

  Subsequently, the reproduction extraction unit 133 determines whether or not the communication history set in the variable r is included in the union of the set S and the set T (step S44). When it is determined that the communication history is not included in the union of the set S and the set T (step S44; No), the reproduction extraction unit 133 deletes the communication history of the variable r from the array R (step S45). That is, the reproduction extraction unit 133 sets communication histories that are not included in the union of the set S and the set T among the communication histories stored in the communication history table 111 as communication histories unnecessary for reproduction.

  On the other hand, when it is determined that the communication history is included in the union of the set S and the set T (step S44; Yes), the reproduction extraction unit 133 proceeds to step S46 to add the index i. Then, the reproduction extraction unit 133 adds 1 to the index i (step S46).

  Subsequently, the reproduction extraction unit 133 determines whether or not the index i is larger than n−1 (step S47). If it is determined that the index i is not greater than n−1 (step S47; No), the reproduction extraction unit 133 proceeds to step S43 to determine the next communication history. On the other hand, when it is determined that the index i is greater than n−1 (step S47; Yes), the reproduction extraction unit 133 reflects the communication history R in the communication record table 111 (step S48). Then, the reproduction extraction unit 133 ends the process.

[Specific examples of communication records]
Next, a specific example of communication recording will be described with reference to FIG. FIG. 7 is a diagram illustrating a specific example of the communication record. As shown in FIG. 7, the communication record stores request data and response data in association with each identification number. The larger the identification number, the newer the communication recording time.

[Specific example of screen transition]
Next, transition of each screen corresponding to each communication history shown in FIG. 7 will be described with reference to FIG. FIG. 8 is a diagram illustrating a specific example of the screen transition displayed on the web browser 2. As illustrated in FIG. 8, the web browser 2 displays a login screen A <b> 1 after performing communication associated with the identification number 1 with the web server 3. Next, the web browser 2 performs communication associated with the identification number 2 with the web server 3 and then displays the image “a1” of “logo.gif” on the login screen A1. Further, the web browser 2 performs communication associated with the identification number 2 with the web server 3 and then displays a screen “a2” of “info.html” on the login screen A1. Next, after the user presses “login” on the login screen A1 and the web browser 2 performs communication associated with the identification number 4 with the web server 3, the top page screen A2 after login is displayed. Is displayed. Next, after performing communication associated with the identification number 5 with the web server 3, the web browser 2 displays the image a3 of “logo2.gif” on the top page screen A2 after login. Further, after the user presses “Setting” and the web browser 2 performs communication associated with the identification number 6 with the web server 3, the setting information page A3 is displayed.

[Specific example of authentication status extraction processing]
Next, authentication status extraction processing using each communication history shown in FIG. 7 will be described with reference to FIG. FIG. 9 is a diagram illustrating a specific example of the authentication state extraction process. As shown in FIG. 9, the Set-Cookie header is set in the response data of the identification numbers 4 and 6.

  The authentication status extraction unit 131 determines in order from the identification number 1 whether or not the response data associated with the identification number includes a Set-Cookie header. Here, the authentication state extraction unit 131 determines that the response data associated with the identification number 4 includes the Set-Cookie header b1. Then, the authentication state extraction unit 131 extracts a communication history corresponding to the identification number 4. That is, at the identification number 4, since the authentication state has changed due to the “login” operation of the web browser 2, the authentication state extraction unit 131 extracts the communication history corresponding to the identification number 4 as communication for reproducing the operation. Furthermore, the authentication status extraction unit 131 determines that the response data associated with the identification number 6 includes the Set-Cookie header b2. Then, the authentication state extraction unit 131 extracts a communication history corresponding to the identification number 6. That is, at the identification number 6, since the authentication state has been changed by pressing “Setting” of the web browser 2, the authentication state extraction unit 131 extracts the communication history corresponding to the identification number 6 as communication for reproducing the operation.

  In this way, the authentication state extraction unit 131 extracts communication in which a session id used for session management is set as communication that reproduces an operation. Here, the authentication state extraction unit 131 extracts the communication history of the identification numbers 4 and 6 as communication for reproducing the operation.

[Specific example of screen transition extraction processing]
Next, the screen transition extraction process using each communication history shown in FIG. 7 will be described with reference to FIG. FIG. 10 is a diagram illustrating a specific example of the screen transition extraction process. As illustrated in FIG. 10, the screen transition extraction unit 132 refers to the Referer set in the last communication history, traces the communication history from the last communication history, and the request destination URL is the value of the referred Referer. Extract communication history that is equivalent. Here, the communication history with the identification number 6 is the last communication history, and the Referer set in the request data with the identification number 6 is “http://sample.com/top” c1.

  Then, the screen transition extraction unit 132 refers to the Referer set in the request data with the identification number 6, and extracts the communication history with the identification number 4 as the communication history that is equal to the value of the Referer referred to by the request destination URL. To do. The request destination URL of the identification number 4 is “sample.com/top” from the “sample.com” c3 indicating the domain and the “/ top” c2 indicating the path, and is therefore set in the request data of the identification number 6. Equivalent to Referer. Therefore, the screen transition extraction unit 132 extracts the communication history with the identification number 4 as communication for reproducing the operation. Since the URL of the request destination with the identification number 5 is “sample.com/logo2.gif”, it is not equivalent to the Referer set in the request data with the identification number 6, and is unnecessary as communication for reproducing the operation. Communication is not extracted.

  Further, the screen transition extraction unit 132 refers to the Referer set in the communication history with the identification number 4, traces back the communication history from the communication history with the identification number 4, and is equal to the value of the Referer referred to by the request destination URL. The communication history that is is extracted. Here, the Referer set in the request data with the identification number 4 is “http://sample.com/login” c4.

  Then, the screen transition extraction unit 132 refers to the Referer set in the request data with the identification number 4, and extracts the communication history with the identification number 1 as the communication history that is equal to the value of the Referrer referred to by the request destination URL. To do. Since the request destination URL of the identification number 1 is “sample.com/login” from “sample.com” c6 indicating the domain and “/ login” c5 indicating the path, it is set in the request data of the identification number 4. Equivalent to Referer. Accordingly, the screen transition extraction unit 132 extracts the communication history with the identification number 1 as communication for reproducing the operation. Note that the request destination URLs with the identification numbers 2 and 3 are not equivalent to the Referer set in the request data with the identification number 6, and are unnecessary communications as communications for reproducing the operation and are not extracted.

  In this way, the screen transition extraction unit 132 extracts a series of communications obtained by tracing the previous communication history from the last communication history Referer as communications that reproduce the operation. Here, the screen transition extraction unit 132 extracts the communication history of the identification numbers 1, 4, and 6 as communication for reproducing the operation.

[Specific example of reproduction extraction processing]
Next, the reproduction extraction process using each communication history shown in FIG. 7 will be described with reference to FIG. FIG. 11 is a diagram illustrating a specific example of the reproduction extraction process.

  The reproduction extraction unit 133 takes the union of the communication history extracted by the authentication state extraction unit 131 and the communication history extracted by the screen transition extraction unit 132. Here, the communication histories extracted by the authentication state extraction unit 131 are the communication histories of the identification numbers 4 and 6. The communication histories extracted by the screen transition extraction unit 132 are the communication histories of the identification numbers 1, 4, and 6. Therefore, the reproduction extraction unit 133 sets each communication history with the identification numbers 1, 4, and 6 as a union of communication histories. Then, the reproduction extraction unit 133 deletes communication histories other than the union from the communication histories stored in the communication record table 111, and extracts communication histories that omit communication unnecessary for reproduction. Here, the reproduction extraction unit 133 deletes the communication histories of the identification numbers 2, 3, and 5, and extracts the communication histories of the identification numbers 1, 4, and 6 that omit communication unnecessary for reproduction.

  In this way, the reproduction extraction unit 133 extracts the union of the communication history extracted by the authentication state extraction unit 131 and the communication history extracted by the screen transition extraction unit 132 as communication for reproducing the operation. Here, the reproduction extraction unit 133 extracts the communication history of the identification numbers 1, 4, and 6 as communication for reproducing the operation.

[Specific example of communication reproduction processing]
Next, communication reproduction processing using each communication history extracted in FIG. 11 will be described with reference to FIG. FIG. 12 is a diagram illustrating a specific example of the communication reproduction process. The communication reproduction process does not return any response other than the response corresponding to the last communication history to the web browser 2 when reproducing the operation using the communication history. Therefore, the web browser 2 does not actually display the screen using the response from the last to the previous communication history. However, in FIG. 12, for convenience of explanation, when a response is returned to the web browser 2, the communication reproduction process is described using a screen displayed on the web browser 2 side.

  The communication reproduction unit 14 reads the communication history from the communication record table 111 from which unnecessary communication has been deleted by the reproduction extraction unit 133, and reproduces the operation using the read communication history. Specifically, the communication reproduction unit 14 reproduces communication using a communication history associated with the identification number 1. Here, if the response is returned to the web browser 2, the web browser 2 displays the login screen A1. Next, the communication reproduction unit 14 reproduces communication using the communication history associated with the identification number 4. Here, if a response is returned to the web browser 2, the web browser 2 displays the top page A2 after login. That is, the communication associated with the identification number 2 that displays the image of “logo.gif” and the communication associated with the identification number 3 that displays the screen of “info.html” are excluded. Even if these communications are omitted, the reproduction result does not change, and the top page A2 after login is displayed. Further, the communication reproduction unit 14 reproduces the communication using the last communication history associated with the identification number 6. Here, when the response is returned to the web browser 2, the web browser 2 displays the setting information page A3. That is, the communication associated with the identification number 5 in which the image “logo2.gif” is displayed is excluded, but even if this communication is omitted, the reproduction result does not change and the setting information page A3 is displayed. The

  In this way, when reproducing the operation using the communication history, the communication reproduction unit 14 reproduces communication in which the reproduction result changes if the operation is omitted. In other words, the communication reproduction unit 14 does not reproduce any communication other than the communication whose reproduction result is changed when the operation is reproduced without reproduction. Thereby, the communication reproduction part 14 can reproduce at high speed compared with the case where it reproduces using all the communication histories.

[Effect of Example 1]
According to the first embodiment, the authentication state extraction unit 131, based on the communication history stored in the communication record table 111, the communication history associated with the response data including the Set-Cookie header used for session management. To extract. The screen transition extraction unit 132 is used to manage screen transitions that are information included in the request data and displayed on the web browser 2 side based on the communication history stored in the communication record table 111. A series of communication histories obtained by tracing the Referer header is extracted. Then, the communication reproduction unit 14 reproduces the operation using the union of the communication history extracted by the authentication state extraction unit 131 and the communication history extracted by the screen transition extraction unit 132. According to such a configuration, the relay device 1 extracts a communication history that has an effect on the reproduction result if the reproduction is performed without an operation, that is, a communication history in which the Set-Cookie header is present in the response data. Further, the relay device 1 extracts a series of communication histories obtained by tracing the Referer header of the request data so as to omit a communication history including a URL that does not affect the reproduction result in the HTML sentence. Thereby, when reproducing the operation, the relay device 1 omits the communication history that does not affect the reproduction result even if the operation is omitted, so that the reproduction process can be performed at high speed.

  By the way, in the relay apparatus 1 according to the first embodiment, as a communication history that does not affect the reproduction result, for example, a communication history including an image URL embedded in an HTML sentence is excluded as a communication that omits an operation. . However, the relay device 1 is not limited to this, and excludes the communication history of the parent screen that only describes the configuration of the small screen as the communication history that does not affect the reproduction result as the communication that omits the operation. May be. Therefore, in the second embodiment, a relay device 1A that excludes the communication history of the parent screen that only describes the configuration of the small screen as the communication history that does not affect the reproduction result as communication that omits the operation will be described.

[Configuration of Relay Device According to Second Embodiment]
FIG. 13 is a functional block diagram illustrating the configuration of the relay device according to the second embodiment. In addition, about the same structure as the relay apparatus 1 shown in FIG. 2, the same code | symbol is shown, and the description of the overlapping structure and operation | movement is abbreviate | omitted. The difference between the first embodiment and the second embodiment is that a small screen extracting unit 201 is added to the communication extracting unit 13. Further, the difference between the first embodiment and the second embodiment is that the reproduction extraction unit 133 is changed to a reproduction extraction unit 133A.

  The small screen extraction unit 201 deletes the communication history of the screen (parent screen) that only describes the configuration of the frame (small screen) from the communication history extracted by the screen transition extraction unit 132. In other words, the HTML of the parent screen that only describes the configuration of the small screen only declares that the small screen is to be arranged, and thus does not require communication of the parent screen. Here, with reference to FIG. 14A to FIG. 14C, it will be described that communication of the main screen that only describes the configuration of the small screen is unnecessary.

  FIG. 14A is a diagram showing HTML of the main screen of the login screen. FIG. 14B is a diagram showing HTML corresponding to each small screen. FIG. 14C is a diagram showing an example of a screen composed of small screens. As shown in FIG. 14A, a “frameset” tag that configures a small screen is set in the HTML of the parent screen of the login screen. In the “frameset” tag, “/title.html” indicating a title screen, “/link.html” indicating a link screen, and “/ login” indicating a login screen are set as small screens. That is, the HTML shown in FIG. 14A declares that the parent screen is arranged with a title screen, a link screen, and a login screen. And the screen comprised by the content of each small screen shown in FIG. 14C is displayed by HTML corresponding to each small screen shown in FIG. 14B. Then, since the HTML of the parent screen shown in FIG. 14A is HTML that only describes the configuration of the small screen, even if communication of the parent screen is omitted, the screen transition is not affected. Therefore, if there is a “frameset” tag in the response history response HTML, and the value of “frame src” points to the next request destination, the communication having this “frameset” tag is determined as the parent screen, and unnecessary communication is performed. Eliminate as.

  The reproduction extraction unit 133A extracts the communication history extracted by the authentication state extraction unit 131 and the communication history extracted by the small screen extraction unit 201 while maintaining the order as communication necessary for reproduction. For example, the reproduction extraction unit 133A takes the union of the communication history extracted by the authentication state extraction unit 131 and the communication history extracted by the small screen extraction unit 201. Then, the reproduction extraction unit 133A deletes communication histories other than the union from communication histories stored in the communication record table 111 as unnecessary communication, and extracts communication histories that omit communication unnecessary for reproduction.

[Small screen extraction processing procedure]
Next, the procedure of small screen extraction processing by the small screen extraction unit 201 will be described with reference to FIG. FIG. 15 is a flowchart illustrating the procedure of the small screen extraction process according to the second embodiment. It is assumed that a communication history is recorded in the communication record table 111 for a series of operations performed by the web browser 2. In addition, it is assumed that the corresponding communication history is extracted by the screen transition extraction unit 132.

  First, the small screen extraction unit 201 acquires the communication set T extracted by the screen transition extraction unit 132 from the screen transition extraction unit 132 (step S51). Here, it is assumed that there are n communication histories belonging to the communication set T. The small screen extraction unit 201 sets n−1 indicating the last communication history of the set T to the index i indicating the subscript of the array (step S52).

  Subsequently, the small screen extraction unit 201 sets the communication history array T [i] in the variable s (step S53). Then, the small screen extraction unit 201 determines whether or not the response data of the variable s is an HTML document and includes a “frameset” tag (step S54). The small screen extraction unit 201 determines whether or not the response data is an HTML document based on whether or not “Content_Type: text / html” is set in the response data.

  When it is determined that the response data is an HTML document and the “frameset” tag is included (step S54; Yes), the small screen extraction unit 201 uses the src attribute of each frame tag surrounded by the “frameset” tag of the response data. Are stored in the set F (step S55). Then, the small screen extraction unit 201 sets n−1 indicating the last communication history of the set T to the index m (step S56).

  Subsequently, the small screen extraction unit 201 sets the communication history array T [m] in the variable t (step S57). Then, the small screen extraction unit 201 determines whether the request destination URL of the variable t is included in the set F and the value of the Refer header of the variable t is equal to the request destination URL of the variable s. (Step S58). When it is determined that the request destination URL is included in the set F and the value of the Referer header of the variable t is equal to the request destination URL of the variable s (step S58; Yes), the small screen extraction unit 201 The communication history of variable s is deleted from set T (step S59). That is, the small screen extraction unit 201 determines that the communication represented by the variable s is the parent screen of the communication represented by the variable t, and excludes it as unnecessary communication. Then, the small screen extraction unit 201 proceeds to step S62 to subtract the index i.

  On the other hand, when it is determined that the request destination URL is not included in the set F or the value of the Referer header of the variable t is not equal to the request destination URL of the variable s (step S58; No), the small screen extraction unit 201 Subtracts 1 from the index m (step S60). Then, the small screen extraction unit 201 determines whether the index m is smaller than 0 (step S61). When it is determined that the index m is 0 or more (step S61; No), the small screen extraction unit 201 proceeds to step S57 to select the next communication history.

  When it is determined that the index m is smaller than 0 (step S61; Yes), the small screen extraction unit 201 subtracts 1 from the index i (step S62). Then, the small screen extraction unit 201 determines whether or not the index i is smaller than 0 (step S63). When it is determined that the index i is greater than or equal to 0 (step S63; No), the small screen extraction unit 201 proceeds to step S53 in order to search for the next “frameset” tag.

  On the other hand, when it is determined that the index i is smaller than 0 (step S63; Yes), the small screen extraction unit 201 outputs the set T to the reproduction extraction unit 133A (step S64). Then, the small screen extraction unit 201 ends the process.

[Specific examples of communication records]
Next, a specific example of communication recording will be described with reference to FIG. FIG. 16 is a diagram illustrating a specific example of communication recording. As shown in FIG. 16, the communication record stores request data and response data in association with each identification number. The larger the identification number, the newer the communication recording time.

[Specific example of screen transition]
Next, transition of each screen corresponding to each communication history shown in FIG. 16 will be described with reference to FIG. FIG. 17 is a diagram illustrating a specific example of the screen transition displayed on the web browser 2. As illustrated in FIG. 17, the web browser 2 displays the parent screen B <b> 1 after performing communication associated with the identification number 1 with the web server 3. Next, the web browser 2 performs communication associated with the identification number 2 with the web server 3, and then displays the title screen d1 on the parent screen B1. Next, the web browser 2 performs communication associated with the identification number 3 with the web server 3, and then displays the link screen d2 on the parent screen B1. Next, the web browser 2 performs communication associated with the identification number 4 with the web server 3, and then displays the login screen d3 on the parent screen B1. Next, the web browser 2 performs communication associated with the identification number 5 with the web server 3, and then displays an image d4 of “logo.gif” on the login screen d3. Next, after performing communication associated with the identification number 6 with the web server 3, the web browser 2 displays a screen d5 of “info.html” on the login screen d3.

  Further, after the user presses “login” on the login screen d3 and the web browser 2 performs communication associated with the identification number 7 with the web server 3, the main screen B2 after login is displayed. To do. Next, the web browser 2 performs communication associated with the identification number 8 with the web server 3, and then displays the title screen d6 on the main screen B2 after login. Next, the web browser 2 performs communication associated with the identification number 9 with the web server 3, and then displays the link screen d7 on the main screen B2 after login. Furthermore, after performing communication associated with the identification number 10 with the web server 3, the web browser 2 displays the post-login menu screen d8 on the main screen B2 after login.

[Specific examples of communication records extracted by screen transition extraction processing]
Next, screen transition extraction processing using each communication history shown in FIG. 16 will be described with reference to FIG. FIG. 18 is a diagram illustrating a specific example of the screen transition extraction process. As illustrated in FIG. 18, the screen transition extraction unit 132 refers to the Referer set in the last communication history, traces the communication history from the last communication history, and the URL of the request destination is the value of the referred Referer. Extract communication history that is equivalent. Here, the screen transition extraction unit 132 traces the communication history from the last communication history of the identification number 10, and the communication of the identification number 7 in which the URL of the request destination is equal to the value of the referred Referer in the identification number 10. Extract history. Further, the screen transition extraction unit 132 extracts the communication history of the identification number 4 in which the request destination URL is equal to the referred Referer value in the identification number 7 by tracing the communication history from the communication history of the identification number 7. To do. Further, the screen transition extraction unit 132 extracts the communication history of the identification number 1 in which the request destination URL is equal to the referred Referer value in the identification number 4 by tracing the communication history from the communication history of the identification number 4. To do.

[Specific example of small screen extraction processing]
Next, small screen extraction processing using each communication history shown in FIG. 18 will be described with reference to FIG. FIG. 19 is a diagram illustrating a specific example of the small screen extraction process. Each communication history shown in FIG. 19 represents each communication history shown in FIG. 18 in detail. As illustrated in FIG. 19, the small screen extraction unit 201 searches the communication history from the last communication history (identification number 10) for the communication history response data including the “frameset” tag. To do. Then, the small screen extraction unit 201 extracts the URL value of the src attribute in the frame tag from the response data including the “frameset” tag. Here, the small screen extraction unit 201 determines that the response data of the identification number 7 includes “frameset” tags E1 and E2. Then, the small screen extraction unit 201 extracts “/title.html” e1, “/link.html” e2, and “/menu.html” e3 which are URL values of the src attribute in the frame tag.

  Further, the small screen extraction unit 201 searches for a communication history different from the identification number 7 and determines whether the request destination URL of the searched communication history is the same as any value of the src attribute. In addition, the small screen extraction unit 201 determines whether or not the value of the Referer header of the searched communication history is equal to the request destination URL of the communication history having the src attribute. Here, the request destination URL of the identification number 10 is “/menu.html” f1, and the small screen extraction unit 201 determines that the request destination URL is the same as “/menu.html” e3 of the src attribute. . Also, the value of the Referer header with the identification number 10 is “http://sample.com/”r1, and the request destination URL of the communication history having the src attribute is“ sample.com ”g1. For this reason, the small screen extraction unit 201 determines that the value indicated by r1 is equal to the value indicated by g1. Therefore, the small screen extraction unit 201 determines that the screen corresponding to the identification number 7 is a parent screen that only describes the configuration of the small screen including the menu screen, and determines the communication history (identification number 7) of the parent screen. delete. On the other hand, the small screen extraction unit 201 extracts the communication history with the identification number 10 as a communication history for reproducing the operation.

  Subsequently, the small screen extraction unit 201 searches the communication history retrospectively for the communication history response data including the “frameset” tag. Then, the small screen extraction unit 201 extracts the URL value of the src attribute in the frame tag from the response data including the “frameset” tag. Here, the small screen extraction unit 201 determines that the response data with the identification number 1 includes “frameset” tags E3 and E4. Then, the small screen extracting unit 201 extracts “/title.html” e4, “/link.html” e5, and “/ login” e6 which are URL values of the src attribute in the frame tag.

  Further, the small screen extraction unit 201 searches for a communication history different from the identification number 1, and determines whether the request destination URL of the searched communication history is the same as any value of the src attribute. In addition, the small screen extraction unit 201 determines whether or not the value of the Referer header of the searched communication history is equal to the request destination URL of the communication history having the src attribute. Here, the request destination URL of the identification number 4 is “/ login” f2, and the small screen extraction unit 201 determines that the request destination URL is the same as “/ login” e6 of the src attribute. In addition, the value of the Refer header with the identification number 4 is “http://sample.com/parent” r2. The request destination URL of the communication history having the src attribute is “sample.com/parent” from “sample.com” g3 indicating the domain and “/ parent” g2 indicating the path. Therefore, the small screen extraction unit 201 determines that the value of the Referer header with the identification number 4 and the request destination URL of the communication history having the src attribute are equal. Therefore, the small screen extraction unit 201 determines that the identification number 1 is a parent screen that only describes the configuration of the small screen including the login screen, and deletes the communication history (identification number 1) of the parent screen. On the other hand, the small screen extraction unit 201 extracts the communication history with the identification number 4 as a communication history for reproducing the operation.

  In this way, the small screen extraction unit 201 excludes communication of the main screen that only describes the configuration of the small screen, and extracts communication of the small screen itself as communication that reproduces the operation. Here, the small screen extraction unit 201 extracts the communication history with the identification numbers 4 and 10 as communication for reproducing the operation.

[Specific example of reproduction extraction processing]
Next, reproduction extraction processing using each communication history shown in FIG. 16 will be described with reference to FIG. FIG. 20 is a diagram illustrating a specific example of the reproduction extraction process.

  The reproduction extraction unit 133A takes the union of the communication history extracted by the authentication state extraction unit 131 and the communication history extracted by the small screen extraction unit 201. Here, it is assumed that the communication history extracted by the authentication state extraction unit 131 is the communication history of the identification numbers 4 and 10. The communication history extracted by the small screen extraction unit 201 is also the communication history with the identification numbers 4 and 10. Therefore, the reproduction extraction unit 133A takes the identification numbers 4 and 10 as the union of communication histories. Then, the reproduction extraction unit 133A deletes communication histories other than the union from the communication histories stored in the communication record table 111, and extracts communication histories that omit communication unnecessary for reproduction. Here, the reproduction extraction unit 133A deletes the communication histories of the identification numbers 1 to 3 and 5 to 9, and extracts the communication histories of the identification numbers 4 and 10 that omit communication unnecessary for reproduction.

  In this way, the reproduction extraction unit 133A extracts the union of the communication history extracted by the authentication state extraction unit 131 and the communication history extracted by the small screen extraction unit 201 as communication for reproducing the operation. Here, the reproduction extraction unit 133A extracts the communication history with the identification numbers 4 and 10 as communication for reproducing the operation.

[Specific example of communication reproduction processing]
Next, communication reproduction processing using each communication history extracted in FIG. 20 will be described with reference to FIG. FIG. 21 is a diagram illustrating a specific example of the communication reproduction process. The communication reproduction process does not return any response other than the response corresponding to the last communication history to the web browser 2 when reproducing the operation using the communication history. Therefore, the web browser 2 does not actually display the screen using the response from the last to the previous communication history. However, in FIG. 21, for convenience of explanation, when a response is returned to the web browser 2, the communication reproduction process is described using a screen displayed on the web browser 2 side.

  The communication reproduction unit 14 reads the communication history from the communication record table 111 from which unnecessary communication has been deleted by the reproduction extraction unit 133, and reproduces the operation using the read communication history. Specifically, the communication reproduction unit 14 reproduces communication using a communication history associated with the identification number 4. Here, if a response is returned to the web browser 2, the web browser 2 displays a login screen d3. That is, the communication associated with the identification number 1 in which the parent screen B1 is displayed is excluded, but even if this communication is omitted, the reproduction result does not change and the login screen d3 is displayed. Next, the communication reproduction unit 14 reproduces the communication using the last communication history associated with the identification number 10. Here, when the response returns to the web browser 2, the web browser 2 displays a menu screen d8 after login. That is, the communication associated with the identification number 7 on which the parent screen B2 is displayed is excluded, but even if this communication is omitted, the reproduction result does not change and the post-login menu screen d8 is displayed.

  In this way, when reproducing the operation using the communication history, the communication reproduction unit 14 reproduces the communication without the parent screen communication as the communication whose reproduction result does not change even if the operation is omitted. Thereby, the communication reproduction part 14 can reproduce at high speed compared with the case where it reproduces using all the communication histories.

[Effect of Example 2]
According to the second embodiment, the authentication status extraction unit 131, based on the communication history stored in the communication record table 111, the communication history associated with the response data including the Set-Cookie header used for session management. To extract. The screen transition extraction unit 132 is used to manage screen transitions that are information included in the request data and displayed on the web browser 2 side based on the communication history stored in the communication record table 111. A series of communication histories obtained by tracing the Referer header is extracted. Furthermore, the small screen extraction unit 201 uses the communication history extracted by the screen transition extraction unit 132 to display the communication history associated with the response data including “frameset” used when configuring the small screen in the screen. Delete the communication history excluding the deleted communication history. The communication reproduction unit 14 reproduces the operation using the union of the communication history extracted by the authentication state extraction unit 131 and the communication history extracted by the small screen extraction unit 201. According to such a configuration, the relay apparatus 1A deletes the communication history associated with the response data including “frameset” used when the small screen is configured in the screen. As a result, when reproducing the operation, the relay device 1A omits the communication history of the main screen that only describes the configuration of the small screen as the communication history that does not affect the reproduction result even if the operation is omitted. Processing can be performed.

  Note that the authentication status extraction unit 131 uses the communication history associated with the response data 111c in which information used for session management is present as communication for reproducing the operation, based on the communication history stored in the communication record table 111. Extract. In the embodiment, the information used for session management has been described as the session id set in the Set-Cookie header. However, the information used for session management is not limited to this, and may be information set when the authentication state is changed.

  The screen transition extraction unit 132 also obtains a series of communications obtained by tracing information used to manage screen transitions displayed on the web browser 2 side based on the communication history stored in the communication record table 111. Extract history. In the embodiment, the information used for managing the transition of the screen has been described as the URL set in the Referer header. However, the information used for managing the transition of the screen is not limited to this, and may be information indicating the address of the screen before the transition.

  Further, the small screen extraction unit 201 deletes the communication history of the parent screen that only describes the configuration of the small screen from the communication history extracted by the screen transition extraction unit 132. In the embodiment, the communication history of the parent screen that only describes the configuration of the small screen has been described as the communication history including at least the “frameset” tag. However, the communication history of the parent screen that only describes the configuration of the small screen is not limited thereto, and may be information that only describes the configuration of the small screen.

  Moreover, the relay apparatus 1 demonstrated the case where it applied on the same network as the web browser 2. FIG. However, the relay device 1 may be applied on a different network from the web browser 2. In this case, a proxy server may be installed between the web browser 2 and the relay device 1. The proxy server and the relay device 1 can be integrated.

[Programs]
The relay device 1 can be realized by mounting each function such as the proxy unit 12, the communication extraction unit 13, and the communication reproduction unit 14 on an information processing apparatus such as a known personal computer or workstation. .

  In addition, each component of each illustrated apparatus does not necessarily need to be physically configured as illustrated. In other words, the specific mode 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, the screen transition extraction unit 132 and the small screen extraction unit 201 may be integrated as one unit. On the other hand, the communication record table 111 may be distributed into a communication record table for recording communication by the proxy unit 12 and a reproduction record table for recording communication to be reproduced. In such a case, the reproduction extraction unit 133A records the communication history other than the union out of the communication histories stored in the communication record table 111 as unnecessary communication, and records the communication history without communication unnecessary for reproduction in the reproduction record table. It ’s fine. Then, the communication reproduction unit 14 may read the communication history from the reproduction record table and reproduce the operation using the read communication history.

  Further, a storage unit such as the communication record table 111 may be connected as an external device of the relay device 1 via a network.

  The various processes described in the above embodiments can be realized by executing a program prepared in advance on a computer such as a personal computer or a workstation. Therefore, in the following, an example of a computer that executes a relay program having the same function as the control unit 10 of the relay apparatus 1 illustrated in FIG. 2 will be described with reference to FIG.

  FIG. 22 is a diagram illustrating a computer that executes a relay program. As illustrated in FIG. 22, the computer 1000 includes a RAM (Random Access Memory) 1010, a network interface device 1020, an HDD 1030, a CPU (Central Processing Unit) 1040, a medium reading device 1050, and a bus 1060. The RAM 1010, the network interface device 1020, the HDD 1030, the CPU 1040, and the medium reading device 1050 are connected by a bus 1060.

  The HDD 1030 stores a relay program 1031 having the same function as that of the control unit 10 shown in FIG. The HDD 1030 stores relay processing related information 1032 corresponding to the communication record table 111 shown in FIG.

  Then, the CPU 1040 reads the relay program 1031 from the HDD 1030 and develops it in the RAM 1010, so that the relay program 1031 functions as the relay process 1011. Then, the relay process 1011 expands information read from the relay processing related information 1032 and the like in an area allocated to itself on the RAM 1010 as appropriate, and executes various data processing based on the expanded data.

  The medium reading device 1050 reads the relay program 1031 from a medium that stores the relay program 1031 or the like even when the relay program 1031 is not stored in the HDD 1030. Examples of the medium reading device 1050 include a CD-ROM and an optical disk device. The network interface device 1020 is a device connected to an external device via a network, and there are wired and wireless.

  Note that the relay program 1031 is not necessarily stored in the HDD 1030, and the computer 1000 may read and execute the program stored in the medium reader 1050 such as a CD-ROM. In addition, this program may be stored in another computer (or server) connected to the computer 1000 via a public line, the Internet, a LAN (Local Area Network), a WAN (Wide Area Network), or the like. In this case, the computer 1000 reads the program from these via the network interface device 1020 and executes it.

  The following appendices are further disclosed with respect to the embodiments including Examples 1 and 2 described above.

(Additional remark 1) About operation which a web browser performs, the memory | storage part which memorize | stored the communication history which matched the request data transmitted from the said web browser to the web server, and the response data received from the said web server,
A first extraction unit for extracting a communication history associated with the response data in which information used for session management exists based on the communication history stored in the storage unit;
Based on the communication history stored in the storage unit, a series of communications obtained by tracing information that is included in the request data and that is used to manage screen transitions output on the web browser side A second extraction unit for extracting a history;
And a reproduction unit that reproduces the operation using a union of the communication history extracted by the first extraction unit and the communication history extracted by the second extraction unit.

(Additional remark 2) The said 1st extraction part extracts the communication record matched with the said response data to which a cookie is set, The relay apparatus of Additional remark 1 characterized by the above-mentioned.

(Supplementary Note 3) The second extraction unit refers to a referrer that indicates an address of the transition source screen set in the request data in the operation, and among the request data before the request data, an address that requests a request is The relay apparatus according to appendix 1, wherein request data having the same address as the referred referer is selected, and a communication record of the selected request data is extracted.

(Supplementary Note 4) The communication history associated with the response data in which information used when configuring the small screen is present is deleted from the communication history extracted by the second extraction unit, and deleted. A third extraction unit for extracting a communication history excluding the communication history;
The reproduction unit is
Any one of appendix 1 to appendix 3, wherein the operation is reproduced using a union of the communication history extracted by the first extraction unit and the communication history extracted by the third extraction unit. The relay device according to one.

(Appendix 5)
For operations performed by the web browser, based on the communication history stored in the storage unit storing the communication history in which the request data transmitted from the web browser to the web server and the response data received from the web server are associated with each other. Extracting a communication history associated with the response data in which information used for session management exists,
Based on the communication history stored in the storage unit, a series of communications obtained by tracing information that is included in the request data and that is used to manage screen transitions output on the web browser side Extract the history,
A relay program that executes a process of reproducing the operation using a union of communication histories extracted by the two processes to be extracted.

(Additional remark 6) It memorize | stored in the memory | storage part which memorize | stored the communication history which matched the request data transmitted from the said web browser to the web server, and the response data received from the said web server about operation which a computer performs by a web browser Based on the communication history, extract the communication history associated with the response data in which information used for session management exists,
Based on the communication history stored in the storage unit, a series of communications obtained by tracing information that is included in the request data and that is used to manage screen transitions output on the web browser side Extract the history,
A relay method, wherein each process for reproducing the operation is executed using a union of communication histories extracted by the two processes to be extracted.

DESCRIPTION OF SYMBOLS 1, 1A relay apparatus 2 Web browser 3 Web server 9 Web relay system 10 Control part 11 Memory | storage part 12 Proxy part 13 Communication extraction part 14 Communication reproduction part 111 Communication recording table 121 Request recording part 122 Request transmission part 123 Response transmission part 124 Response Recording unit 131 Authentication state extraction unit 132 Screen transition extraction unit 133, 133A Reproduction extraction unit

Claims (4)

For operations performed by the web browser, a storage unit storing a communication history in which request data transmitted from the web browser to the web server and response data received from the web server are associated with each other;
A first extraction unit for extracting a communication history associated with the response data in which information used for session management exists based on the communication history stored in the storage unit;
Based on the communication history stored in the storage unit, a series of communications obtained by tracing information that is included in the request data and that is used to manage screen transitions output on the web browser side A second extraction unit for extracting a history;
And a reproduction unit that reproduces the operation using a union of the communication history extracted by the first extraction unit and the communication history extracted by the second extraction unit. From the communication history extracted by the second extraction unit, delete the communication history associated with the response data in which information used when configuring a small screen in the screen exists, and remove the deleted communication history A third extraction unit for extracting the communication history
The reproduction unit is
The relay apparatus according to claim 1, wherein the operation is reproduced using a union of the communication history extracted by the first extraction unit and the communication history extracted by the third extraction unit. . On the computer,
For operations performed by the web browser, based on the communication history stored in the storage unit storing the communication history in which the request data transmitted from the web browser to the web server and the response data received from the web server are associated with each other. Extracting a communication history associated with the response data in which information used for session management exists,
Based on the communication history stored in the storage unit, a series of communications obtained by tracing information that is included in the request data and that is used to manage screen transitions output on the web browser side Extract the history,
A relay program that executes a process of reproducing the operation using a union of communication histories extracted by the two processes to be extracted. Based on the communication history stored in the storage unit storing the communication history in which the request data transmitted from the web browser to the web server and the response data received from the web server are associated with the operation performed by the web browser by the computer. A communication history associated with the response data in which information used for session management exists,
Based on the communication history stored in the storage unit, a series of communications obtained by tracing information that is included in the request data and that is used to manage screen transitions output on the web browser side Extract the history,
A relay method, wherein each process for reproducing the operation is executed using a union of communication histories extracted by the two processes to be extracted.

Images