JP4197658B2 - Client computer, automatic transfer program, automatic transfer method - Google Patents

Description

The present invention relates to a client computer , an automatic transfer program, and an automatic transfer method, for example.

  Conventionally, various contents have been published on the Web, and can be roughly classified into static contents and dynamic contents. Static content refers to content that can be cached with a normal proxy cache, and dynamic content refers to content that cannot be cached with a normal proxy cache. In recent years, dynamic content is often used in, for example, portal sites, electronic commerce, real-time information services, paid content such as videos and music, and in-house systems.

  In a computer system comprising a Web server and a client computer (hereinafter referred to as a client), when using dynamic content on the Web server from the client, the client always sends a request to the Web server for processing. You must receive the results. For this reason, there are drawbacks in that a load is applied to the Web server and network traffic increases.

  Therefore, a technology (fingerprint cache: hereinafter referred to as FP technology) that installs a proxy server (server-side proxy, client-side proxy, etc.) between the Web server and the client to reduce the network load by using caching and functions associated therewith. ) Has been proposed (see, for example, Non-Patent Document 1).

  In this FP technology, for the content once transmitted between the Web server and the client, the content cached in the proxy on the client side is displayed or the request target content and cache are displayed only by exchanging requests and responses from the next time. Since the desired content can be displayed by communication only with the difference with the content that is being used, the communication data amount is reduced, which is particularly effective in a communication environment using a low-speed line.

By the way, in an in-house system or the like, an authentication server is often installed in a network and many clients are connected to the network.
In such a system environment, in order to access an external server from a client, a session is established through user authentication by an authentication server, and then the external server is accessed.

On the other hand, in a company having a large number of clients, there is a demand for managing the state of application software (hereinafter referred to as a client module) of each client with an external server without involving the user. For example, there is a demand for changing client module settings of a large number of clients at a certain timing without omission.
To manually change the settings of the client modules of all clients connected to the network, it is necessary to have each client operator change the settings by sending e-mail to individual clients. Not all people have the same computer skills, and not everyone can change the client settings just by looking at the email, and if there are a large number of clients, they will definitely change the settings of all the client modules It is not easy to do.

Therefore, it is conceivable to send a setting file from the server to each client and automatically update the setting of the client module.
For this purpose, when each client is started, a request is sent from the client module to the server, a setting file is sent from the server to each client by this request, and setting is performed using the setting file received by the client module. The change process may be automatically executed.

However, in the case of a computer system using conventional FP technology, a request is sent from the client module to the authentication server unless a session is established and a session ID (identification information for identifying a session) is not cached in the client. The authentication server sends a login screen when it is issued, and if the user does not enter login information, the user is not authenticated by the authentication server and a session is not established. There is a problem that the function cannot be realized. Although this problem can be solved by providing the client module with a function to interpret the login screen sent from the authentication server, it is necessary to incorporate the same function as the browser into the client module. is required.
Kenichiro Yoshii et al., “Fingerprint Cache and Application to Dynamic Web Content Delivery”, 4th Internet Technology Workshop (2001.9.5-2001.9.7), Figure 2

  As described above, in the conventional technology described above, in the system configuration in which the proxy server and the authentication server are arranged between the Web server and the client, when the client module setting of the client is automatically updated, the request from the client module to the server is authenticated. There was a problem that the background processing between the client and the proxy server could not be executed automatically because it was repelled by the server.

The present invention has been made to solve such problems, and in a system in which a proxy server and an authentication server are arranged between a web server and a client, a function for automatically executing background processing between the client and the proxy server. It is an object to provide a client computer , an automatic transfer program, and an automatic transfer method that can realize the above.

In order to solve the above-described problems, the client computer of the present invention responds to a request from a user by performing user authentication with a proxy server that mediates a request for content published by a web server on a network and its response. When the client computer connected via the network with the authentication server that establishes a session to the access destination transmits the access destination information and the login information to the authentication server and is authenticated by the authentication server A web browser that establishes a session with an access destination, a cache that is provided separately from the cache of the web browser, and that can store session identification information in association with access destination information, and the web browser and the authentication server Request Stores the session identification information included in the response from the authentication server to the web browser in the cache while relaying the exchange of responses, and the session identification information is stored in the cache at or after activation. If the session identification information is stored, the session identification information and corresponding access destination information are read from the cache, and setting information for performing automatic processing is obtained from the proxy server. While sending the request to the authentication server and updating the software setting of the client module itself using the setting information included in the response received from the proxy server through the authentication server in response to the request. Client that performs processing Characterized by comprising a module.

