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

Description

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

  In recent years, there is a demand for a technique for improving user operation efficiency when using web services in business.

  For example, as a technique for improving user operation efficiency, there is a technique of a relay device that relays communication between a browser indicating a user terminal and a web server. Such a relay device stores the request data transmitted to the web server, the response data received from the web server, and the processing identification information in association with each other in the storage device. Then, the relay device refers to the storage device, and among the parameters included in the two request data having the same processing identification information, the values in the two request data are different and are not included in the immediately preceding response data. Extract parameters and generalize them so that they can be entered. Then, the relay device accepts an input of a value for a generalized parameter at the time of reproduction, and transmits request data in which the value of the accepted input is set to the extracted parameter value to the web server. As a result, the relay device sequentially generates a series of requests and transmits them to the web server without using the user as much as possible, thereby improving the operation efficiency of the user (for example, Patent Document 1). The generalized parameters include authentication information such as a user ID (identification) and a password, for example.

JP 2012-074001 A JP 2004-287929 A JP 2008-117093 A

  By the way, there is a web application (hereinafter referred to as a cooperative web application) that is used in cooperation by a plurality of users. In such a collaborative web application, a process in which the operation is restricted by the user can be performed. For example, in a reservation of a conference room, a process that restricts a reservation cancellation operation can be performed only by a user who has reserved the room, and in a paperwork, a process that restricts a draft approval operation can be performed only by a manager. Therefore, when reproducing the operation in the cooperative web application, authentication information of a plurality of users related to the reproduction may be required.

  In such a cooperative web application, there is a problem that security is not ensured when authentication information of a plurality of users is sent from the same user terminal to the relay device when the operation is reproduced. For example, when the reproduction is performed from the user terminal of the user A who performs the reproduction, the authentication information of the user B related to the reproduction is passed to the user terminal of the user A, so the user A is not permitted even when the user B is not present. It can be reproduced using the authentication information of user B. As a result, security is not ensured.

  In one aspect, an object is to reproduce an operation of a cooperative web application in consideration of security.

  A relay method disclosed in the present application is a relay method in which a relay device relays communication between a client terminal and a web server that executes a web application, and the request data transmitted from the client terminal to the web server Response data received from the web server is recorded in the storage device, and switching information that is information on request data to be processed after the communication destination client is switched is recorded in the storage device and recorded in the storage device. Based on the switching information, the communication destination client terminal is switched to reproduce the request data and response data recorded in the storage device.

  According to one aspect of the relay method disclosed in the present application, it is possible to reproduce an operation for a cooperative web application in consideration of security.

FIG. 1 is a functional block diagram illustrating the configuration of the web relay device according to the embodiment. FIG. 2 is a diagram illustrating an example of a data structure of the communication record table. FIG. 3 is a diagram illustrating an example of a data structure of the authority switching record table. FIG. 4 is a diagram illustrating an example of a script related to the authority switching start notification and the authentication notification. FIG. 5 is a diagram illustrating an example of a script related to the authority switching end notification. FIG. 6 is a diagram illustrating an example of the data structure of the general-purpose processing table. FIG. 7 is a diagram for explaining a specific example of the communication recording process. FIG. 8A is a diagram (1) illustrating the transition between the communication record table and the authority switching record table. FIG. 8B is a diagram (2) for explaining the transition between the communication record table and the authority switching record table. FIG. 8C is a diagram (3) illustrating the transition between the communication record table and the authority switching record table. FIG. 8D is a diagram (4) illustrating the transition between the communication record table and the authority switching record table. FIG. 9 is a diagram for explaining a specific example of the reproduction process. FIG. 10 is a diagram illustrating an example of a reproduction request screen. FIG. 11 is a diagram for explaining a method for acquiring authentication information for authority switching. FIG. 12 is a diagram illustrating an example of a proxy execution input support screen. FIG. 13 is a diagram illustrating a flowchart of processing by the script insertion unit. FIG. 14 is a diagram illustrating a flowchart of processing by the authority switching recording unit. FIG. 15 is a diagram illustrating a flowchart of processing by the authority switching record calling unit. FIG. 16 is a diagram illustrating a flowchart of processing by the token issuing unit. FIG. 17 is a diagram illustrating a flowchart of processing by the authority switching reproduction unit. FIG. 18 is a diagram illustrating a computer that executes a relay program.

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

