Information processing device, information processing method, and program

Abstract

To provide an information processing device, an information processing method, and a program that allows a user to control the size of cookies stored on a terminal.SOLUTION: An information processing device includes a receiving unit that receives, from a terminal, an HTTP request including a cookie stored in the terminal, a transmitting unit that transmits an HTTP response to the terminal, a selecting unit that, when a request is received from the terminal, selects a cookie to be deleted from among the cookies stored in the terminal, and a deletion processing unit that instructs the terminal to delete the cookie to be deleted selected by the selecting unit.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to an information processing device, an information processing method, and a program. [Background technology]

[0002] A technology is known that manages the status between a web server and a web browser by storing a character string called a cookie in the web browser. For example, Patent Document 1 discloses a behavior history analysis system that identifies and links users who have accessed the Internet using cookie information or the like, thereby determining their behavioral patterns more accurately. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2009-289172 Summary of the Invention [Problem to be solved by the invention]

[0004] With the increase in web services, various cookies are stored in the web browsers of devices. Cookies stored on a device are sent from the device to a web server when the device's web browser accesses the server. However, if the data size of the cookies stored on a device is too large, the web server may receive an HTTP (Hypertext Transfer Protocol) request containing a large number of cookies and return an error to the device. If an error is returned from the web server in this way, the device will be unable to receive the desired web service.

[0005] Therefore, an object of the present invention is to provide an information processing device, an information processing method, and a program that make it possible to control the size of cookies stored in a terminal. [Means for solving the problem]

[0006] An information processing device according to one embodiment of the present invention includes a receiving unit that receives an HTTP request from a terminal, the request including a cookie stored on the terminal; a transmitting unit that transmits an HTTP response to the terminal; a selecting unit that, when a request is received from the terminal, selects a cookie to be deleted from among the cookies stored on the terminal; and a deletion processing unit that instructs the terminal to delete the cookie to be deleted selected by the selecting unit. [Effects of the Invention]

[0007] According to the present invention, it is possible to provide an information processing device, an information processing method, and a program that make it possible to control the size of cookies stored in a terminal. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of a Web system according to an embodiment of the present invention. [Figure 2] FIG. 2 illustrates an example of a hardware configuration of a Web server. [Figure 3] FIG. 2 is a diagram illustrating an example of a functional block configuration of a Web server. [Figure 4] FIG. 10 is a diagram illustrating an example of a cookie list. [Figure 5] FIG. 10 is a diagram illustrating an example of a cookie management DB. [Figure 6] FIG. 10 is a diagram illustrating an example of a processing procedure performed by a Web system. [Figure 7] 10 is a flowchart illustrating an example of a processing procedure for a terminal to determine whether to execute a cookie deletion request. [Figure 8] 10 is a flowchart illustrating an example of a processing procedure in which a Web server selects cookies to be deleted. DETAILED DESCRIPTION OF THE INVENTION

[0009] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described with reference to the accompanying drawings, in which the same reference numerals denote the same or similar components.

[0010] <System configuration> 1 is a diagram showing an example of a Web system 1 according to this embodiment. The Web system 1 includes a Web server 10 and a terminal 20. The terminal 20 can communicate with the Web server 10 via a communication network N.

[0011] The web server 10 is a server that provides various websites. The websites provided by the web server 10 are not particularly limited, but examples thereof include EC (Electronic Commerce) sites, online banking sites, and travel reservation sites. The web server 10 may be realized by multiple servers.

[0012] Terminal 20 is a terminal operated by a user, and includes various terminals equipped with a web browser, such as smartphones, tablet terminals, mobile phones, personal computers (PCs), notebook PCs, personal digital assistants (PDAs), and home game consoles.

[0013] The Web server 10 issues cookies to terminal 20 that has accessed the website as necessary. The issued cookies are stored in terminal 20. When terminal 20 accesses the same website again, it sends the stored cookies to the Web server 10. Based on the received cookies, the Web server 10 can grasp the behavior of terminal 20 within the website.