The client computer according to the present invention further comprises log storage means for storing a log of processing executed by the client computer according to claim 1, wherein the client module has the session identification information at startup. If the session identification information is stored as a result of determining whether or not it is stored in the cache , the session identification information, the access destination information, and the log storage unit log are added to the request and the authentication is performed. It is transmitted to a server.

The automatic transfer program of the present invention includes a proxy server that mediates a request for a content published by a web server on a network and a response thereof, and a session to an access destination for a request from a user by performing user authentication. In an automatic file transfer program for causing a client computer connected via a network to an authentication server to be established to execute processing, the client computer transmits the access destination information and login information to the authentication server, and the authentication server A web browser that establishes a session with the access destination when the user is authenticated, a cache that is provided separately from the web browser and that can store session identification information in association with the access destination information, the web browser In relaying a request or response exchange with the authentication server, the session identification information included in the response from the authentication server to the web browser is stored in the cache, and the session identification information is stored at the time of activation or after activation. It is determined whether or not the session identification information is stored in the cache, and when the session identification information is stored, setting information for reading the session identification information and the corresponding access destination information from the cache and performing automatic processing. While adding to the request for obtaining from the proxy server and transmitting to the authentication server, the setting of the client module itself using the setting information included in the response received from the proxy server through the authentication server in response to the request The process of updating Characterized in that to function as a client module.

The automatic transfer method of the present invention includes a proxy server that mediates a request for a content published by a web server on a network and a response thereof, and a session to an access destination for a request from a user by performing user authentication. In an automatic file transfer method in a client computer connected to an authentication server to be established via a network, when the web browser transmits the access destination information and login information to the authentication server and the user is authenticated by the authentication server Included in the response from the authentication server to the web browser while the client module relays the step of establishing a session with the access destination and the exchange of requests or responses between the web browser and the authentication server Storing session identification information in a cache provided separately from the web browser; determining whether the session identification information is stored in the cache when the client module is activated or after activation; When identification information is stored, the session identification information and corresponding access destination information are read from the cache, and setting information for performing automatic processing is added to the request for obtaining from the proxy server and the authentication is performed. sending to the server, the client module using the setting information included in the response received from the authentication server; and a step of executing a process of updating their configuration.

In the present invention, for example, whether or not a session ID corresponding to the access destination is stored in the client computer at a predetermined timing such as at the time of activation, automatic scheduling after activation, or a simple operation by the user, and the session identification information Is stored, a request with the session identification information added is transmitted from the client computer to the authentication server.
For the request received from the client computer, the authentication server determines whether or not the session identification information exists and the validity of the existing session identification information. If the session identification information is valid, the request received from the client computer is Therefore, the response can be received from the proxy server to the client computer through the authentication server. As a result, the software running on the client computer can execute a process of updating its own setting using the setting information included in the received response. In addition, a log of processing executed by the client computer can be stored, and the log can be automatically uploaded to the proxy server at a predetermined timing.

  As described above, according to the present invention, in a system in which a proxy server and an authentication server are arranged between a web server and a client, a function of automatically executing background processing between the client and the proxy server can be realized.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. FIG. 1 is a diagram showing a configuration of a proxy cache type client / server system according to an embodiment of the present invention.