[Web relay system configuration]
FIG. 1 is a functional block diagram illustrating the configuration of the relay device according to the embodiment. As shown in FIG. 1, the web relay system 9 includes a relay device 1, terminals 2 </ b> A and 2 </ b> B, and a web server 3. The relay device 1 relays communication between the terminals 2A and 2B and the web server 3. The terminals 2A and 2B are client terminals such as personal computers that use web services. The web server 3 deploys a web application 41 that executes a web service. Here, the web application 41 is a web application used in cooperation by a plurality of users, for example, an application related to conference room reservation. Here, the web application 41 used in cooperation by a plurality of users is referred to as a “cooperative web application”. In the web relay system 9, the web server 3 may be applied to the same network as the relay device 1 and the terminals 2A and 2B, or the web server 3 is applied to a different network as an external device. It may be.

  Here, the cooperative web application will be described. In the cooperation-side web application, since a plurality of users cooperate and use, access restriction is provided for operations by the users. For example, in a collaborative web application related to conference room reservation, only the user who reserved the conference room can cancel the reservation, so even if another user wants to use the conference room that has already been reserved, Cannot operate. Therefore, when the relay device 1 according to the embodiment urgently uses a conference room reserved by another user, the relay device 1 switches the process from the user's terminal to the user's terminal that reserved the conference room for authentication. It is possible to acquire information. In the following, a cooperative web application relating to conference room reservation will be described as an example.

  The relay device 1 includes a communication recording process for recording the communication from the communication destination terminal 2A and a reproduction process for reproducing the recorded communication. In the communication recording process, the relay device 1 records request data transmitted from the communication destination terminal 2A to the web server 3 and response data received from the web server 3 in a communication recording table 31 described later. At the same time, the relay device 1 records the timing at which the communication destination authority needs to be switched as request authority data in the authority switching record table 32 to be described later. Further, in the reproduction process, the relay device 1 causes the communication destination terminal 2 </ b> A to switch the communication destination at a timing when the authority needs to be switched based on the authority switching information recorded in the authority switching recording table 32. And the relay apparatus 1 receives the authentication information of the said communication destination from the switched communication destination. The authentication information is, for example, a user ID and a password. Then, after authenticating using the authentication information, the relay device 1 reproduces the request data recorded in the communication record table 31 with the authority switched.

  The relay device 1 includes a control unit 10, a terminal communication unit 11, and an external service communication unit 12. In addition, the relay device 1 includes a communication recording table 31, an authority switching recording table 32, a general-purpose processing table 33, and a token management table 34.

  The terminal communication unit 11 is a communication interface with the terminal. The external service communication unit 12 is a communication interface with an external service, for example, a web application 41 deployed in the web server 3.

  The control unit 10 includes a communication recording unit 13, a script insertion unit 14, an authority switching recording unit 15, and a generalization unit 16. In addition, the control unit 10 includes a communication record calling unit 17, a recording reproduction unit 18, an authority switching recording calling unit 19, a token issuing unit 20, an authority switching reproduction unit 21, and a token discarding unit 22. 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 communication recording unit 13 sequentially records the request data transmitted from the terminal 2 </ b> A to the web server 3 in the communication recording table 31 for each series of operations of the cooperative web application. Then, the communication recording unit 13 transmits the request data transmitted from the terminal 2 </ b> A to the web server 3. Further, the communication recording unit 13 sequentially records the response data transmitted from the web server 3 in the communication recording table 31 in association with the request data. And the communication recording part 13 transmits the response data by which the script was inserted in the response data transmitted from the web server 3 to the terminal 2A. The script is inserted into the response data by the script insertion unit 14 described later.

  Here, the data structure of the communication record table 31 will be described with reference to FIG. FIG. 2 is a diagram illustrating an example of a data structure of the communication record table. As shown in FIG. 2, the communication record table 31 stores a record number 31a, request data 31b, and response data 31c in association with each other as a communication record. The recording number 31a is a number assigned in the order in which the associated request data 31b and response data 31c are recorded, and is assigned in ascending order. The request data 31b is data requested from the terminal 2A to the web server 3. The response data 31c is data returned from the web server 3 and corresponds to the request data 31b. As an example, when the recording number 31a is “2”, “GET login.cgi? Uid = user1 & pass = user1 HTTP / 1.0” as the request data 31b and “HTTP / 1.0 200 OK <html> Conference Room List” as the response data 31c "

  Returning to FIG. 1, upon receiving the response data, the script insertion unit 14 refers to the authority switching recording table 32 that records the authority switching information, determines whether authority is being switched, and responds to the determination result. Insert script into response data. Here, the data structure of the authority switching record table 32 will be described with reference to FIG. FIG. 3 is a diagram illustrating an example of a data structure of the authority switching record table.

  As shown in FIG. 3, the authority switching record table 32 stores authority switching number 32a, authentication 32b, authority switching start 32c, and authority switching end 32d in association with each other as authority switching information. The authority switching number 32a indicates an identification number for a series of operations with authority switching, and is given in ascending order as an example. The authentication 32b stores a recording number indicating request data for authentication. The authority switching start 32c indicates the recording number of the start of request data processed after the authority is switched. The authority switching end 32d indicates the recording number of the end of request data processed after the authority is switched. As an example, when the authority switching number 32a is “1”, “2” is stored as the authentication 32b, “3” is stored as the authority switching start 32c, and “3” is stored as the authority switching end 32d.

  Returning to FIG. 1, for example, when receiving the response data, the script insertion unit 14 acquires authority switching information having the latest authority switching number 32 a from the authority switching information recorded in the authority switching recording table 32. If the acquisition is not possible, the script insertion unit 14 determines that the authority is not being switched if the recording number is set in the authority switching end 32d of the acquired authority switching information. Further, even if the script insertion unit 14 is able to obtain the authorization switching information, if the recording number is set in the authorization switching information authentication 32b and the recording number is not set in the authorization switching start 32c and the authorization switching end 32d, the script insertion unit 14 Judge that it is not switching. On the other hand, for the acquired authority switching information, the script insertion unit 14 determines that the authority is being switched when the recording number is set in the authority switching start 32c and the recording number is not set in the authority switching end 32d. . Then, the script insertion unit 14 inserts, into the response data, a script (a script related to the authority switching start notification) for notifying the terminal 2A of the authority switching start timing when authority switching is not being performed. The script insertion unit 14 inserts, into the response data, a script (a script related to authentication notification) for notifying the terminal 2A of the timing of authentication when the authority is not being switched. In addition, when the authority is being switched, the script insertion unit 14 inserts a script (a script related to the authority switching end notification) for notifying the terminal 2A of the timing of the authority switching end in the response data.

  Here, an example of the script related to the authority switching start notification and the authentication notification and the script related to the authority switching end notification will be described with reference to FIGS. 4 and 5. FIG. 4 is a diagram illustrating an example of a script related to the authority switching start notification and the authentication notification. FIG. 5 is a diagram illustrating an example of a script related to the authority switching end notification.

  FIG. 4 shows a script related to the authority switching start notification and the authentication notification. The portion of the script related to the authority switching start notification is indicated by reference numeral f1. Here, it is shown that when the F8 key whose key code is “119” is pressed, a command for notifying the timing of authentication is issued. That is, when the F8 key is pressed, the terminal 2A notifies the relay device 1 that it is the timing of authentication. Further, the part of the script related to the authority switching start notification is indicated by reference numeral f2. Here, it is shown that when the F9 key whose key code is “120” is pressed, a command is issued to notify that it is the timing for starting authority switching. That is, when the F9 key is pressed, the terminal 2A notifies the relay device 1 that it is the timing for starting the authority switching. As indicated by reference numeral f3, an alert may be given to notify the user that pressing of the F8 key is an authentication notification and pressing of the F9 key is an authority switching start notification. Here, a dialog screen is displayed.

  FIG. 5 shows a script related to the authority switching end notification. The portion of the script related to the authority switching end notification is indicated by reference numeral f4. Here, it is shown that when the F8 key whose key code is “119” is pressed, a command is issued to notify that it is the timing of the end of authority switching. In other words, when the F8 key is pressed, the terminal 2A notifies the relay apparatus 1 that it is the timing of the end of the authority switching. Note that, as indicated by reference numeral f5, an alert for notifying the user that pressing of the F8 key is an authority switching end notification may be given. Here, a dialog screen is displayed.

  The authority switching recording unit 15 updates the authority switching information according to the notification transmitted from the script of the terminal 2A. For example, the authority switching recording unit 15 acquires the notification content from the terminal 2A. Further, when the notification content is “authentication notification”, the authority switching recording unit 15 adds new authority switching information, and sets the authority switching number 32a to the latest number. Then, the authority switching recording unit 15 sets the next number of the latest recording number in the communication record information recorded in the communication record table 31 as the authentication number in the authentication 32b. That is, when the notification content is “authentication notification”, the authority switching recording unit 15 determines that the next operation (request data) is authentication. Further, when the notification content is “authorization switching start”, the authority switching recording unit 15 sets the next number of the latest recording number in the communication record information as the authority switching start number in the authority switching start 32c. That is, the authority switching recording unit 15 determines that the next operation (request data) is the first operation performed with another authority when the notification content is “start authority switching”. Further, when the notification content is “authorization switching end”, the authority switching recording unit 15 sets the latest recording number in the communication record information as the authority switching end number in the authority switching end 32d. That is, the authority switching recording unit 15 determines that the latest operation (request data) is the last operation performed with another authority when the notification content is “authorization switching end”.

  The generalization unit 16 generates request data so as to generalize a series of operations of the cooperative web application. For example, it is assumed that an operation record of a series of operations of the cooperative web application is recorded in the communication record table 31 a plurality of times by the communication recording unit 13 in advance. The generalization unit 16 refers to the communication record recorded in the communication record table 31, and among the parameters included in the two request data of the same operation, the values in the two request data are different and the immediately preceding response data Extract parameters not included in. And the generalization part 16 produces | generates the request data which replaced the value of the extracted parameter with the variable, for example as generalized request data. Then, the generalization unit 16 records the generated request data in the general-purpose processing table 33.

  Here, the data structure of the general-purpose processing table 33 will be described with reference to FIG. FIG. 6 is a diagram illustrating an example of the data structure of the general-purpose processing table. As shown in FIG. 6, the general-purpose processing table 33 stores a communication number 33a and request data 33b in association with each other. The communication number 33 a is a number assigned in the order in which the request data 33 b is recorded, and corresponds to the recording number 31 a of the communication recording table 31. The request data 33 b is request data that is generalized general-purpose processing, and corresponds to the request data 31 b of the communication recording table 31. Note that “uid” and “pass” in the request data 33b are parameters indicating a user ID and a password, respectively. “Rid” and “reason” in the request data are parameters indicating a room number and a purpose, respectively.

  For example, when the communication number 33a is “2”, the request data 33b includes a user ID and a password. That is, the request data 33b is a process in which the value of the parameter “uid” is replaced with the variable “%%” and the value of the parameter “pass” is replaced with the variable “%%”. When the communication number 33a is “3”, the request data 33b includes a room number. That is, the request data 33b is a process in which the value of the parameter “rid” is replaced with the variable “%%”. When the communication number 33a is “4”, the request data 33b includes a room number and a purpose. That is, the request data 33b is a process in which the value of the parameter “rid” is replaced with the variable “%%” and the value of the parameter “reason” is replaced with the variable “%%”.

  When receiving the reproduction request from the terminal 2A, the communication record calling unit 17 calls the request data corresponding to the reproduction request from the general-purpose processing table 33 in order. The request data here indicates generalized request data. In addition, the reproduction request here includes a specific value of a parameter whose value is made variable by generalization. The communication record calling unit 17 embeds a specific value in a location that is a parameter of the called request data, and generates request data to be reproduced. The reproduction request may be executed from, for example, a reproduction request screen installed in advance on the terminal 2A.

  The recording reproduction unit 18 transmits the request data to be reproduced, which is generated by the communication record calling unit 17, to the web server 3 until the authority switching is started. Whether authority switching has been started is determined by the authority switching record calling unit 19 described later.

  The authority switching record calling unit 19 calls the corresponding authority switching information from the authority switching recording table 32. Then, the authority switching record calling unit 19 refers to the authority switching information and determines whether or not the request data to be reproduced is the timing when authority switching is started. For example, the authority switching record calling unit 19 determines whether or not the communication number 33a of the request data to be reproduced matches the authority switching start 32c number recorded in the authority switching recording table 32. Here, if it is determined that they match, the authority switching record calling unit 19 determines that it is the timing when authority switching has started. On the other hand, if the authority switching record calling unit 19 determines that they do not match, it determines that it is not the timing when authority switching has started.

  The token issuing unit 20 issues a token and notifies the terminal 2A of the issued token when it is time to start authority switching. Thereby, the token issuing unit 20 causes the terminal 2A to switch the communication destination using the issued token. For example, the token issuing unit 20 issues a token having an identifier that is unique in the system when it is determined that the request data reproduced by the authority switching recording / calling unit 19 is the timing when authority switching is started. The token issuing unit 20 records the issued token identifier in the token management table 34 in association with the number indicated by the authority switching number 32a of the authority switching information. The token identifier may be a character string, a number, or an image, and may be unique within the system. Then, the token issuing unit 20 notifies the token to the communication destination terminal 2A.

  The authority switching reproduction unit 21 reproduces communication records related to authority switching using the token and the authentication information. For example, when the authority switching reproduction unit 21 receives the token and authentication information related to authority switching from the switched communication destination, the authority switching reproduction unit 21 determines whether or not the received token identifier is recorded in the token management table 34. The authentication information includes the user ID and password of the switched communication destination. Then, if the received token identifier is recorded in the token management table 34, the authority switching reproduction unit 21 embeds the received authentication information in the request data related to authentication and generates request data to be reproduced. The request data related to the authentication here indicates generalized request data corresponding to the number indicated by the authentication switching information authentication 32b. Then, the recording reproduction unit 18 transmits the request data to be reproduced, that is, request data related to authentication to the web server 3. Thereby, the authority is switched to the switched communication destination.

  Further, the authority switching reproduction unit 21 reproduces communication records from the start of authority switching to the end thereof. For example, the recording reproduction unit 18 transmits to the web server 3 request data to be reproduced from the number indicated by the authority switching start 32c of the authority switching information to the number indicated by the authority switching end 32d.

  The token discarding unit 22 discards the token when the authority switching ends. For example, when the communication number of the request data to be reproduced is the number indicated by the authority switching end 32d of the authority switching information, the token discarding unit 22 deletes the token information recorded in the token management table 34.