[0014] When issuing a cookie, the web server 10 can specify the domain in which the cookie will be valid. A cookie with a specified domain is valid in the specified domain and any subdomains under the specified domain. On the other hand, if no domain is specified when the cookie is issued, the cookie is valid only in the domain in which it was issued. For example, if cookie A with xxx.com specified as the domain is stored in the terminal 20, the terminal 20 will send cookie A to the web server 10 whether it accesses the xxx.com website or the aaa.xxx.com website. On the other hand, if cookie B issued by xxx.com without specifying a domain is stored in the terminal 20, the terminal 20 will send cookie B when it accesses the xxx.com website, but will not send cookie B when it accesses the aaa.xxx.com website.

[0015] Here, if Web server 10 provides a large number of websites in the same domain and subdomains under that domain, and each website issues its own various cookies, a large number of cookies will be stored on terminal 20. Furthermore, when terminal 20 accesses a website, cookies that are valid for that website's domain and subdomains under that domain will be sent to Web server 10 all at once.

[0016] Because cookies are included in the header of an HTTP request, if a large number of cookies are sent, the header size also increases. Furthermore, some web servers 10 impose a limit on the upper header size of HTTP requests. Therefore, if a large number of cookies are sent from terminal 20, web server 10 determines that the header size exceeds the upper limit and returns an error, preventing terminal 20 from accessing the website. To prevent this situation, in this embodiment, if the total data size of cookies stored on the terminal is equal to or greater than a threshold, web server 10 deletes the cookies stored in the web browser of terminal 20 so that the total data size of cookies is equal to or less than the threshold.

[0017] Next, if multiple websites are provided under the same domain or subdomains under that domain, and each website issues its own unique cookies, it may become difficult for the web server 10 as a whole to manage the cookies it issues. Furthermore, because website content is frequently updated due to changes in services, etc., some cookies may no longer be in use. In such a situation, it is not easy for a website administrator to accurately keep track of all cookies issued. Therefore, the web server 10 according to this embodiment accumulates and analyzes cookies included in HTTP requests received from multiple terminals 20, thereby creating a database that indicates the types of cookies issued by the web server 10 and the data size of each cookie. This allows, for example, the administrator of the web server 10 to centrally manage the types of cookies issued by the web server 10 by referring to the database. Furthermore, the administrator can classify issued cookies into cookies that can be deleted and cookies that should not be deleted, for example, by checking with the creator of each website.

[0018] <Hardware configuration> 2 is a diagram showing an example of the hardware configuration of the Web server 10. The Web server 10 has a processor 11 such as a CPU (Central Processing Unit) or a GPU (Graphical Processing Unit), a memory (e.g., RAM or ROM), a storage device 12 such as an HDD (Hard Disk Drive) and / or an SSD (Solid State Drive), a network IF (Network Interface) 13 for wired or wireless communication, an input device 14 for accepting input operations, and an output device 15 for outputting information. The input device 14 is, for example, a keyboard, a touch panel, a mouse, and / or a microphone. The output device 15 is, for example, a display, a touch panel, and / or a speaker.

[0019] The web server 10 may be configured with one or more physical servers, or may be configured with a virtual server running on a hypervisor, or may be configured with a cloud server. The web server 10 may also be called an information processing device.

[0020] <Function block configuration> FIG. 3 is a diagram illustrating an example of a functional block configuration of the Web server 10. The Web server 10 includes a memory unit 100, a receiving unit 101, a transmitting unit 102, a selecting unit 103, a deletion processing unit 104, a collecting unit 105, and an analyzing unit 106. The memory unit 100 can be realized using a storage device 12 included in the Web server 10. The receiving unit 101, the transmitting unit 102, the selecting unit 103, the deletion processing unit 104, the collecting unit 105, and the analyzing unit 106 can be realized by the processor 11 of the Web server 10 executing a program stored in the storage device 12. The program can be stored in a storage medium. The storage medium storing the program may be a non-transitory computer-readable medium. The non-transitory storage medium is not particularly limited, and may be, for example, a storage medium such as a universal serial bus (USB) memory or a compact disc read-only memory (CD-ROM).