As shown in the figure, this proxy cache type client / server system includes at least one web server computer 1 (hereinafter referred to as Web server machine 1), a proxy server computer 2 (hereinafter referred to as proxy server machine 2), a user. An authentication server computer 3 (hereinafter referred to as “authentication server machine 3”) and a client computer 4 (hereinafter referred to as “client PC 4”) are connected via a communication line. Each machine is a computer including a CPU, storage means such as a memory, a hard disk device, a monitor, a mouse, a keyboard, and the like. The CPU operates as processing means in cooperation with software installed in the hard disk device of each machine. When the processing means operates, a cache area is set in the memory. The cache area corresponds to the caches 22 and 43 shown below.
The Web server machine 1 includes Web server software 11 (hereinafter referred to as Web server 11) and a content storage unit 12.
The proxy server machine 2 includes server-side proxy software 21 (hereinafter referred to as server proxy 21) and a cache 22 as setting information storage means. The cache 22 stores (stores) a setting file which is setting information of software (client module 42) operating on the client computer PC4. The server proxy 21 mediates a request for the content of the Web server machine 1 and its response.
The authentication server machine 3 includes authentication server software 31 (hereinafter referred to as an authentication server 31) and an authentication information storage unit 32. The authentication information storage unit 32 stores user authentication information (login information such as a user name and password) registered in advance as a regular user.
The client PC 4 includes browser software 41 (hereinafter referred to as browser 41), client-side application software 42 (hereinafter referred to as client module 42), and a cache 43. In the cache 43, the received session ID, content, FP, and the like are cached (saved). The session ID is stored as a session ID management table (see FIG. 9) associated with each URL.

That is, the proxy cache type client / server system includes one or more Web server machines 1, one or more proxy server machines 2, one or more authentication server machines 3, and 1 connected by a communication line. Web server 11 having one or a plurality of clients 4, operating on Web server machine 1, server proxy 21 operating on proxy server machine 2, authentication server 31 operating on authentication server machine 3, client A browser 41 and a client module 42 operating on the machine 4 are included.
The server proxy 21 has a function of transmitting a request received from the client module 42 via one or more authentication servers 31 to the Web server 11 directly or via one or more proxy servers. For an intermediary function that sends a response received directly or via one or more proxy servers to the client module 42 via the authentication server 31, and a request received via the authentication server 31 from the client module 42, A response is created using information cached in the cache 22 (setting file for setting update of the client module 42, content received from the Web server 11, etc.), and the created response is sent to the client module via the authentication server 31. And a function of transmitting to 2. For example, the server proxy 21 reads the setting file stored in the cache 22 and returns it as a response to a setting file download request from the client module 42.
One or a plurality of proxy servers may be connected between the Web server machine 1 and the proxy server machine 2 or between the proxy server machine 2 and the authentication server machine 3.
The authentication server 31 has a function of transmitting a request received from the browser 41 via the client module 42 to the server proxy 21, a function of transmitting a response received from the server proxy 21 to the browser 41 via the client module 42, It is determined whether or not a session ID is attached to the received request. If no session ID is attached, an authentication screen stored in the authentication information storage unit 32 is transmitted to the browser 41, and the received request While the user authentication information (login information such as user name and password) is attached to the user authentication, after establishing the session with the access destination after issuing the user authentication, the session ID is issued and transmitted to the browser 41, If the received request has a session ID, The request received from the ant module 42 and a function of transmitting to the server the proxy 21. The session ID is session identification information.

The client module 42 can be broadly divided into a network load reduction function that reduces the download amount at the second and subsequent access to the access destination and a management function of the server proxy 21 to automatically download the setting file. It has an automatic download and update function for automatically updating the setting contents. The automatic download and update function is a function that is activated and executed by the client module 42 when the client PC 4 is activated. The network load reduction function is the function described in the related art.
That is, the client module 42 transmits a request received from the browser 41 to the server proxy 21 via one or a plurality of authentication servers 31 and the response received from the server proxy 21 via the authentication server 31 to the browser 41. A request such as a request for content including an access destination (URL) and a session ID and a request for downloading a setting file is created, and the created request is transmitted to the server proxy 21 via the authentication server 31. A function for receiving a response from the server proxy 21 to the request via the authentication server 31, and whether the request or response received from the browser 41 has a session ID attached thereto. A session ID stored in the cache 43 in association with the access destination (URL), and a session stored (cached) in the cache 43 when accessing the same access destination (URL) as before. A function of adding an ID to a request and transmitting the request. The cache 43 is session identification information storage means.

  In the client module 42, the URL of a proxy server that is an access destination for automatically downloading the setting file is set (stored) in advance, and the client module 42 has a predetermined timing (at startup) when updating the setting. Alternatively, immediately after startup, always or automatically after startup or simple operation by the user or the like, the contents of the cache 43 are checked, and a request including the URL and the session ID cached in the cache 43 is transmitted. . The setting file is an information file from which the setting contents of itself (software) are updated.