[Specific example of communication record processing]
Next, a specific example of the communication recording process will be described with reference to FIGS. 7 and 8A to 8D. FIG. 7 is a diagram for explaining a specific example of the communication recording process. 8A to 8D are diagrams for explaining the transition between the communication record table and the authority switching record table. As shown in FIG. 7, the numbers in parentheses of the request and response indicate communication numbers. The script (a) indicates a script (see FIG. 4) related to the authority switching start notification and the authentication notification, and the script (b) indicates a script (refer to FIG. 5) related to the authority switching end notification. It is assumed that no data has been recorded in the communication record table 31 and the authority switching record table 32 yet.

  Request data (1) whose communication number (record number) is “1” is transmitted from the terminal 2A (S11).

  In the relay device 1, the communication recording unit 13 records the request data (1) and the response data (1) in the communication recording table 31 (S12). Here, it is assumed that the request data (1) is “GET / index.cgi HTTP / 1.0” and the response data (1) is “HTTP / 1.0 200 OK <html> login”. The upper part of FIG. 8A shows the contents of the communication record in the communication record table 31.

  Then, the script insertion unit 14 refers to the authority switching recording table 32 and determines whether authority is being switched. Here, the script insertion unit 14 determines that the authority is not being switched because no data is recorded in the authority switching recording table 32. Then, the script insertion unit 14 responds with the script (a) related to the authentication notification for notifying the terminal 2A of the authentication timing and the authority switching start notification for notifying the terminal 2A of the authority switching start timing. It inserts into data (1) (S13). And the communication recording part 13 transmits the response data (1) in which the script was inserted to the terminal 2A (S14).

  In the terminal 2A, a login screen for prompting authentication is displayed according to the response data (1). When the F8 key is pressed (S15), the terminal 2A notifies the relay device 1 that it is the timing of authentication. The request when the F8 key is pressed is, for example, “GET / delegate.cgi? Action = auth” as indicated by reference numeral f1 in FIG.

  In the relay device 1, the authority switching recording unit 15 determines that the next request data is authentication because the notification content is “authentication notification”. Then, the authority switching recording unit 15 generates new authority switching information, sets “1” in the authority switching number 32a, and records the next number “2” of the latest recording number in the authentication 32b (S16). . The lower part of FIG. 8A shows the contents of the authority switching information in the authority switching recording table 32.

  In the terminal 2A, request data (2) whose communication number (record number) is “2” is transmitted from the login screen (S17). The request data (2) is a request for prompting authentication with the input user ID and password.

  In the relay device 1, the communication recording unit 13 records the request data (2) and the response data (2) in the communication recording table 31 (S18). Here, the request data (2) is “GET login.cgi? Uid = user1 & pass = user1 HTTP / 1.0”, and the response data (2) is “HTTP / 1.0 200 OK <html> Conference room list”. And The upper part of FIG. 8B shows the contents of the communication record in the communication record table 31.

  Then, the script insertion unit 14 refers to the authority switching recording table 32 and determines whether authority is being switched. Here, the script insertion unit 14 determines that the authority is not being switched because the recording number is set in the authentication 32b of the authority switching recording table 32 and the recording number is not set in the authority switching start 32c and the authority switching end 32c. To do. Then, the script insertion unit 14 responds with a script (a) relating to an authentication notification for notifying the terminal 2A that it is an authentication timing or an authority switching start notification for notifying the terminal 2A that it is an authority switching start timing. It inserts into data (2) (S19). And the communication recording part 13 transmits the response data (2) in which the script was inserted to the terminal 2A (S20).

  In the terminal 2A, a conference room list screen is displayed according to the response data (2). When the F9 key is pressed (S21), the terminal 2A notifies the relay device 1 that it is the timing for starting the authority switching. The request when the F9 key is pressed is, for example, “GET / delegate.cgi? Action = start”, as indicated by reference numeral f2 in FIG.

  In the relay device 1, the authority switching recording unit 15 determines that the next request data is an operation performed with another authority because the notification content is “start authority switching”. Then, the authority switching recording unit 15 records the next number “3” of the latest recording number in the authority switching start 32c of the authority switching information (S22A). The lower part of FIG. 8B shows the contents of authority switching information in the authority switching recording table 32.

  In the terminal 2A, when the cancel key is pressed on the conference room list screen, the request data (3) whose communication number (record number) is “3” is transmitted (S22). The request data (3) is a request for canceling the reservation of the room number “101”.

  In the relay device 1, the communication recording unit 13 records the request data (3) and the response data (3) in the communication recording table 31 (S23). Here, it is assumed that the request data (3) is “GET cancel.cgi? Rid = 101 HTTP / 1.0” and the response data (3) is “HTTP / 1.0 200 OK <html> success”. The upper part of FIG. 8C shows the contents of the communication record in the communication record table 31.

  Then, the script insertion unit 14 refers to the authority switching recording table 32 and determines whether authority is being switched. Here, the script insertion unit 14 determines that the authority is being switched because the recording number is set in the authority switching start 32c of the authority switching recording table 32 and the recording number is not set in the authority switching end 32d. Then, the script insertion unit 14 inserts the script (b) including the authority switching end notification for notifying the terminal 2A of the authority switching end timing into the HTML of the response data (3) (S24). And the communication recording part 13 transmits the response data (3) in which the script was inserted to the terminal 2A (S25).

  In the terminal 2A, the conference room list screen is displayed as it is according to the response data (3). Then, when the F8 key is pressed (S26), the terminal 2A notifies the relay device 1 that it is the timing of the end of the authority switching. The request when the F8 key is pressed is, for example, “GET / delegate_end.cgi” as indicated by reference numeral f4 in FIG.

  In the relay device 1, the authority switching recording unit 15 determines that the latest request data (3) is the last operation performed with another authority because the notification content is “authorization switching end”. The authority switching recording unit 15 records the latest recording number “3” in the authority switching end 32d of the authority switching information (S27). The lower part of FIG. 8C shows the contents of authority switching information in the authority switching recording table 32.

  Thereafter, in the terminal 2A, when the reservation key is pressed on the conference room list screen, the request data (4) whose communication number (record number) is “4” is transmitted (S28). The request data (4) is a request for reserving the room number “101”. In this request, “important meeting” is set as the purpose.

  In the relay device 1, the communication recording unit 13 records the request data (4) and the response data (4) in the communication recording table 31 (S29). Here, the request data (4) is “GET reserve.cgi? Rid = 101 & reason =” important meeting ”HTTP / 1.0”, and the response data (4) is “HTTP / 1.0 200 OK <html> success”. Suppose there is. FIG. 8D shows the contents of the communication record in the communication record table 31.

  Then, the script insertion unit 14 refers to the authority switching recording table 32 and determines whether authority is being switched. Here, the script insertion unit 14 determines that the authority is not being switched because the recording number is set in the authority switching end 32d of the authority switching recording table 32. Then, the script insertion unit 14 responds with the script (a) related to the authentication notification for notifying the terminal 2A of the authentication timing and the authority switching start notification for notifying the terminal 2A of the authority switching start timing. It inserts into data (4) (S30). And the communication recording part 13 transmits the response data (4) in which the script was inserted to the terminal 2A (S31).

  In this way, the communication recording process of the cooperative web application related to the conference room reservation is performed, and the communication recording table 31 and the authority switching recording table 32 are generated.