[0021] The storage unit 100 stores a cookie list 100a that manages cookies to be deleted and cookies not to be deleted, a log database (DB) 100b that stores a history (log) of cookies deleted from the terminal 20, a cookie collection DB 100c that collects cookies received by the Web server 10 from the terminal 20, and a cookie management DB 100d that stores the results of analyzing the cookies collected in the cookie collection DB 100c. The cookie list 100a may be generated, for example, based on the results of an administrator of the Web server 10 checking the data size and purpose of cookies recorded in the cookie management DB 100d. Note that the storage unit 100 may be realized by the storage units of multiple servers. For example, the cookie list 100a, the log DB 100b, the cookie collection DB 100c, and the cookie management DB 100d may each be stored on a separate server.

[0022] The receiving unit 101 receives an HTTP request including a cookie stored in the terminal 20 from the terminal 20 .

[0023] The transmitting unit 102 transmits an HTTP response to the HTTP request to the terminal 20. The transmitting unit 102 may also transmit the HTTP response including a script. The script may cause the terminal 20 to execute a process of determining whether or not the terminal 20 should issue a cookie deletion request to the Web server 10. The script may also be called a program. The script may also be JavaScript (registered trademark).

[0024] Furthermore, the transmitting unit 102 may transmit "target information" indicating the target terminal and / or domain for which a cookie deletion request is to be made, by including it in the HTTP response. The script may also cause the terminal 20 to decide whether or not to make a cookie deletion request based on the target information. The target information may also be associated with a percentage of terminals that will make a cookie deletion request for each domain, and the script may cause the terminal 20 to decide whether or not to make a cookie deletion request based on that percentage when the domain specified in the HTTP request is included in the target information. The percentage may be a value (%) set by an administrator, for example.

[0025] When the selection unit 103 receives a cookie deletion request from the terminal 20 (more specifically, a script transmitted to the terminal 20), it selects cookies to be deleted from among the cookies stored in the terminal 20.

[0026] The deletion processing unit 104 instructs the terminal 20 to delete the cookies to be deleted selected by the selection unit 103.

[0027] The collection unit 105 collects cookies included in HTTP requests received from multiple terminals 20 and stores them in the cookie collection DB 100c.

[0028] The analysis unit 106 analyzes the cookies collected by the collection unit 105 on a per-cookie basis and stores the analysis results in the cookie management DB 100d (database). The analysis unit 106 also analyzes the minimum data size, average data size, and maximum data size of cookies with the same name for the collected cookies and stores the results in the cookie management DB 100d.

[0029] FIG. 4 is a diagram showing an example of the cookie list 100a. As shown in FIG. 4A, the cookie list 100a includes a deletion cookie list indicating cookies to be deleted, and as shown in FIG. 4B, a non-deletion cookie list (protected cookies) indicating cookies not to be deleted. The "cookie name" and "domain" indicate the name of the cookie and the domain for which the cookie is valid. Note that when a domain name begins with a dot "." (cookies Aa and Bb in FIG. 4), a domain is specified, indicating that the cookie is valid in both the domain of the same name and subdomains under that domain. On the other hand, when a domain name begins with a letter (cookie Cc in FIG. 4), no domain is specified, indicating that the cookie is valid only in the domain of the same name.

[0030] "Size to be deleted" refers to the size of the cookie to be deleted. For example, in A of FIG. 4, the size of cookie Aa is written as 1 kbyte or more, which means that if the size of cookie Aa stored on terminal 20 is 1 kbyte or more, cookie Aa will be deleted. Note that some cookies have a fixed data size, while others have a variable data size. Therefore, by specifying a "size to be deleted," a cookie can be deleted only if its data size is equal to or greater than a predetermined size. On the other hand, by not specifying a "size to be deleted," a cookie can be deleted regardless of its data size.