The operation of the proxy cache type client / server system of this embodiment will be described below. The network load reducing function will be described with reference to FIGS. The network load reduction function will be described separately because the operation differs between the first access and the second and subsequent accesses. First, the case of the first access will be described.
In the case of the first access, when the user activates the client PC 4 and the browser 41 and inputs a URL desired to be displayed on the screen of the browser 41 (S101 in FIG. 3), the browser 41 receives a request including the input URL. Is transmitted to the client module 42 (S102).

The client module 42 transfers the request received from the browser 41 to the authentication server 31 (S103).
When the request is received, the authentication server 31 determines the presence and validity of the session ID (S104). In this case, since it is the first access, since the session ID is not included in the request, the authentication server 31 transmits (replies) the login authentication screen to the client module 42 as a response (S105).
The client module 42 transfers the response received from the authentication server 31 to the browser 41 (S106).
The browser 41 displays a login authentication screen for the received response (S107).
When the user who sees the login authentication screen displayed on the screen of the browser 41 inputs the login ID and password (S108), the browser 41 creates a request including the input login ID and password and sends it to the client module 42. (S109).

The client module 42 transfers the request received from the browser 41 to the authentication server 31 (S110).
When the request is received, the authentication server 31 compares the login ID and password included in the request with the authentication information stored in the authentication information storage unit 32 and executes authentication processing (S111). It is determined whether the user is a regular user.
If the user is a regular user, the authentication server 31 establishes a session with an external server (the server proxy 21 or the Web server 11), creates a session ID that is identification information for identifying the session, and A response for notification with the session ID added is transmitted (returned) to the client module 42 (S112).
The client module 42 transfers the response received from the authentication server 31 to the browser 41 (S113).
The browser 41 reads the session ID from the received response, and transmits a request with the session ID added thereto (hereinafter referred to as a request with a session ID) to the client module 42 (S114).

When the request with session ID is received, the client module 42 transfers the request to the authentication server 31 according to the session ID included in the request with session ID (S115), and caches (saves) the session ID in the cache 43 ( S116).
When a request with a session ID is received, the authentication server 31 determines whether or not a session ID is added to the request. If a session ID is added, the authentication server 31 determines the validity of the session ID. (S117).
The validity of the session ID is determined by comparing it with the session ID created and stored by the authentication server itself at the previous access.
If the session ID is valid as a result of this determination, the authentication server 31 transfers the request with the session ID to the server proxy 21 (S118).

When receiving a request with a session ID from the authentication server 31, the server proxy 21 transfers the request to the Web server 11 that is the destination (S119).
When the request with the session ID is received, the Web server 11 creates a response to the request and transmits it to the client PC 4 (S120).
This response includes the content to be requested.
The response transmitted from the Web server 11 is received by the server proxy 21, added with an FP (fingerprint), transferred to the authentication server 31 (S 121), and cached in the cache 22.
The authentication server 31 transfers the received response to the client module 42 (S122).
The client module 42 transfers the received response to the browser 41 (S123) and caches it in the cache 43. The transferred response is received by the browser 41 and displayed on the screen of the browser 41 (S124), and is cached in its own temporary file or the like.

Next, the case of the second and subsequent accesses will be described with reference to FIG.
In the case of the second and subsequent accesses, when the user inputs a URL desired to be displayed on the screen of the browser 41 (S201), the browser 41 receives a request including the input URL and a session ID cached in the temporary file. (This is called a request with a session ID) is created and transmitted to the client module 42 (S202).

The client module 42 stores the session ID included in the request with session ID received from the browser 41 in the cache 43 (S203), and transfers the request with session ID to the authentication server 31 (S204).
When the request with session ID is received, the authentication server 31 determines the presence / absence and validity of the session ID (S205). In this case, since it is the second access, the session ID is included in the request, and the authentication server 31 collates the session ID included in the request with the session ID that was created and stored for the first time. Then, the validity of the received session ID is determined.
If the session IDs match each other as a result of this determination, the authentication server 31 determines that the received session ID is valid, and transfers the received request with session ID to the server proxy 21 (S206).