[Specific examples of reproduction processing]
Next, a specific example of the reproduction process will be described with reference to FIG. FIG. 9 is a diagram for explaining a specific example of the reproduction process. In this specific example, “the user 1 of the terminal 2A reserves the room number 101 that has already been reserved by the user 2 for the purpose of an important meeting” is reproduced.

  As shown in FIG. 9, the communication record and authority switching information recorded by the communication record process are shown. The upper part of FIG. 9 shows the contents of the communication record in the communication record table 31. The lower part of FIG. 9 shows the contents of the authority switching information in the authority switching recording table 32.

  The generalization unit 16 refers to the communication record recorded in the communication record table 31 and generalizes a series of operations, in this case, operations from record numbers 1 to 4. As a result, the general-purpose processing table 33 shown in FIG. 6 is generated.

When receiving the reproduction request from the terminal 2A, the communication record calling unit 17 calls the request data corresponding to the reproduction request from the general-purpose processing table 33. Then, the communication record calling unit 17 embeds a specific value in a location that is set as a parameter of the called request data, and generates request data to be reproduced. Here, a parameter “uid” indicating a user ID, a parameter “pass” indicating a password, a parameter “rid” indicating a room number, and a parameter [reason] indicating a reason are variables. The request when the reproduction request is made is, for example, “start.cgi? Uid = XXX & pass = XXX & rid = XXX & reason = XXX HTTP / 1.0”. Assume that the user ID of user 1 is “user1”, the password is “user1”, the room number is “101”, and the purpose is “important meeting”. Then, a specific request for the reproduction request is as follows, for example.
“Start.cgi? Uid = user1 & pass = user1 & rid = 101 & reason = Important Conference HTTP / 1.0”

  The reproduction request may be executed from a reproduction execution screen installed in advance on the terminal 2A. FIG. 10 is a diagram illustrating an example of a reproduction request screen. As shown in FIG. 10, “ID”, “password”, “room number”, and “purpose” are represented as titles. “ID” corresponds to the user ID of the parameter. “Password” corresponds to a parameter password. The “room number” corresponds to the parameter room number. “Purpose” corresponds to the purpose of the parameter. The t0 portion is an area for inputting specific contents for each parameter. Then, when the execution button is pressed, a reproduction request is made.

  When a reproduction request is made from the terminal 2A, the authority switching record calling unit 19 determines whether the communication number of the request data to be reproduced matches the number of the authority switching start 32c recorded in the authority switching recording table 32. Determine whether. Here, the number of the authority switching start 32c is “3”.

  For the communication numbers 1 and 2, the authority switching record calling unit 19 determines that the communication number of the request data to be reproduced does not match the number of the authority switching start 32c. That is, the authority switching record calling unit 19 determines that the request data to be reproduced is not the timing when authority switching is started. Accordingly, the recording reproduction unit 18 transmits the request data to be reproduced to the web server 3 in order for the communication numbers 1 and 2.

  For the communication number 3, the authority switching record calling unit 19 determines that the communication number of the request data to be reproduced matches the number of the authority switching start 32c. That is, the authority switching record calling unit 19 determines that the request data to be reproduced is the timing when authority switching is started. Therefore, the token issuing unit 20 issues a token, notifies the issued token to the terminal 2A, and switches the communication destination. Here, it is assumed that the identifier of the issued token is “abcde”.

  Then, the authority switching reproduction unit 21 receives a request including a token and authentication information from the switched terminal 2B. A specific example of a request including a token and authentication information will be described later.

  Then, if the received token is “abcde”, the authority switching reproduction unit 21 embeds the received authentication information in the request data related to authentication because it matches the token issued by the token issuing unit 20. . Then, the authority switching reproduction unit 21 generates request data to be reproduced. Here, the request data related to authentication is generalized request data corresponding to the number “2” of the authentication 32 b recorded in the authority switching recording table 32. The reproduced request data is “GET login.cgi? Uid = user2 pass = user2 HTTP / 1.0”. The authority switching reproduction unit 21 transmits the request data to be reproduced to the web server 3. Thereby, the authority is switched to the user 2.

  Then, the authority switching reproduction unit 21 reproduces communication records from the start of authority switching to the end thereof. Here, the authority switching reproduction unit 21 reproduces from the authority switching start number 32c “3” to the authority switching end 32d number “3” based on the authority record information recorded in the authority switching record table 32. Request data is transmitted to the web server 3. The reproduced request data is “GET cancel.cgi? Rid = 101 HTTP / 1.0”. Thereby, the authority switching reproduction unit 21 can cancel the room number “101” with the authority switched to the user 2.

  Thereafter, the authority switching reproduction unit 21 returns the authority to the original user 1. The reproduced request data is “GET login.cgi? Uid = user1 pass = user1 HTTP / 1.0”. The authority switching reproduction unit 21 transmits the request data to be reproduced to the web server 3. Thereby, the authority is returned to the user 1.

  For the communication number 4, since the communication number 4 of the request data to be reproduced by the authority switching record calling unit 19 does not match the number “3” of the authority switching start 32c, the request data to be reproduced performs authority switching. It is determined that it is not the start timing. Therefore, the recording reproduction unit 18 transmits the request data to be reproduced for the communication number 4 to the web server 3. Thereby, the user 1 of the terminal 2A can reserve the room number 101.

  Here, a method for acquiring authentication information for authority switching will be described with reference to FIG. FIG. 11 is a diagram for explaining a method for acquiring authentication information for authority switching. In FIG. 11, the terminal A transmits a reproduction request to the relay apparatus 1 using HTTP (HyperText Transfer Protocol).

  As illustrated in FIG. 11, the token issuing unit 20 of the relay device 1 transmits a token (identifier: “abcde”) to the terminal A using a method different from HTTP. For example, the token issuing unit 20 can transmit to the terminal A using MMS (Multimedia Messaging Service).

  The application of the terminal A that has received the token notifies the partner terminal (terminal B) that the proxy execution is requested to request information for requesting the proxy execution including the received token. Here, for example, the application of the terminal can notify the information to the terminal (terminal B) of the partner who wants to request proxy execution using NFC (Near Field Communication) that enables near field communication.