[0031] Figure 5 shows an example of the cookie management DB 100d. The "cookie name" and "domain" are the same as those in Figure 4. The "minimum size," "average size," and "maximum size" indicate the minimum, average, and maximum sizes of each cookie that the Web server 10 has received from a terminal 20 in the past. The "number of users" indicates the number of terminals 20 from which the Web server 10 has received a cookie during a predetermined period in the past (e.g., the past year). For example, the example in Figure 5 means that the Web server 10 has received cookies KKt from 500,000 terminals 20 in the past.

[0032] <Processing Procedure> FIG. 6 is a diagram showing an example of a processing procedure performed by the Web system 1.

[0033] In step S10, when the web browser of terminal 20 receives an instruction from the user to access a website provided by web server 10, it sends an HTTP request including all cookies that are valid in the domain of the website and subdomains under that domain to web server 10. A receiving unit of web server 10 receives the HTTP request from terminal 20.

[0034] In step S11, the collection unit 105 of the Web server 10 stores the cookie received from the terminal 20 in the cookie collection DB 100c. The analysis unit 106 may update the cookie management DB 100d by analyzing the data stored in the cookie collection DB 100c at predetermined intervals (for example, once a month).

[0035] In step S12, the transmitting unit 102 of the Web server 10 transmits an HTTP response including the script and the target information to the terminal 20.

[0036] In step S13, the web browser of terminal 20 executes the script included in the received HTTP response. After executing the script, terminal 20 determines whether or not to execute a cookie deletion request based on the target information. If terminal 20 determines to execute the cookie deletion request, it proceeds to the processing procedure of step S14. If terminal 20 determines not to execute the cookie deletion request, it ends the processing without proceeding to the processing procedure of step S14.

[0037] In step S14, the web browser of terminal 20 sends an HTTP request including a cookie deletion request to web server 10. Note that this HTTP request also includes all cookies that are valid in the domain of the accessed website and subdomains under that domain. Note that the domain to be specified in this HTTP request may be embedded in a script in advance. Alternatively, the domain to be specified in this HTTP request may be the highest-level domain among the domains of websites provided by web server 10. This allows more cookies to be included in the HTTP request including the cookie deletion request. Alternatively, sending the HTTP request including the cookie deletion request may be calling an API (Application Programming Interface) provided by web server 10 for accepting cookie deletion requests.

[0038] In step S15, the selection unit 103 of the Web server 10 compares the cookie list 100a with all the cookies received in the processing procedure of step S14 to select one or more cookies to be deleted.

[0039] In step S16, the deletion processing unit 104 of the Web server 10 sends an HTTP response to the terminal 20, including information instructing the terminal 20 to delete the cookie selected in the processing procedure of step S15. The information instructing the terminal 20 to delete the cookie specifically corresponds to information instructing the terminal 20 to change the expiration date stored in the cookie to a date earlier than the current time. The deletion processing unit 104 of the Web server 10 also records the cookie instructed to be deleted in the log DB 100b in association with the identifier of the terminal 20. The identifier of the terminal 20 is arbitrary, but may be, for example, a cookie issued to uniquely identify the terminal 20.

[0040] In step S17, the web browser of the terminal 20 deletes the cookie whose expiration date has been changed to a past date.

[0041] 7 is a flowchart showing an example of a processing procedure for determining whether or not to execute a cookie deletion request by the terminal 20. The processing procedure in FIG. 7 corresponds to the processing procedure in step S13 in FIG.

[0042] In step S100, terminal 20, which has executed the script included in the HTTP response, determines whether or not terminal 20 itself is included in the target information included in the HTTP response, thereby determining whether or not to execute a cookie deletion request. If terminal 20 itself is included, it determines that the cookie deletion request will be executed and proceeds to the processing procedure of step S101, but if terminal 20 itself is not included, it determines that the cookie deletion request will not be executed and ends the processing.

[0043] For example, terminal 20 may determine whether or not the target information includes an identifier of terminal 20 itself. Alternatively, terminal 20 may determine that the target information includes an identifier of terminal 20 itself when the target information includes a numerical value obtained as a result of performing a predetermined calculation on an identifier for uniquely identifying terminal 20.