When receiving a request with a session ID from the authentication server 31, the server proxy 21 transfers the request to the Web server 11 that is the destination (S207).
When the request with the session ID is received, the Web server 11 creates a response to the request and transmits the response to the client PC 4 (S208).
The response transmitted from the Web server 11 is received by the server proxy 21 and transferred from the server proxy 21 to the authentication server 31 (S209).
At this time, the transferred response includes only FP (fingerprint) in the case of the same content as the previous time. In addition, when a part of the requested content is different, only the difference content and the FP are included.
The authentication server 31 transfers the received response to the client module 42 (S210).

  In accordance with the FP included in the received response, the client module 42 reads out the corresponding content from the cache 43 and transfers it as a response to the browser 41 (S211). The transferred response is received by the browser 41 and displayed on the screen of the browser 41 (S212).

Next, referring to FIG. 5, in this proxy cache type client / server system, the client module 42 automatically downloads the setting file by using the management function of the server proxy 21 and automatically updates its own setting. The update function will be described.
In this case, when the user starts the OS of the client PC 4 by turning on the power of the client PC 4 or the like, the client module 42 is started almost immediately, and immediately accesses the cache 43 and stores the session ID in the cache 43. Is checked whether it is cached (S301). This check operation is always performed while the client module 42 is running. Note that the check operation may be performed at regular time intervals.
If the session ID is not cached in the cache 43 as a result of this check, the client module 42 waits for a predetermined time and checks again.

If the session ID is cached in the cache 43 as a result of the check, the client module 42 reads the session ID from the cache 43 (S302), creates a request with a session ID, and transmits it to the authentication server 31 ( S303). The request in this case is a setting file download request.
When the request with session ID is received, the authentication server 31 determines the presence / absence and validity of the session ID (S304). In this case, the session ID is included in the request, and the authentication server 31 receives the session ID included in the request against the session ID created and stored for the first time. The validity of the session ID is determined.
If the session IDs match as a result of this determination, the authentication server 31 determines that the received session ID is valid, and transfers the received request with session ID to the server proxy 21 (S305).

When receiving a request with a session ID from the authentication server 31, the server proxy 21 reads the setting file requested by the request from the memory and transmits it as a response to the client module 42 through the authentication server 31 (S306, S307).
The client module 42 saves the received response setting file in the memory or the cache 43 (S308), and then executes a process of updating its own setting based on the saved setting file (S309).

  As described above, according to the proxy cache type client / server system of this embodiment, the client module 42 having the function of caching the previously received content is not equipped with the function of interpreting the authentication screen, that is, the browser 41. The client module 42 accesses (provides a request) the server proxy 21 via the authentication server 31 in the background operation without implementing an advanced interpretation function equivalent to the above, and the client proxy 42 responds to the request from the server proxy 21 to the client module 42. The configuration file can be automatically downloaded and the client module 42 can automatically change its configuration.

In addition, this invention is not limited only to the said embodiment.
In the above embodiment, an example of a system in which each machine is connected one by one has been described. However, the present invention can also be applied to cases where a plurality of authentication servers are installed (connected) in parallel and / or in series. It is.
For example, as shown in FIG. 6, the client PC 4 accesses the Web server 1A via the authentication server 31A and the server proxy 21, and accesses the Web server 1B via the authentication server 31B to authenticate the management function of the server proxy 21. When configured to be used via the server A, that is, in a system configuration in which a plurality of authentication servers 31A and 31B are installed in parallel, the session ID added to the request for downloading the setting file is the authentication server The session ID issued when the session with the server proxy 21 is established, that is, the session ID issued by the authentication server 31A is required instead of the session ID issued by B. For this reason, it is necessary to store the session ID separately for each authentication server 31A, 31B (for each URL) in the cache 43 or the memory of the client PC 4.

  For example, as shown in FIG. 7, when a plurality of authentication servers 31A and 31C are installed in series, it is necessary to hold a plurality of session IDs in the cache 43 for one URL. In this example, the session ID (A_SessionID = aaaaaaaaaa) issued by the authentication server 31A and the session ID (C_SessionID = cccccccccc) issued by the authentication server 31C with respect to http: // serverA / which is the URL of the access destination Two need to be held in the cache 43.