The application of the terminal B that has received information requesting proxy execution including a token generates authentication information. Then, the application of the terminal B transmits a request including the token and the authentication information to the relay device 1. For example, a request including a token and authentication information is “delegate.cgi? Uid = XXX & pass = XXX & tokun = xxx”. If the user ID of the user 2 is “user2” and the password is “user2”, the specific request is as follows, for example.
“Delegate.cgi? Uid = user2 & pass = user2 & tokun = abcde”

  Upon receiving the request including the token and the authentication information, the authority switching reproduction unit 21 switches the authority using the received authentication information if the received token matches the token issued by the token issuing unit 20.

  Thereby, even if the specific room number is already reserved by the user 2, the relay device 1 can switch from the reserved user 2 terminal to the authority of the user 2 by the user 2. Therefore, the relay device 1 can reproduce the operation while ensuring security even in the case of a cooperative web application.

  Although the token issuing unit 20 of the relay device 1 transmits the token to the terminal A, the present invention is not limited to this. For example, the token issuing unit 20 may transmit a proxy execution input support screen including token information. FIG. 12 is a diagram illustrating an example of a proxy execution input support screen. As shown in FIG. 12, “uid” and “pass” are represented as titles. “Uid” corresponds to a user ID. “Pass” corresponds to a password. “Token” corresponds to token information, and a token identifier “abcde” is displayed. And t1 part becomes an area | region which inputs the specific content with respect to each parameter. In the terminal B, when the transmission button is pressed, a request including a token and authentication information is transmitted to the relay device 1.