[0044] Furthermore, the terminal 20 that executed the script included in the HTTP response may determine whether or not to execute a cookie deletion request by determining whether or not the domain of the Web server 10 that sent the HTTP response is included in the target information. If the domain of the Web server 10 is included in the target information, the terminal 20 determines to execute the cookie deletion request and proceeds to the processing procedure of step S101. If the domain of the Web server 10 is not included in the target information, the terminal 20 determines not to execute the cookie deletion request and terminates the processing. Note that the target information may be associated with the percentage of terminals 20 that will execute the cookie deletion request for each domain. For example, suppose that a percentage of 10% is associated with the domain (XXX.com) of the target information. In this case, the terminal 20 may determine to execute the cookie deletion request with a 10% probability if the domain of the Web server 10 that sent the HTTP response is XXX.com.

[0045] In step S101, the terminal 20 transmits an HTTP request including a cookie deletion request to the Web server 10.

[0046] 8 is a flowchart showing an example of the processing procedure for selecting cookies to be deleted by the Web server 10. The processing procedure in FIG. 8 corresponds to the processing procedure in step S15 in FIG.

[0047] In step S200, the selection unit 103 of the Web server 10 acquires cookies stored in the terminal 20. For example, the selection unit 103 of the Web server 10 acquires all cookies included in the header of the HTTP request (step S14 in FIG. 6) that includes a cookie deletion request.

[0048] In step S201, the selection unit 103 of the Web server 10 determines whether the total data size of the cookies acquired in the processing procedure of step S200 is equal to or greater than a threshold. If it is equal to the threshold, the process proceeds to the processing procedure of step S202. If it is less than the threshold, it is determined that cookie deletion is not necessary and the process ends. Note that this threshold may be called the first threshold.

[0049] In step S202, the selection unit 103 of the Web server 10 selects the cookie to be deleted.

[0050] (How to select cookies to delete) Next, several specific examples will be explained regarding the method of selecting cookies to be deleted by the selection unit 103. Note that the deletion methods explained below can be combined in any way.

[0051] [Removal Method 1] If a cookie included in the cookie list to be deleted (list to be deleted) is present among the cookies stored in terminal 20, selection unit 103 may select that cookie as a cookie to be deleted. For example, if the cookie shown in A of FIG. 4 is included in the cookie list to be deleted, selection unit 103 may select cookies with the cookie name Aa, Bb, or Cc as cookies to be deleted. Note that in deletion method 1, cookies in the cookie list to be deleted that do not have a "size to be deleted" specified may be selected as cookies to be deleted. In this case, selection unit 103 may select cookies with the cookie name Cc as cookies to be deleted.

[0052] [Removal Method 2] The selection unit 103 may select a cookie as a cookie to be deleted if the cookie stored on the terminal 20 is included in the deletion cookie list (deletion target list) and the size of the cookie stored on the terminal 20 is equal to or larger than the "deletion target size" in the deletion cookie list. For example, if the size of cookie Aa stored on the terminal 20 is 0.5 kbytes, the selection unit 103 does not select cookie Aa as a cookie to be deleted. On the other hand, if the size of cookie Aa stored on the terminal 20 is 1.5 kbytes, the selection unit 103 selects cookie Aa as a cookie to be deleted.

[0053] [Removal Method 3] The selection unit 103 may select as cookies to be deleted cookies that are not included in the list of cookies not to be deleted from among the cookies stored in the terminal 20. For example, if the list of cookies not to be deleted includes the cookies shown in B of Fig. 4, the selection unit 103 may select cookies to be deleted from cookies other than cookies Mm, Nn, and Pp.

[0054] [Removal Method 4] The selection unit 103 may select cookies to be deleted from among the cookies stored on the terminal 20 in descending order of data size until the size of the cookies stored on the terminal 20 when the cookies are deleted falls below a predetermined threshold. Note that in the deletion method 4, the selection unit 103 may select cookies to be deleted from among the cookies not included in the list of cookies not to be deleted.