Furthermore, as shown in FIG. 8, when a plurality of authentication servers 31A, 31B, and 31C are installed in series and in parallel, a plurality of session IDs must be held in the cache 43 for one URL. In addition, it is necessary to manage each session ID separately for each URL.
In this example, http: // serverA / C / (the session ID issued by the authentication server 31A and the session ID issued by the authentication server 31C) as the first access destination (access path) in the serial configuration and the second As an access destination (access route), there is http: // serverA / B / (a session ID issued by the authentication server 31A and a session ID issued by the authentication server 31B).

  In order to satisfy these conditions, a session ID management table in which the URL of the access destination is associated with the session ID is held in the cache 43 or the memory of the client PC 4, and the client module 42 checks the cache 43 at the time of activation. From the contents of the session ID management table 91 held in the cache 43 or memory, the session ID corresponding to the access destination is read from the cache 43 and added to the request for transmission.

Specifically, in the example of the system configuration in FIG. 8, as shown in FIG. 9, the session ID management table 91 is stored in http: // serverA / C /, which is a URL with the Web server 11A system as an access destination. On the other hand, two session IDs of A_SessionID = aaaaaaaaaa and C_SessionID = cccccccccc are stored in association with each other.
Further, two session IDs A_SessionID = aaaaaaaaaa and B_SessionID = bbbbbbbbbb are stored in association with http: // serverA / B /, which is a URL with the Web server 11B system as an access destination.
In this way, by providing a function for managing a plurality of session IDs for each URL, a plurality of authentication servers 31A, 31B, 31C are connected (arranged) in series and / or in parallel between the client module 42 and the server proxy 21. Even in such a case, the client module 42 can automatically access the server proxy 21 of the automatic download destination via the authentication server 31A to download the setting file and update the setting.

In the above-described embodiment, the function of the client module 42 automatically downloading the setting file of the server proxy 21 has been described. In addition to this, the proxy cache type client / server system also transmits a log file from the client module 42 to the server proxy 21. Has the ability to upload.
Hereinafter, an automatic upload function in which the client module 42 automatically uploads the log file stored in the client PC 4 to the server proxy 21 in the proxy cache type client / server system will be described with reference to FIG.
In this case, the client module 42 running on the client PC 4 sequentially stores a log file for trouble analysis in a predetermined area of the hard disk device every time the process is executed (S401).
As in the above embodiment, the client module 42 accesses the cache 43 at a predetermined timing, and checks whether the session ID is cached in the cache 43 (S402). This check operation is always performed while the client module 42 is running. Note that the check operation may be performed at regular time intervals.
If the session ID is not cached in the cache 43 as a result of this check, the client module 42 waits for a predetermined time and checks again.