[Processing procedure by script insertion part]
Next, the processing procedure by the script insertion unit 14 will be described with reference to FIG. FIG. 13 is a diagram illustrating a flowchart of processing by the script insertion unit. In the communication recording process, it is assumed that the script insertion unit 14 has received response data corresponding to the request data.

  The script insertion unit 14 acquires authority switching information having the latest authority switching number 32a from the authority switching information recorded in the authority switching recording table 32 (step S101). Then, the script insertion unit 14 refers to the acquired authority switching information and determines whether the authority is being switched (step S102). For example, the script insertion unit 14 determines whether or not a recording number is set for the authentication 32b, the authority switching start 32c, or the authority switching end 32d of the acquired latest authority switching information.

  When it is determined that the authority is not being switched (step S102; No), the script insertion unit 14 inserts a script related to the authority switching start notification and the authentication notification into the response data (step S103). When the authority is not being switched, for example, when a recording number is set in the authority switching end 32d, a recording number is set in the authentication 32b, and a recording number is set in the authority switching start 32c and the authority switching end 32d. If not, the number of rows is 0.

  On the other hand, if it is determined that the authority is being switched (step S102; Yes), the script insertion unit 14 inserts a script related to the authority switching end notification into the response data (step S104). The case where the authority is being switched is, for example, the case where the recording number is set in the authority switching start 32c and the recording number is not set in the authority switching end 32d.

  In this manner, the script insertion unit 14 inserts a script for notifying the terminal 2A of the predetermined timing in the received response data.

[Processing procedure by authority switching recording unit]
Next, the processing procedure by the authority switching recording unit 15 will be described with reference to FIG. FIG. 14 is a diagram illustrating a flowchart of processing by the authority switching recording unit. It is assumed that predetermined notification contents are transmitted from the script of the terminal 2A.

  The authority switching recording unit 15 acquires the notification content from the terminal 2A (step S111). Then, the authority switching recording unit 15 acquires the latest record number from the communication record information recorded in the communication record table 31 (step S112). Here, the latest recording number is m.

  Subsequently, the authority switching recording unit 15 determines whether or not the acquired notification content is “authentication notification” (step S113). When it is determined that the notification content is “authentication notification” (step S113; Yes), the authority switching recording unit 15 adds new authority switching information and sets the latest authority switching number (step S114). Then, the authority switching recording unit 15 sets the number m + 1 as the authentication number in the authentication 32b (step S115). That is, the authority switching recording unit 15 determines that the next operation (request data) is authentication.

  On the other hand, when it is determined that the notification content is not “authentication notification” (step S113; No), the authority switching recording unit 15 determines whether the notification content is “authority switching start” (step S116). When it is determined that the notification content is “authority switching start” (step S116; Yes), the authority switching recording unit 15 sets the number m + 1 as the authority switching start number in the authority switching start 32c (step S117). That is, the authority switching recording unit 15 determines that the next operation (request data) is the first operation performed with another authority.

  On the other hand, when it is determined that the notification content is not “authority switching start” (step S116; No), the authority switching recording unit 15 determines whether the notification content is “authority switching end” (step S118). When it is determined that the notification content is “authorization switching end” (step S118; Yes), the authority switching recording unit 15 sets the number m as the authority switching end number in the authority switching end 32d (step S119). That is, the authority switching recording unit 15 determines that the latest operation (request data) is the last operation performed with another authority.

  On the other hand, when it is determined that the notification content is not “end of authority switching” (step S118; No), the authority switching recording unit 15 returns an error to the terminal 2A of the transmission source (step S120).

  In this manner, the authority switching recording unit 15 generates authority switching information recorded in the authority switching recording table 32 in accordance with the notification content from the terminal 2A.