[0055] In addition, the selection unit 103 may select cookies to be deleted according to the above-mentioned deletion methods 1 and / or 2, and if the size of the cookies stored on the terminal 20 when the selected cookies are deleted exceeds a predetermined threshold, it may further execute the deletion method 4.

[0056] For example, suppose that terminal 20 contains cookies A1, A2, and A3, each with a data size of 100 bytes, 200 bytes, and 500 bytes, respectively. Furthermore, suppose that the size of the cookies stored on terminal 20 (more precisely, the size of the cookies valid for the website domain and subdomains under that domain notified in the HTTP request, among all the cookies stored on terminal 20) is 5.5 kbytes. Furthermore, suppose that the predetermined threshold is 5 kbytes. In this case, selection unit 103 selects cookie A3 as a cookie to be deleted, but does not select cookies A1 and A2 as cookie to be deleted. Furthermore, suppose that the size of the cookies stored on terminal 20 is 5.7 kbytes. In this case, selection unit 103 selects cookies A3 and A2 as cookie to be deleted, but does not select cookie A1 as a cookie to be deleted. The predetermined threshold may be referred to as a second threshold.

[0057] Alternatively, selection unit 103 may select cookies to be deleted in the order of deletion method 1, deletion method 2, and deletion method 4. For example, selection unit 103 selects cookies from the deletion cookie list that do not have a deletion target size specified according to deletion method 1 described above. Next, if the size of cookies that would be stored on terminal 20 if the cookies selected according to selection method 1 were deleted exceeds a predetermined threshold, selection unit 103 further selects cookies to be deleted from the deletion cookie list that have a deletion target size specified according to deletion method 2. Next, if the size of cookies that would be stored on terminal 20 if the cookies selected according to deletion method 2 were deleted exceeds the predetermined threshold, selection unit 103 further executes deletion method 4.

[0058] <Summary> According to the embodiment described above, the Web server 10 can delete cookies held by the terminal 20. This makes it possible to provide an information processing device, an information processing method, and a program that enable control of the size of cookies stored in the terminal 20.

[0059] The above-described embodiments are intended to facilitate understanding of the present invention and are not intended to limit the present invention. The flowcharts, sequences, elements included in the embodiments, and their arrangements, materials, conditions, shapes, sizes, etc., described in the embodiments are not limited to those illustrated and can be modified as appropriate. Furthermore, configurations shown in different embodiments can be partially substituted or combined with each other.

[0060] <Additional Notes> (Appendix 1) a receiving unit that receives an HTTP request from a terminal, the HTTP request including a cookie stored in the terminal; a transmission unit that transmits an HTTP response to the terminal; a selection unit that selects, when receiving a request from the terminal, cookies to be deleted from among the cookies stored in the terminal; a deletion processing unit that instructs the terminal to delete the cookie to be deleted selected by the selection unit; An information processing device having the above.

[0061] (Appendix 2) the transmitting unit transmits the HTTP response including a program; the selection unit selects the cookie to be deleted when the request is received from the program transmitted to the terminal. 2. The information processing device according to claim 1.

[0062] (Appendix 3) the program causes the terminal to execute a process of determining whether or not the terminal will make the request; 3. The information processing device according to claim 2.

[0063] (Appendix 4) the transmission unit transmits the HTTP response by including target information indicating a target terminal and / or domain that makes the request; the program causes the terminal to determine whether or not to make the request based on the target information. 4. The information processing device according to claim 3.

[0064] (Appendix 5) The target information is associated with a ratio for each domain, the program causes the terminal to determine whether to make the request based on the ratio when the domain of the HTTP request is included in the target information; 5. The information processing device according to claim 4.

[0065] (Appendix 6) the selection unit selects the cookies to be deleted from the cookies stored on the terminal when the total data size of the cookies stored on the terminal is equal to or larger than a threshold value. 6. An information processing device according to any one of appendices 1 to 5.

[0066] (Appendix 7) the selection unit, when a cookie included in the list of cookies to be deleted is present among the cookies stored on the terminal, selects the cookie as the cookie to be deleted; 7. The information processing device according to any one of appendices 1 to 6.