If the session ID is cached in the cache 43 as a result of the check, the client module 42 reads the session ID from the cache 43 (S403) and reads the contents of the log file from a predetermined area of the hard disk device ( In S404, a request with the log and the session ID added is created and transmitted to the authentication server 31 (S405). The request in this case is a log upload request.
When the request is received, the authentication server 31 determines the presence / absence and validity of the session ID (S406). In this case, the request includes a session ID and a log, and the authentication server 31 collates the session ID included in the request with the session ID created and stored for the first time, The validity of the received session ID is determined.
If the session IDs match each other as a result of this determination, the authentication server 31 determines that the received session ID is valid, and transfers the received log and the request with the session ID to the server proxy 21 (S407).

When receiving a request with a log and a session ID from the authentication server 31, the server proxy 21 stores the log included in the request in a predetermined area of the hard disk device (S408). When the log is saved, the client module 42 transmits a response to the log saving request to the client module 42 through the authentication server 31 (S409, S410).
The client module 42 determines that the transmitted log has been normally stored when the response from the server proxy 21 is received.
As a result, in a system configuration in which the authentication server machine 3 is interposed between the client PC 4 and the proxy server machine 2, setting information and logs are automatically transferred between the client PC 4 and the proxy server machine 2 by background processing without human intervention. The function to (exchange) can be realized.

The figure which shows the structure of the proxy cache type | mold client server system of one embodiment concerning this invention. The communication sequence chart which shows the first time access operation in the proxy cache type client server system of FIG. The communication sequence chart which shows the first time access operation of the proxy cache type client server system of FIG. The communication sequence chart which shows the access operation | movement after the 2nd in the proxy cache type | mold client server system of FIG. The figure which shows the proxy cache type client server system of FIG. 2 is a communication sequence chart showing an operation of automatically downloading a setting file stored in a proxy server machine and updating a setting of a client PC in the proxy cache type client / server system of FIG. The figure which shows an example of the system which has arrange | positioned the authentication server in parallel. The figure which shows an example of the system which has arrange | positioned the authentication server in series. The figure which shows an example of the system which has arrange | positioned the authentication server in parallel and in series. The figure which shows a session ID management table. 6 is a communication sequence chart showing an operation of automatically uploading a setting file stored in a client PC to a proxy server machine in this proxy cache type client / server system.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1,1A, 1B, 1C ... Web server machine, 2 ... Proxy server machine, 3 ... Authentication server machine, 4 ... Client PC, 11 ... Web server, 12 ... Content storage part, 21 ... Server proxy, 22 ... Cache, 31 , 31A, 31B, 31C ... authentication server, 32 ... authentication information storage unit, 41 ... browser, 42 ... client module, 43 ... cache, 91 ... session ID management table.

Claims (4)

Through a network, a proxy server that mediates requests and responses to content published by web servers on the network, and an authentication server that establishes a session to the access destination for user requests by performing user authentication Connected client computers,
A web browser that establishes a session with the access destination when the access destination information and login information are transmitted to the authentication server and the user is authenticated by the authentication server;
Provided separately from the cache of the web browser, a cache that can be stored by associating session identification information with access destination information,
While relaying the exchange of requests or responses between the web browser and the authentication server, the session identification information included in the response from the authentication server to the web browser is stored in the cache. It is determined whether or not session identification information is stored in the cache. If the session identification information is stored, the session identification information and corresponding access destination information are read from the cache, and automatic processing is performed. Using the setting information included in the response received from the proxy server through the authentication server in response to the request while adding to the request for obtaining the setting information from the proxy server software of the client module itself Client computer, characterized by comprising a client module that executes processes for updating the hardware settings. The client computer according to claim 1.
Log storage means for storing a log of processing executed by the client computer;
When the session identification information is stored as a result of determining whether or not the session identification information is stored in the cache at startup, the client module determines the session identification information, the access destination information, and the log A client computer, wherein a log of storage means is added to a request and transmitted to the authentication server. Through a network, a proxy server that mediates requests and responses to content published by web servers on the network, and an authentication server that establishes a session to the access destination for user requests by performing user authentication In an automatic file transfer program that causes a connected client computer to execute processing,
The client computer;
A web browser that establishes a session with the access destination when the access destination information and login information are transmitted to the authentication server and the user is authenticated by the authentication server;
A cache that is provided separately from the web browser and that can store session identification information in association with access destination information;
While relaying the exchange of requests or responses between the web browser and the authentication server, the session identification information included in the response from the authentication server to the web browser is stored in the cache. It is determined whether or not session identification information is stored in the cache. If the session identification information is stored, the session identification information and corresponding access destination information are read from the cache, and automatic processing is performed. Using the setting information included in the response received from the proxy server through the authentication server in response to the request while adding to the request for obtaining the setting information from the proxy server configuration of client module itself Automatic transfer program for causing to function as a client module that executes a process to update. Through a network, a proxy server that mediates requests and responses to content published by web servers on the network, and an authentication server that establishes a session to the access destination for user requests by performing user authentication In an automatic file transfer method in a client computer connected by
A step of establishing a session with the access destination when the web browser transmits the access destination information and login information to the authentication server and the user is authenticated by the authentication server;
A cache provided separately from the web browser for session identification information included in a response from the authentication server to the web browser while a client module relays a request or response exchange between the web browser and the authentication server The step of storing in
When the client module is activated or after activation, it is determined whether the session identification information is stored in the cache, and when the session identification information is stored, the access destination information corresponding to the session identification information And sending the setting information for performing automatic processing to the request for obtaining from the proxy server to the authentication server,
And a step of executing a process in which the client module updates its own setting using setting information included in a response received from the authentication server.

Images