[Processing procedure by the authority switching record calling unit]
Next, a processing procedure by the authority switching record calling unit 19 will be described with reference to FIG. FIG. 15 is a diagram illustrating a flowchart of processing by the authority switching record calling unit. In the reproduction process, the request data to be reproduced is reproduced in the order of the communication numbers recorded in the general-purpose processing table 33.

  The authority switching record calling unit 19 acquires the communication number 33a of the request data to be reproduced (step S131). Then, the authority switching record calling unit 19 confirms whether or not the acquired communication number 33a matches the authority start number 32c of the authority switching information recorded in the authority switching recording table 32 (step S132). Then, the authority switching record calling unit 19 determines whether the numbers match as a result of the confirmation (step S133).

  When it is determined that the numbers match (step S133; Yes), the authority switching record calling unit 19 notifies the token issuing unit 20 of the authority switching number 32a of the authority switching information and requests token issuance ( Step S134). On the other hand, if it is determined that the numbers do not match (step S133; No), the authority switching record calling unit 19 ends the process.

[Processing procedure by token issuing unit]
Next, the processing procedure by the token issuing unit 20 will be described with reference to FIG. FIG. 16 is a diagram illustrating a flowchart of processing by the token issuing unit. It is assumed that the authority switching record calling unit 19 notifies the authority switching number 32a and requests to issue a token.

  The token issuing unit 20 receives the authority switching number from the authority switching record calling unit 19 (step S141). Then, the token issuing unit 20 issues a token character string that is unique within the system (step S142). Then, the token issuing unit 20 records the token character string and the authority switching number 32a in association with each other in the token management table 34 (step S143).

  Then, the token issuing unit 20 notifies the issued token to the terminal 2A (step S144).

[Processing procedure by authority switching reproduction unit]
Next, a processing procedure by the authority switching reproduction unit 21 will be described with reference to FIG. FIG. 17 is a diagram illustrating a flowchart of processing by the authority switching reproduction unit. It is assumed that a request including a token and authentication information is transmitted from the switched terminal 2B. In the authentication information, the user ID and password of the switched communication destination are set.

  The authority switching reproduction unit 21 receives a request including a token and authentication information from the switched terminal 2B (step S151). Then, the authority switching reproduction unit 21 searches the token management table 34 for a corresponding token character string (step S152). As a result of the search, the authority switching reproduction unit 21 determines whether there is a corresponding token character string (step S153).

  When it is determined that there is no corresponding token character string (step S153; No), the authority switching reproduction unit 21 returns an error to the terminal 2B that is the transmission source of the request including the token (step S158).

  On the other hand, when it is determined that there is a corresponding token character string (step S153; Yes), the authority switching reproduction unit 21 acquires the authority switching number associated with the token character string from the token management table 34. Then, the authority switching reproduction unit 21 acquires authority switching information corresponding to the acquired authority switching number from the authority switching recording table 32 (step S154).

  Subsequently, the authority switching reproduction unit 21 reproduces communication corresponding to the authentication number of the authority switching information using the authentication information (step S155). For example, the authority switching reproduction unit 21 acquires the generalized request data 33 b corresponding to the number indicated by the authority switching information authentication 32 b from the general-purpose processing table 33. Then, the authority switching reproduction unit 21 embeds authentication information in the acquired request data and generates request data to be reproduced. Then, the authority switching reproduction unit 21 transmits the generated request data to the web server 3.

  Subsequently, the authority switching reproduction unit 21 reproduces communication from the authority switching start number to the authority switching end number of the authority switching information (step S156). For example, the authority switching reproduction unit 21 sequentially transmits to the web server 3 each request data to be reproduced from the number indicated by the authority switching start 32c of the authority switching information to the number indicated by the authority switching end 32d of the authority switching information. . The reproduced request data is request data in which specific contents are embedded in the generalized request data 33b corresponding to each number, and is performed by the communication record calling unit 17, for example.

  Then, the authority switching reproduction unit 21 requests the token discarding unit 22 to discard the token (Step S157). For example, the authority switching reproduction unit 21 deletes information corresponding to the corresponding token character string from the token management table 34.