[0067] (Appendix 8) the selection unit selects, from among the cookies stored in the terminal, cookies that are not included in a list of cookies not to be deleted as the cookies to be deleted; 8. An information processing device according to any one of appendices 1 to 7.

[0068] (Appendix 9) the selection unit selects the cookies to be deleted from among the cookies stored on the terminal in descending order of data size until the size of the cookies stored on the terminal becomes equal to or smaller than a predetermined threshold when the cookies are deleted. An information processing device according to any one of appendices 1 to 8.

[0069] (Appendix 10) a collection unit that collects cookies included in HTTP requests received from multiple terminals; an analysis unit that analyzes the cookies collected by the collection unit on a cookie-by-cookie basis and stores the analysis results in a database; 10. An information processing device according to any one of appendices 1 to 9.

[0070] (Appendix 11) The analysis unit analyzes the minimum data size, average data size, and maximum data size of the collected cookies with the same name and stores the results in the database. 11. The information processing device according to claim 10.

[0071] (Appendix 12) An information processing method executed by an information processing device, receiving an HTTP request from a terminal, the HTTP request including a cookie stored on the terminal; sending an HTTP response to the terminal; selecting a cookie to be deleted from among cookies stored in the terminal when a request is received from the terminal; instructing the terminal to delete the selected cookie to be deleted; An information processing method including:

[0072] (Appendix 13) On the computer, receiving an HTTP request from a terminal, the HTTP request including a cookie stored on the terminal; sending an HTTP response to the terminal; selecting a cookie to be deleted from among cookies stored in the terminal when a request is received from the terminal; instructing the terminal to delete the selected cookie to be deleted; A program to execute. [Explanation of symbols]

[0073] 1 Web system, 10 Web server, 11 Processor, 12 Storage device, 13 Network IF, 14 Input device, 15 Output device, 20 Terminal, 100 Storage unit, 100a Cookie list, 100b Log DB, 100c Cookie collection DB, 100d Cookie management DB, 101 Receiving unit, 102 Transmitting unit, 103 Selecting unit, 104 Deletion processing unit, 105 Collecting unit, 106 Analyzing unit

Claims

1. a receiving unit that receives an HTTP request from a terminal, the HTTP request including a cookie stored in the terminal; a transmitting unit that transmits an HTTP response to the terminal; a selection unit that selects, when receiving a request from the terminal, cookies to be deleted from among the cookies stored in the terminal; a deletion processing unit that instructs the terminal to delete the cookie to be deleted selected by the selection unit; and the selection unit selects the cookies to be deleted from the cookies stored in the terminal based on the data size of the cookies stored in the terminal. Information processing device.

2. the selection unit selects, from among the cookies stored in the terminal, cookies that are not included in a list of cookies not to be deleted as the cookies to be deleted; The information processing device according to claim 1 .

3. a collection unit that collects cookies included in HTTP requests received from a plurality of terminals; an analysis unit that analyzes the cookies collected by the collection unit on a cookie-by-cookie basis and stores the analysis results in a database; The information processing device according to claim 1 .

4. The analysis unit analyzes the minimum data size, average data size, and maximum data size of the collected cookies with the same name and stores the results in the database. The information processing device according to claim 3 .

5. An information processing method executed by an information processing device, receiving an HTTP request from a terminal, the HTTP request including a cookie stored on the terminal; sending an HTTP response to the terminal; selecting a cookie to be deleted from among cookies stored in the terminal when a request is received from the terminal; instructing the terminal to delete the selected cookie to be deleted; Including, the selecting step selects the cookies to be deleted from the cookies stored in the terminal based on the data size of the cookies stored in the terminal; Information processing methods.

6. On the computer, receiving an HTTP request from a terminal, the HTTP request including a cookie stored on the terminal; sending an HTTP response to the terminal; selecting a cookie to be deleted from among cookies stored in the terminal when a request is received from the terminal; instructing the terminal to delete the selected cookie to be deleted; Execute the selecting step selects the cookies to be deleted from the cookies stored in the terminal based on the data size of the cookies stored in the terminal; program.

Images