[Effect of Example]
According to the above embodiment, the relay device 1 records the request data transmitted from the terminal 2 </ b> A to the web server 3 and the response data received from the web server 3 in the communication record table 31. Then, the relay device 1 records switching information, which is information about request data processed after the communication destination terminal is switched, in the authority switching recording table 32. Then, the relay device 1 switches the communication destination terminal based on the switching information recorded in the authority switching recording table 32 and reproduces the request data and response data recorded in the communication recording table 31. According to such a configuration, the relay device 1 switches the communication destination terminal based on the switching information recorded in advance. Therefore, even if the authentication information of a plurality of persons is not sent from the same terminal 2A, the cooperative web The operation related to the application can be reproduced. For example, when user B who is involved in reproduction passes his / her authentication information to terminal 2A of user A, user A is prevented from using authentication information of user B without permission even when user B is not present. it can. As a result, the relay device 1 can reproduce the operation related to the cooperative web application while ensuring security.

  Further, according to the above-described embodiment, the relay device 1 uses the identification number for starting switching and the identification number for switching end of request data processed after the communication destination terminal 2A is switched for the request data having the identification number. Recorded in the authority switching record table 32 as switching information. When receiving the reproduction request from the terminal 2A, the relay device 1 determines whether or not the identification number of the request data to be reproduced matches the switching start identification number recorded in the switching information. If the relay device 1 determines that they match, the relay device 1 causes the terminal 2A to switch the communication destination, and reproduces the request data according to authentication information related to switching from the switched communication destination. According to such a configuration, the relay device 1 can switch the communication destination to the terminal 2A and acquire authentication information related to the communication destination from the switched communication destination, so that the authority can be switched according to the authentication information. The request data can be reproduced with the switched authority. Therefore, the relay apparatus 1 can reproduce the operation related to the cooperative web application without sending authentication information of a plurality of persons from the same terminal 2A.

  Further, according to the above embodiment, the relay device 1 issues a token to the terminal 2A when it is determined that the request data identification number matches the switching start identification number recorded in the switching information. Then, the relay device 1 causes the terminal 2A to switch the communication destination using the issued token, and reproduces the request data according to authentication information related to switching from the switched communication destination. According to such a configuration, the relay device 1 can switch the communication destination from the terminal 2A to another terminal by using the token, and can acquire the authentication information of the switching destination. Even if it is not sent, the operation related to the cooperative web application can be easily reproduced.

  Also, according to the above embodiment, when receiving the response data during the communication recording process, the relay device 1 refers to the switching information and determines whether the switching start identification number is recorded. When the relay device 1 determines that the switching start identification number is not recorded, the relay device 1 notifies the terminal 2A that there is a change in communication destination switching in the case of request data that requires communication destination switching. Insert script data into the received response data. And the relay apparatus 1 transmits the response data which inserted script data to the terminal 2A, and updates switching information according to the notification from the terminal 2A. According to such a configuration, the relay device 1 sets the timing for changing the communication destination in the switching information during the communication recording process. Therefore, when reproducing the communication recording, the switching of the communication destination is performed using the switching information. It is possible to make changes.

[Programs]
The relay device 1 can be realized by mounting each function of the control unit 10 and the like on an information processing device such as a known personal computer or workstation.

  Further, the relay apparatus 1 has been described as having a communication recording process and a reproduction process. However, the communication recording process and the reproduction process may not be the same relay apparatus, and may be included in different relay apparatuses. In such a case, the communication record table 31, the authority switching record table 32, and the general-purpose processing table 33 may be shared by the respective relay devices.

  In addition, each component of each illustrated apparatus does not necessarily need to be physically configured as illustrated. That is, 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 communication recording unit 13 and the script insertion unit 14 may be integrated as one unit, or the authority switching reproduction unit 21 and the token discarding unit 22 may be integrated as one unit. On the other hand, the authority switching reproduction unit 21 may be distributed to a processing unit that reproduces authority switching communication and a processing unit that reproduces communication from the start of authority switching to the end thereof. Further, the communication record table 31, the authority switching record table 32, and the general-purpose processing table 33 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. 1 will be described with reference to FIG.

  FIG. 18 is a diagram illustrating a computer that executes a relay program. As illustrated in FIG. 18, 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 recording table 31, the authority switching recording table 32, the general-purpose processing table 33, and the token management table 34 illustrated 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 the information read from the relay processing related information 1032 and the like appropriately in the area allocated to itself on the RAM 1010, and executes various data processing based on the expanded data and the like.

  The medium reader 1050 reads the relay program 1031 from a medium or the like that stores the relay program 1030 even when the relay program 1030 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 reading device 1050 such as a CD-ROM. Further, 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.

DESCRIPTION OF SYMBOLS 1 Relay device 10 Control part 11 Terminal communication part 12 External service communication part 13 Communication recording part 14 Script insertion part 15 Authority switching recording part 16 Generalization part 17 Communication recording calling part 18 Record reproduction part 19 Authority switching recording calling part 20 Token issue Unit 21 Authority switching reproduction unit 22 Token discard unit 31 Communication recording table 32 Authority switching recording table 33 General-purpose processing table 34 Token management table 2A, 2B Terminal 3 Web server 41 Web application 9 Web relay system

Claims (6)

A relay method in which a relay device relays communication between a client terminal and a web server that executes a web application,
Record the request data transmitted from the client terminal to the web server and the response data received from the web server in a storage device,
Record switching information, which is information related to request data processed after the communication destination client terminal is switched, in the storage device,
A relay method comprising: switching a communication destination client terminal based on switching information recorded in the storage device and reproducing request data and response data recorded in the storage device. The process of recording the switching information includes, as request information including identification information, identification information for switching start and switching end of request data processed after the communication destination client terminal is switched as the switching information. Record in storage,
When the reproduction process receives a reproduction request from the client terminal, it determines whether or not the identification information of the request data to be reproduced matches the switching start identification information recorded in the switching information, and the request data If it is determined that the identification information matches the switching start identification information recorded in the switching information, the client terminal is caused to switch the communication destination, and the request is made according to information about the communication destination from the switched communication destination. The relay method according to claim 1, wherein the data is reproduced. In the case where it is determined that the identification information of the request data matches the switching start identification information recorded in the switching information, the reproducing process issues a token to the client terminal, and uses the issued token to The relay method according to claim 2, wherein the client terminal is caused to switch the communication destination, and the request data is reproduced according to information on the communication destination from the switched communication destination. In the process of recording the switching information, when the response data is received in the process of recording the request data and the response data, the switching information is referred to, and it is determined whether or not the switching start identification information is recorded. If it is determined that the switching start identification information is not recorded, the script data for notifying the client terminal that there is a change in the communication destination switching is received in the case of request data that requires the switching of the communication destination. The relay method according to claim 1, wherein the switching information is inserted into the response data and transmitted to the client terminal, and the switching information is updated in response to a notification from the client terminal. A relay device that relays communication between a client terminal and a web server that executes a web application,
A first storage unit that records request data transmitted from the client terminal to the web server and response data received from the web server;
A second storage unit that records switching information that is information related to request data processed after the communication destination client terminal is switched;
Based on the switching information recorded in the second storage unit, the communication destination client terminal is switched, and a reproduction unit that reproduces the request data and response data recorded in the first storage unit,
A relay apparatus comprising: On the computer,
Record the request data transmitted from the client terminal to the web server that executes the web application and the response data received from the web server in the storage device,
Record switching information, which is information related to request data processed after the communication destination client terminal is switched, in the storage device,
A relay program for switching a communication destination client terminal based on switching information recorded in the storage device, and executing processing for reproducing request data and response data recorded in the storage device.

Images