Cross-site cache data processing method and device, terminal and storage medium

Abstract

The embodiment of the invention discloses a cross-site cache data processing method and device, a terminal and a storage medium, and the method comprises the steps: determining a browser cache cross-site transmission attribute corresponding to a browser, and obtaining a reference website exception list corresponding to the browser cache cross-site transmission attribute; and when the browser receives a cross-site cache transfer request of the reference website for the target website, determining to transfer the target cache data of the target website to the reference website in a cross-site manner based on the browser cache cross-site transfer attribute, the reference website and the reference website exception list. According to the embodiment of the invention, the method is based on the global limitation of the cross-site transmission attribute of the browser cache and the double limitation of the exemption list in the reference website exception list; the cross-site cache data transmission method provided by the embodiment of the invention not only can be compatible with the security problem in cross-site cache data transmission, but also can be compatible with nested login and access behaviors of an old service system.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a cross-site cache data processing method, device, terminal and storage medium. Background Art

[0002] In recent years, with the rapid development of the Internet, browsers have gradually become a common Internet access tool. It is becoming more and more common to use browsers for nested logins and nested accesses to multiple websites. For security reasons, the SameSite attribute corresponding to the website cache data cookie is used to limit the interactive behavior of cross-site website cache data. However, using the SameSite attribute corresponding to the website cache data cookie to limit the interactive behavior of cross-site website cache data makes the browser incompatible with some old business systems. For example, nested logins and access based on old business systems will not be possible. Summary of the invention

[0003] The embodiments of the present application provide a cross-site cache data processing method, device, terminal and storage medium, which can solve the technical problem of limiting the interactive behavior of cross-site website cache data through the SameSite attribute corresponding to the website cache data cookie, making the browser incompatible with some old business systems.

[0004] In a first aspect, an embodiment of the present application provides a method for cross-site cache data transmission, the method comprising:

[0005] Determine a browser cache cross-site transfer attribute corresponding to the browser, and obtain a reference website exception list corresponding to the browser cache cross-site transfer attribute;

[0006] When the browser receives a cross-site cache transfer request from a reference website to a target website, based on the browser cache cross-site transfer attribute, the reference website and the reference website exception list, it is determined to cross-site transfer the target cache data of the target website to the reference website.

[0007] Optionally, obtaining a reference website exception list corresponding to the browser cache cross-site transfer attribute includes:

[0008] Determine the cross-site transfer type of the browser cache cross-site transfer attribute;

[0009] If the cross-site transfer type is a cross-site transfer allowed type, obtaining a cross-site transfer allowed exception list of the website;

[0010] If the cross-site transfer type is a cross-site transfer rejection type, then a cross-site transfer rejection exception list of the website is obtained.

[0011] Optionally, the determining to transfer the target cache data of the target website to the reference website across sites based on the browser cache cross-site transfer attribute, the reference website and the reference website exception list includes:

[0012] Performing list matching processing on the reference website based on the reference website exception list to obtain a list matching result;

[0013] Based on the list matching result and the reference website exception list, it is determined to transfer the target cache data of the target website to the reference website across sites.

[0014] Optionally, determining to transfer the target cache data of the target website to the reference website across sites based on the list matching result and the reference website exception list includes:

[0015] If the reference website exception list is a website cross-site transfer exception list and the list matching result is a list mismatch type, determining to cross-site transfer the target cache data of the target website to the reference website;

[0016] If the reference website exception list is a website rejection cross-site transfer exception list and the list matching result is a list matching type, it is determined to cross-site transfer the target cache data of the target website to the reference website.

[0017] Optionally, the method further comprises:

[0018] If the reference website exception list is a website cross-site transfer exception list and the list matching result is a list matching type, then the target cache data of the target website is prohibited from being transferred across sites to the reference website;

[0019] If the reference website exception list is a website rejection cross-site transfer exception list and the list matching result is a list mismatch type, cross-site transfer of the target cache data of the target website to the reference website is prohibited.

[0020] Optionally, the prohibiting the target cache data of the target website from being transferred across sites to the reference website includes:

[0021] Determine the cross-site transfer type of the browser cache cross-site transfer attribute;

[0022] If the cross-site transfer type is a cross-site transfer rejection type, the target cache data of the target website is prohibited from being transferred across the site to the reference website;

[0023] If the cross-site transfer type is a type that allows cross-site transfer, a browser cache cross-site transfer attribute configuration process is performed on the target website to prohibit the target cache data of the target website from being transferred across sites to the reference website.

[0024] Optionally, performing browser cache cross-site transfer attribute configuration processing on the target website to prohibit cross-site transfer of target cache data of the target website to the reference website includes:

[0025] For the target website, modify the browser cache cross-site transfer attribute of the browser to a cross-site transfer rejection type to prohibit the target cache data of the target website from being transferred across sites to the reference website; or,

[0026] A temporary browser cache cross-site transfer attribute is newly created for the target website, and the temporary browser cache cross-site transfer attribute is set to a temporary cross-site transfer rejection type, so that after the cross-site cache transfer request fails, the temporary cross-site transfer rejection type is unconfigured.

[0027] Optionally, the determining to transfer the target cache data of the target website to the reference website across sites includes:

[0028] Determine the cross-site transfer type of the browser cache cross-site transfer attribute;

[0029] If the cross-site transfer type is a type that allows cross-site transfer, the target cache data of the target website is transferred across the site to the reference website;

[0030] If the cross-site transfer type is a cross-site transfer rejection type, a browser cache cross-site transfer attribute configuration process is performed on the target website to cross-site transfer the target cache data of the target website to the reference website.

[0031] Optionally, performing browser cache cross-site transfer attribute configuration processing on the target website to transfer target cache data of the target website to the reference website across sites includes:

[0032] For the target website, modify the browser cache cross-site transfer attribute of the browser to allow cross-site transfer type, so as to transfer the target cache data of the target website to the reference website across sites; or,

[0033] A temporary browser cache cross-site transfer attribute is newly created for the target website, and the temporary browser cache cross-site transfer attribute is set to a temporary allowed cross-site transfer type to transfer the target cache data of the target website across the site to the reference website, and the temporary allowed cross-site transfer type is unconfigured after the target cache data is transferred.

[0034] In a second aspect, an embodiment of the present application provides a cross-site cache data processing device, the device comprising:

[0035] A determination module, adapted to determine a browser cache cross-site transfer attribute corresponding to the browser, and obtain a reference website exception list corresponding to the browser cache cross-site transfer attribute;

[0036] The access module is adapted to determine, when the browser receives a cross-site cache transfer request from a reference website to a target website, to transfer the target cache data of the target website to the reference website across sites based on the browser cache cross-site transfer attribute, the reference website and the reference website exception list.

[0037] Optionally, the determination module is adapted to determine a cross-site transfer type of the browser cache cross-site transfer attribute;

[0038] If the cross-site transfer type is a cross-site transfer allowed type, obtaining a cross-site transfer allowed exception list of the website;

[0039] If the cross-site transfer type is a cross-site transfer rejection type, then a cross-site transfer rejection exception list of the website is obtained.

[0040] Optionally, the access module is adapted to perform list matching processing on the reference website based on the reference website exception list to obtain a list matching result;

[0041] Based on the list matching result and the reference website exception list, it is determined to transfer the target cache data of the target website to the reference website across sites.

[0042] Optionally, the access module is adapted to determine to transfer the target cache data of the target website across sites to the reference website if the reference website exception list is a website allowed cross-site transfer exception list and the list matching result is a list mismatch type;

[0043] If the reference website exception list is a website rejection cross-site transfer exception list and the list matching result is a list matching type, it is determined to cross-site transfer the target cache data of the target website to the reference website.

[0044] Optionally, the access module is further adapted to prohibit the cross-site transfer of the target cache data of the target website to the reference website if the reference website exception list is a website cross-site transfer allowed exception list and the list matching result is a list matching type;

[0045] If the reference website exception list is a website rejection cross-site transfer exception list and the list matching result is a list mismatch type, cross-site transfer of the target cache data of the target website to the reference website is prohibited.

[0046] Optionally, the access module is further adapted to determine a cross-site transfer type of the browser cache cross-site transfer attribute;

[0047] If the cross-site transfer type is a cross-site transfer rejection type, the target cache data of the target website is prohibited from being transferred across the site to the reference website;

[0048] If the cross-site transfer type is a type that allows cross-site transfer, a browser cache cross-site transfer attribute configuration process is performed on the target website to prohibit the target cache data of the target website from being transferred across sites to the reference website.

[0049] Optionally, the access module is further adapted to modify the browser cache cross-site transfer attribute of the browser to a cross-site transfer rejection type for the target website, so as to prohibit the cross-site transfer of the target cache data of the target website to the reference website; or,

[0050] A temporary browser cache cross-site transfer attribute is newly created for the target website, and the temporary browser cache cross-site transfer attribute is set to a temporary cross-site transfer rejection type, so that after the cross-site cache transfer request fails, the temporary cross-site transfer rejection type is unconfigured.

[0051] Optionally, the access module is further adapted to determine a cross-site transfer type of the browser cache cross-site transfer attribute;

[0052] If the cross-site transfer type is a type that allows cross-site transfer, the target cache data of the target website is transferred across the site to the reference website;

[0053] If the cross-site transfer type is a cross-site transfer rejection type, performing browser cache cross-site transfer attribute configuration processing on the target website to cross-site transfer the target cache data of the target website to the reference website;

[0054] Optionally, the access module is further adapted to modify the browser cache cross-site transfer attribute of the browser to allow cross-site transfer type for the target website, so as to transfer the target cache data of the target website to the reference website across sites; or,

[0055] A temporary browser cache cross-site transfer attribute is newly created for the target website, and the temporary browser cache cross-site transfer attribute is set to a temporary allowed cross-site transfer type to transfer the target cache data of the target website across the site to the reference website, and the temporary allowed cross-site transfer type is unconfigured after the target cache data is transferred.

[0056] The beneficial effects brought about by the technical solutions provided in some embodiments of the present application include at least:

[0057] An embodiment of the present application provides a method for cross-site cache data transmission. First, the browser cache cross-site transmission attribute corresponding to the browser is determined. The browser cache cross-site transmission attribute is used to control the browser to globally control whether cross-site cache data transmission is allowed. Then, a reference website exception list corresponding to the browser cache cross-site transmission attribute is obtained. Each browser cache cross-site transmission attribute has its own corresponding reference website exception list. The reference website exception list is not subject to the browser's global restriction of allowing or denying cross-site cache data transmission, thereby avoiding all cross-site cache data transmissions being denied or allowed.

[0058] Finally, when the browser receives a cross-site cache transfer request from the reference website to the target website, based on the browser cache cross-site transfer attributes, the reference website and the reference website exception list, it is determined to cross-site transfer the target cache data of the target website to the reference website. Based on the dual restrictions of the global restrictions on the browser cache cross-site transfer attributes and the exemption list in the reference website exception list, the cross-site cache data transfer method provided in the embodiment of the present application is compatible with both the security issues in cross-site cache data transfer and the nested login and access behaviors of legacy business systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without paying any creative work.

[0060] Figure 1 An exemplary system architecture diagram of a cross-site cache data transmission method provided in an embodiment of the present application;

[0061] Figure 2 A schematic diagram of a flow chart of a cross-site cache data transmission method provided in an embodiment of the present application;

[0062] Figure 3 A schematic diagram of a process for obtaining a reference website exception list corresponding to a browser cache cross-site transfer attribute provided in an embodiment of the present application;

[0063] Figure 4 A schematic diagram of a process for transferring target cache data of a target website to a reference website across sites provided by an embodiment of the present application;

[0064] Figure 5A schematic diagram of another process of transferring target cache data of a target website to a reference website across sites provided by an embodiment of the present application;

[0065] Figure 6 A schematic diagram of a process for prohibiting target cache data of a target website from being transferred across sites to a reference website provided by an embodiment of the present application;

[0066] Figure 7 A schematic diagram of the structure of a cross-site cache data processing device provided in an embodiment of the present application;

[0067] Figure 8 A schematic diagram of the structure of a terminal provided in an embodiment of the present application. DETAILED DESCRIPTION

[0068] In order to make the features and advantages of the embodiments of the present application more obvious and easy to understand, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of them. Based on the embodiments in the embodiments of the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the embodiments of the present application.

[0069] With the rapid development of information technology and the Internet, browsers have gradually become the mainstream Internet access tool. When users use browsers to surf the Internet, they will encounter nested logins and nested accesses to multiple websites. Nested logins and nested accesses generally involve the transmission of cached data across websites. In order to avoid leakage of user data in the transmission of cached data across websites, which affects the user's information security. At present, based on security considerations, the SameSite attribute corresponding to the website cache data cookie can be used to limit the interactive behavior of cached data across websites. Commonly, for security considerations, the browser engine Chromium adjusts the SameSite attribute to Lax during the evolution process, which can alleviate CSRF (cross-site request forgery) attacks to a certain extent, but the new problem introduced is that the browser will not be compatible with some old business systems. In order to be compatible with old business systems, traditional browser manufacturers usually set the SameSite attribute to None and keep it unchanged, which is not compatible with security.

[0070] In order to solve the above technical problems, an embodiment of the present application provides a cross-site cache data transmission method. First, a browser cache cross-site transmission attribute corresponding to the browser is determined. The browser cache cross-site transmission attribute is used to control the browser to globally control whether cross-site cache data transmission is allowed. Then, a reference website exception list corresponding to the browser cache cross-site transmission attribute is obtained. Each browser cache cross-site transmission attribute has its own corresponding reference website exception list. The reference website exception list is not restricted by the browser's global permission or rejection of cross-site cache data transmission, thereby avoiding that all cross-site cache data transmissions are rejected or allowed. Finally, when the browser receives a cross-site cache transmission request from a reference website for a target website, based on the browser cache cross-site transmission attribute, the reference website and the reference website exception list, it is determined to cross-site transmit the target cache data of the target website to the reference website. Based on the dual restrictions of the global restrictions of the browser cache cross-site transmission attribute and the exemption list in the reference website exception list, the cross-site cache data transmission method provided by the embodiment of the present application can be compatible with both the security issues in cross-site cache data transmission and the nested login and access behaviors of old business systems.

[0071] See also Figure 1 , Figure 1 An exemplary system architecture diagram of a cross-site cache data transmission method provided in an embodiment of the present application.

[0072] like Figure 1 As shown, the system architecture may include a terminal 101, a network 102, and a server 103. The network 102 is used to provide a medium for a communication link between the terminal 101 and the server 103. The network 102 may include various types of wired communication links or wireless communication links, for example, the wired communication link includes an optical fiber, a twisted pair, or a coaxial cable, and the wireless communication link includes a Bluetooth communication link, a Wireless-Fidelity (Wi-Fi) communication link, or a microwave communication link.

[0073] The terminal 101 can interact with the server 103 through the network 102 to receive messages from the server 103 or send messages to the server 103, or the terminal 101 can interact with the server 103 through the network 102 to receive messages or data sent by other users to the server 103. The terminal 101 can be hardware or software. When the terminal 101 is hardware, it can be various terminals, including but not limited to smart watches, smart phones, tablet computers, laptop portable computers and desktop computers. When the terminal 101 is software, it can be installed in the terminals listed above, which can be implemented as multiple software or software modules (for example: used to provide distributed services), or it can be implemented as a single software or software module, which is not specifically limited here.

[0074] In an embodiment of the present application, terminal 101 can determine the browser cache cross-site transfer attribute corresponding to the browser, and obtain the reference website exception list corresponding to the browser cache cross-site transfer attribute; thereafter, when the browser receives a cross-site cache transfer request from the reference website for the target website, based on the browser cache cross-site transfer attribute, the reference website and the reference website exception list, it is determined to cross-site transfer the target cache data of the target website to the reference website.

[0075] The server 103 may be a business server that provides various services. It should be noted that the server 103 may be hardware or software. When the server 103 is hardware, it may be implemented as a distributed server cluster consisting of multiple servers, or it may be implemented as a single server. When the server 103 is software, it may be implemented as multiple software or software modules (for example, for providing distributed services), or it may be implemented as a single software or software module, which is not specifically limited here.

[0076] Alternatively, the system architecture may not include the server 103. In other words, the server 103 may be an optional device in the embodiments of this specification. That is, the method provided in the embodiments of this specification may be applied to a system structure that only includes the terminal 101, and the embodiments of this application do not limit this.

[0077] It should be understood that Figure 1 The number of terminals, networks and servers in the figure is only for illustration and any number of terminals, networks and servers may be used according to implementation requirements.

[0078] See also Figure 2 , Figure 2 A flow chart of a cross-site cache data delivery method provided for an embodiment of the present application. The execution subject of the embodiment of the present application can be a terminal that executes the cross-site cache data delivery method, or a processor in the terminal that executes the cross-site cache data delivery method, or a cross-site cache data delivery service in the terminal that executes the cross-site cache data delivery method. For the convenience of description, the specific execution process of the cross-site cache data delivery method is introduced below by taking the execution subject being the processor in the terminal as an example.

[0079] S202: Determine a browser cache cross-site transfer attribute corresponding to the browser, and obtain a reference website exception list corresponding to the browser cache cross-site transfer attribute.

[0080] The browser cache cross-site transfer attribute is used to control whether the browser allows cross-site cache data transfer globally. In the browser's function setting page, you can set the function control item of the browser cache cross-site transfer attribute visually, so that users can directly set the browser cache cross-site transfer attribute in the function setting page. In addition, after the browser cache cross-site transfer attribute is set, it can be stored in the database and is still valid after the browser is restarted. Here, the form of the database includes but is not limited to profile (user configuration file), local storage (local storage), session storage (session storage), IndexedDB (front-end cache).

[0081] After the user starts the browser, the processor determines the browser cache cross-site transfer attribute corresponding to the browser, and obtains the reference website exception list corresponding to the browser cache cross-site transfer attribute. Each browser cache cross-site transfer attribute has its own corresponding reference website exception list. The reference website exception list is not subject to the browser's global permission or rejection of cross-site cache data transfer, thereby avoiding all cross-site cache data transfers from being rejected or allowed, and avoiding all cross-site cache data transfers from being rejected or allowed, thereby preparing for the subsequent control of whether the website on the browser sends website cache data across sites.

[0082] It should be noted that cross-site refers to the two URLs (Uniform Resource Locators) whose eTLD (effective top level domain) + 1 is different. eTLD + 1 here refers to the effective top level domain + the second level domain. For example, the effective top level domain can be ".com", ".org" and ".info", and eTLD + 1 can be "abc.com", "abc.org" and "abc.info".

[0083] Here, the reference website exception list corresponding to the browser cache cross-site transfer attribute can be updated regularly, and can also be updated in a personalized manner based on the needs of the user. Based on the reference website exception update list issued by the reference website exception list management platform, the reference website exception list stored in the terminal where the browser is located can be updated. The reference website exception list management platform can be connected to multiple terminals to achieve batch updates. Of course, the terminal where the browser is located can respond to the user's update operation on the reference website exception list and update the reference website exception list stored in the terminal where the browser is located to achieve personalized updates based on the actual needs of the user.

[0084] See also Figure 3 , Figure 3A flowchart of obtaining a reference website exception list corresponding to a browser cache cross-site transfer attribute is provided in an embodiment of the present application.

[0085] like Figure 3 As shown, optionally, obtaining a reference website exception list corresponding to the browser cache cross-site transfer attribute in step S202 includes:

[0086] S302: Determine the cross-site transfer type of the browser cache cross-site transfer attribute.

[0087] The browser cache cross-site transfer attribute is a global attribute for each website opened in the browser. The cross-site transfer type of the browser cache cross-site transfer attribute can include the type of allowing cross-site transfer and the type of rejecting cross-site transfer. When the cross-site transfer type of the browser cache cross-site transfer attribute is the type of allowing cross-site transfer, the global SameSite corresponding to the browser can be None, and each website opened in the browser generally allows cross-site transfer of website cache data, of course, except for the website cache data corresponding to each website in the website's allowed cross-site transfer exception list. In other words, the website cache data corresponding to each website in the website's allowed cross-site transfer exception list is rejected for cross-site transfer of website cache data, that is, the SameSite of the corresponding website cache data can be modified to Lax. Here, the website's allowed cross-site transfer exception list can be a website that includes user personal data and a website that has transaction data, etc., to avoid leakage of user personal information.

[0088] When the cross-site transfer type of the browser cache cross-site transfer attribute is the cross-site transfer rejection type, the global SameSite corresponding to the browser can be Lax, and the websites opened in the browser generally refuse to perform cross-site transfer of website cache data, of course, except for the website cache data corresponding to each website in the website rejection cross-site transfer exception list. In other words, each website in the website rejection cross-site transfer exception list can perform cross-site transfer of website cache data, that is, the SameSite of the corresponding website cache data can be modified to None. Here, the website rejection cross-site transfer exception list can include websites that require cross-site transfer of website cache data for users to browse the website, such as the need for cross-site transfer of website cache data when developers develop web pages.

[0089] S304: If the cross-site transfer type is a cross-site transfer allowed type, obtain a cross-site transfer allowed exception list of the website.

[0090] The user can set the browser cache cross-site transfer attribute corresponding to the browser to the allow cross-site transfer type. When the cross-site transfer type is the allow cross-site transfer type, the website allow cross-site transfer exception list corresponding to the allow cross-site transfer type can be obtained. Here, the websites in the website allow cross-site transfer exception list are not affected by the browser cache cross-site transfer attribute being the allow cross-site transfer type after being opened by the browser.

[0091] S306: If the cross-site transfer type is a cross-site transfer rejection type, obtain a cross-site transfer rejection exception list of the website.

[0092] The user can set the browser cache cross-site transfer attribute corresponding to the browser to the deny cross-site transfer type. When the cross-site transfer type is the deny cross-site transfer type, the website deny cross-site transfer exception list corresponding to the deny cross-site transfer type can be obtained. Here, the websites in the website deny cross-site transfer exception list are also not affected by the browser cache cross-site transfer attribute being the deny cross-site transfer type after being opened by the browser.

[0093] S204: When the browser receives a cross-site cache transfer request from the reference website to the target website, based on the browser cache cross-site transfer attribute, the reference website and the reference website exception list, determine to cross-site transfer the target cache data of the target website to the reference website.

[0094] When a user browses a website based on a browser, when the browser receives a cross-site cache transfer request from a reference website to a target website, the reference website can be judged based on the browser cache cross-site transfer attribute and the reference website exception list to determine whether to send the website cache data corresponding to the reference website to the target website. When the reference website is judged based on the browser cache cross-site transfer attribute and the reference website exception list, the website cache data corresponding to the reference website can be sent to the target website, and it is determined to cross-site transfer the target cache data of the target website to the reference website. Here, based on the dual restrictions of the global restrictions on the browser cache cross-site transfer attribute and the exemption list in the reference website exception list, the cross-site cache data transfer method provided in the embodiment of the present application can be compatible with both the security issues in cross-site cache data transfer and the nested login and access behaviors of legacy business systems.

[0095] See also Figure 4 , Figure 4 A schematic diagram of a process for cross-site transmission of target cache data of a target website to a reference website is provided in an embodiment of the present application.

[0096] like Figure 4 As shown, optionally, in step S204, based on the browser cache cross-site transfer attribute, the reference website and the reference website exception list, determining to cross-site transfer the target cache data of the target website to the reference website includes:

[0097] S402: performing list matching processing on the reference website based on the reference website exception list to obtain a list matching result.

[0098] When the cross-site transfer type is the cross-site transfer type that allows, the reference website exception list at this time is the website cross-site transfer exception list that allows, and at this time, the reference website can be matched based on the website cross-site transfer exception list to obtain a list matching result; when the cross-site transfer type is the cross-site transfer rejection type, the reference website exception list at this time is the website cross-site transfer rejection exception list, and at this time, the reference website can be matched based on the website cross-site transfer rejection exception list to obtain a list matching result.

[0099] S404: Based on the list matching result and the reference website exception list, determine to transfer the target cache data of the target website to the reference website across sites.

[0100] Optionally, in step S404, based on the list matching result and the reference website exception list, determining to transfer the target cache data of the target website to the reference website across sites includes:

[0101] If the reference website exception list is a website cross-site transfer exception list and the list matching result is a list mismatch type, it is determined to cross-site transfer the target cache data of the target website to the reference website;

[0102] If the reference website exception list is a website rejection cross-site transfer exception list and the list matching result is a list matching type, it is determined that the target cache data of the target website is transferred cross-site to the reference website.

[0103] Determining to transfer the target cache data of the target website across sites to the reference website corresponds to two situations. In the first situation, when the cross-site transfer type is the cross-site transfer allowed type, the reference website exception list is the website cross-site transfer allowed exception list, and the websites in the website cross-site transfer allowed exception list are not affected by the cross-site transfer allowed type, that is, the websites in the website cross-site transfer allowed exception list are denied cross-site transfer of website cache data. Therefore, when the match result with the cross-site transfer allowed exception list is a list mismatch type, it is determined that the target cache data of the target website is transferred across sites to the reference website.

[0104] In the second case, when the cross-site transfer type is the cross-site transfer rejection type, the reference website exception list is the website cross-site transfer rejection exception list, and the websites in the website cross-site transfer rejection exception list are not affected by the cross-site transfer rejection type, that is, the websites in the website cross-site transfer rejection exception list are allowed to cross-site transfer the website cache data. Therefore, when the matching result with the cross-site transfer rejection exception list is a list match type, it is determined that the target cache data of the target website is transferred cross-site to the reference website.

[0105] See also Figure 5 , Figure 5 Another flowchart of transferring target cache data of a target website to a reference website across sites is provided in an embodiment of the present application.

[0106] like Figure 5 As shown, optionally, determining in step S204 to transfer the target cache data of the target website to the reference website across sites includes:

[0107] S502: Determine the cross-site transfer type of the browser cache cross-site transfer attribute.

[0108] After the browser is started, the user can set the browser cache cross-site transfer properties to update the current browser cache cross-site transfer properties. The browser can also obtain the browser cache cross-site transfer properties of the previous browser from the database used to store the browser cache cross-site transfer properties to adapt to the user's usage habits. Afterwards, the processor determines the cross-site transfer type of the browser cache cross-site transfer properties. The cross-site transfer type includes the allowed cross-site transfer type and the rejected cross-site transfer type.

[0109] S504: If the cross-site transfer type is a cross-site transfer allowed type, the target cache data of the target website is cross-site transferred to the reference website.

[0110] When the cross-site transfer type is the cross-site transfer allowed type, and based on the reference website exception list, it is determined that the reference website is allowed to cross-site transfer the target cache data of the target website to the reference website, the target cache data of the target website is cross-site transferred to the reference website.

[0111] S506: If the cross-site transfer type is a cross-site transfer rejection type, a browser cache cross-site transfer attribute configuration process is performed on the target website to cross-site transfer the target cache data of the target website to the reference website.

[0112] When the cross-site transfer type is the cross-site transfer rejection type, and based on the reference website exception list, it is determined that the reference website is allowed to cross-site transfer the target cache data of the target website to the reference website, the browser cache cross-site transfer attribute configuration processing is performed on the target website to cross-site transfer the target cache data of the target website to the reference website.

[0113] Optionally, in step S506, performing browser cache cross-site transfer attribute configuration processing on the target website to cross-site transfer the target cache data of the target website to the reference website includes:

[0114] For the target website, the browser cache cross-site transfer property of the browser is modified to allow cross-site transfer type, so as to transfer the target cache data of the target website to the reference website across sites.

[0115] On the premise that the reference website is allowed to pass the target cache data of the target website across sites to the reference website based on the reference website exception list, when the target cache data of the target website needs to be passed across sites to the reference website, the browser cache cross-site transfer property of the browser can also be modified to allow cross-site transfer type for the target website. It should be noted that the allow cross-site transfer type here is open to the target website so as to pass the target cache data of the target website across sites to the reference website.

[0116] Of course, in step S506, the browser cache cross-site transfer attribute configuration processing is performed on the target website to transfer the target cache data of the target website to the reference website across the site, which may also include:

[0117] Create a temporary browser cache cross-site transfer attribute for the target website, set the temporary browser cache cross-site transfer attribute to the temporary allow cross-site transfer type to transfer the target cache data of the target website across sites to the reference website, and unconfigure the temporary allow cross-site transfer type after the target cache data is transferred.

[0118] The temporary browser cache cross-site transfer attribute can be newly created in the cache space corresponding to the browser, and the browser cache cross-site transfer attribute configuration processing for the target website can be to create a temporary browser cache cross-site transfer attribute corresponding to the target website on the terminal side corresponding to the browser. Of course, the temporary browser cache cross-site transfer attribute can be obtained from the browser cache cross-site transfer attribute corresponding to the target website on the server side. When the browser cache cross-site transfer attribute corresponding to the target website on the server side is different from the expected temporary browser cache cross-site transfer attribute, the local temporary browser cache cross-site transfer attribute can be modified. For example, the local corresponding SameSite attribute of the website cache data is modified from Lax to None, thereby setting the temporary browser cache cross-site transfer attribute to a temporary allowed cross-site transfer type. And after the cross-site cache transfer request fails, the temporary rejection of the cross-site transfer type can be canceled to save the memory space occupied by the browser.

[0119] In addition, in other embodiments provided by the present application, the cross-site cache data transmission method also includes:

[0120] If the reference website exception list is a website cross-site transfer exception list and the list matching result is a list matching type, cross-site transfer of the target cache data of the target website to the reference website is prohibited;

[0121] If the reference website exception list is a website rejection cross-site transfer exception list and the list matching result is a list mismatch type, cross-site transfer of the target cache data of the target website to the reference website is prohibited.

[0122] There are two situations where the cross-site transfer of the target cache data of the target website to the reference website is prohibited. In the first situation, when the cross-site transfer type is the cross-site transfer type allowed, the reference website exception list is the website cross-site transfer exception list allowed, and the websites in the website cross-site transfer exception list allowed are not affected by the cross-site transfer type allowed, that is, the websites in the website cross-site transfer exception list allowed are denied cross-site transfer of the website cache data. Therefore, when the matching result with the cross-site transfer exception list allowed is the list match type, the cross-site transfer of the target cache data of the target website to the reference website is prohibited.

[0123] In the second case, when the cross-site transfer type is the cross-site transfer rejection type, the reference website exception list is the website cross-site transfer rejection exception list, and the websites in the website cross-site transfer rejection exception list are not affected by the cross-site transfer rejection type, that is, the websites in the website cross-site transfer rejection exception list are allowed to cross-site transfer website cache data. Therefore, when the match result with the cross-site transfer rejection exception list is a list mismatch type, it is prohibited to cross-site transfer the target cache data of the target website to the reference website.

[0124] See also Figure 6 , Figure 6 A flowchart for prohibiting cross-site transmission of target cache data of a target website to a reference website is provided in an embodiment of the present application.

[0125] Optionally, prohibit the target cache data of the target website from being passed across sites to the reference website, including:

[0126] S602: Determine the cross-site transfer type of the browser cache cross-site transfer attribute.

[0127] The specific content of step S602 may refer to the description of step S502.

[0128] S604: If the cross-site transfer type is a cross-site transfer rejection type, cross-site transfer of the target cache data of the target website to the reference website is prohibited.

[0129] When the cross-site transfer type is the cross-site transfer rejection type, and based on the reference website exception list, it is determined that the reference website is rejected from cross-site transfer of the target cache data of the target website to the reference website, then cross-site transfer of the target cache data of the target website to the reference website is prohibited.

[0130] S606: If the cross-site transfer type is the cross-site transfer allowed type, a browser cache cross-site transfer attribute configuration process is performed on the target website to prohibit the target cache data of the target website from being transferred across the site to the reference website.

[0131] When the cross-site transfer type is the cross-site transfer type allowed, and based on the reference website exception list, it is determined that the reference website is denied cross-site transfer of the target cache data of the target website to the reference website, the browser cache cross-site transfer attribute configuration processing is performed on the target website to prohibit the cross-site transfer of the target cache data of the target website to the reference website.

[0132] Optionally, in step S606, the target website is subjected to a browser cache cross-site transfer attribute configuration process to prohibit the target cache data of the target website from being transferred across sites to the reference website, including:

[0133] For the target website, the browser cache cross-site transfer property of the browser is modified to the deny cross-site transfer type to prohibit the target cache data of the target website from being transferred across sites to the reference website.

[0134] On the premise that the reference website is denied cross-site transmission of the target cache data of the target website to the reference website based on the reference website exception list, when the target cache data of the target website is denied cross-site transmission to the reference website, the browser cache cross-site transmission attribute of the browser can be modified to the deny cross-site transmission type for the target website. It should be noted that the deny cross-site transmission type here is open to the target website to prohibit the cross-site transmission of the target cache data of the target website to the reference website.

[0135] Of course, in step S606, the browser cache cross-site transfer attribute configuration processing is performed on the target website to prohibit the target cache data of the target website from being transferred across the site to the reference website, and further includes:

[0136] Create a temporary browser cache cross-site transfer attribute for the target website, set the temporary browser cache cross-site transfer attribute to the temporary cross-site transfer rejection type, so that after the cross-site cache transfer request fails, the temporary cross-site transfer rejection type can be unconfigured.

[0137] In this embodiment, the temporary browser cache cross-site transfer attribute can also be newly created in the cache space corresponding to the browser, and the browser cache cross-site transfer attribute configuration processing for the target website can be to create a temporary browser cache cross-site transfer attribute corresponding to the target website on the terminal side corresponding to the browser. In addition, the temporary browser cache cross-site transfer attribute can be obtained from the browser cache cross-site transfer attribute corresponding to the target website on the server side. When the browser cache cross-site transfer attribute corresponding to the target website on the server side is different from the expected temporary browser cache cross-site transfer attribute, the local temporary browser cache cross-site transfer attribute can be modified. For example, the local corresponding SameSite attribute of the website cache data is modified from None to Lax, thereby setting the temporary browser cache cross-site transfer attribute to a temporary rejection of cross-site transfer type. And after the cross-site cache transfer request fails, the temporary rejection of cross-site transfer type can be canceled. The memory space occupied by the browser can be saved.

[0138] An embodiment of the present application also provides a computer-readable storage medium, which can store multiple instructions, and the instructions are suitable for being loaded by a processor and executing the steps of any method in the above embodiments.

[0139] See also Figure 7 , Figure 7 A schematic diagram of the structure of a cross-site cache data processing device provided in an embodiment of the present application.

[0140] The embodiment of the present application provides a cross-site cache data processing device 700, which includes:

[0141] A determination module 710 is adapted to determine a browser cache cross-site transfer attribute corresponding to the browser, and obtain a reference website exception list corresponding to the browser cache cross-site transfer attribute;

[0142] The access module 720 is adapted to determine to cross-site transfer the target cache data of the target website to the reference website based on the browser cache cross-site transfer attribute, the reference website and the reference website exception list when the browser receives a cross-site cache transfer request from the reference website to the target website.

[0143] Optionally, the determination module 710 is adapted to determine a cross-site transfer type of the browser cache cross-site transfer attribute;

[0144] If the cross-site transmission type is the cross-site transmission allowed type, obtain the website's cross-site transmission exception list;

[0145] If the cross-site transfer type is a cross-site transfer rejection type, obtain the website's cross-site transfer rejection exception list.

[0146] Optionally, the access module 720 is adapted to perform list matching processing on the reference website based on the reference website exception list to obtain a list matching result;

[0147] Based on the list matching results and the reference website exception list, determine to pass the target cache data of the target website across sites to the reference website.

[0148] Optionally, the access module 720 is adapted to determine to transfer the target cache data of the target website across sites to the reference website if the reference website exception list is a website cross-site transfer allowed exception list and the list matching result is a list mismatch type;

[0149] If the reference website exception list is a website rejection cross-site transfer exception list and the list matching result is a list matching type, it is determined that the target cache data of the target website is transferred cross-site to the reference website.

[0150] Optionally, the access module 720 is further adapted to prohibit the cross-site transfer of the target cache data of the target website to the reference website if the reference website exception list is a website cross-site transfer allowed exception list and the list matching result is a list matching type;

[0151] If the reference website exception list is a website rejection cross-site transfer exception list and the list matching result is a list mismatch type, cross-site transfer of the target cache data of the target website to the reference website is prohibited.

[0152] Optionally, the access module 720 is further adapted to determine the cross-site transfer type of the browser cache cross-site transfer attribute;

[0153] If the cross-site transfer type is the cross-site transfer rejection type, the target cache data of the target website is prohibited from being transferred across sites to the reference website;

[0154] If the cross-site transfer type is the cross-site transfer type allowed, the browser cache cross-site transfer attribute configuration processing is performed on the target website to prohibit the target cache data of the target website from being transferred across the site to the reference website.

[0155] Optionally, the access module 720 is further adapted to modify the browser cache cross-site transfer attribute of the browser to a cross-site transfer rejection type for the target website, so as to prohibit the cross-site transfer of the target cache data of the target website to the reference website; or,

[0156] Create a temporary browser cache cross-site transfer attribute for the target website, set the temporary browser cache cross-site transfer attribute to the temporary cross-site transfer rejection type, so that after the cross-site cache transfer request fails, the temporary cross-site transfer rejection type can be unconfigured.

[0157] Optionally, the access module 720 is further adapted to determine the cross-site transfer type of the browser cache cross-site transfer attribute;

[0158] If the cross-site transfer type is a type that allows cross-site transfer, the target cache data of the target website is transferred across the site to the reference website;

[0159] If the cross-site transfer type is a cross-site transfer rejection type, a browser cache cross-site transfer attribute configuration process is performed on the target website to transfer the target cache data of the target website to the reference website across the site;

[0160] Optionally, the access module 720 is further adapted to modify the browser cache cross-site transfer attribute of the browser to allow cross-site transfer type for the target website, so as to transfer the target cache data of the target website to the reference website across the site; or,

[0161] Create a temporary browser cache cross-site transfer attribute for the target website, set the temporary browser cache cross-site transfer attribute to the temporary allow cross-site transfer type to transfer the target cache data of the target website across sites to the reference website, and unconfigure the temporary allow cross-site transfer type after the target cache data is transferred.

[0162] See also Figure 8 , Figure 8 A schematic diagram of the structure of a terminal provided in an embodiment of the present application. Figure 8 As shown, the terminal 800 may include: at least one processor 801 , at least one network interface 804 , a user interface 803 , a memory 805 , and at least one communication bus 802 .

[0163] The communication bus 802 is used to realize the connection and communication between these components.

[0164] The user interface 803 may include a display screen (Display) and a camera (Camera), and the optional user interface 803 may also include a standard wired interface and a wireless interface.

[0165] The network interface 804 may optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).

[0166] Among them, the processor 801 may include one or more processing cores. The processor 801 uses various interfaces and lines to connect various parts in the entire terminal 800, and executes various functions and processes data of the terminal 800 by running or executing instructions, programs, code sets or instruction sets stored in the memory 805, and calling data stored in the memory 805. Optionally, the processor 801 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA). The processor 801 can integrate one or a combination of a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 801, and it can be implemented separately through a chip.

[0167] Among them, the memory 805 may include a random access memory (Random Access Memory, RAM) and may also include a read-only memory (Read-Only Memory, ROM). Optionally, the memory 805 includes a non-transitory computer-readable storage medium. The memory 805 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 805 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned method embodiments, etc.; the data storage area may store data involved in the above-mentioned method embodiments, etc. The memory 805 may optionally be at least one storage device located away from the aforementioned processor 801. As Figure 8 As shown, the memory 805 as a computer storage medium may include an operating system, a network communication module, a user interface module, and a cross-site cache data transfer program.

[0168] exist Figure 8In the terminal 800 shown, the user interface 803 is mainly used to provide an input interface for the user and obtain the data input by the user; and the processor 801 can be used to call the cross-site cache data transfer program stored in the memory 805, and specifically perform the following operations:

[0169] Determine the browser cache cross-site transfer attribute corresponding to the browser, and obtain a reference website exception list corresponding to the browser cache cross-site transfer attribute;

[0170] When the browser receives a cross-site cache transfer request from a reference website to a target website, based on the browser cache cross-site transfer attribute, the reference website and the reference website exception list, it is determined to cross-site transfer the target cache data of the target website to the reference website.

[0171] Optionally, when the processor 801 executes the acquisition of the reference website exception list corresponding to the browser cache cross-site transfer attribute, the processor 801 specifically performs the following steps:

[0172] Determine the cross-site transfer type of the browser cache cross-site transfer attribute;

[0173] If the cross-site transmission type is the cross-site transmission allowed type, obtain the website's cross-site transmission exception list;

[0174] If the cross-site transfer type is a cross-site transfer rejection type, obtain the website's cross-site transfer rejection exception list.

[0175] Optionally, when the processor 801 determines to transfer the target cache data of the target website to the reference website across sites based on the browser cache cross-site transfer attribute, the reference website and the reference website exception list, the processor 801 specifically performs the following steps:

[0176] Performing list matching processing on the reference website based on the reference website exception list to obtain a list matching result;

[0177] Based on the list matching results and the reference website exception list, determine to pass the target cache data of the target website across sites to the reference website.

[0178] Optionally, when the processor 801 determines to transfer the target cache data of the target website to the reference website across sites based on the list matching result and the reference website exception list, the processor 801 specifically performs the following steps:

[0179] If the reference website exception list is a website cross-site transfer exception list and the list matching result is a list mismatch type, it is determined to cross-site transfer the target cache data of the target website to the reference website;

[0180] If the reference website exception list is a website rejection cross-site transfer exception list and the list matching result is a list matching type, it is determined that the target cache data of the target website is transferred cross-site to the reference website.

[0181] Optionally, the processor 801 further executes prohibiting the cross-site transfer of the target cache data of the target website to the reference website if the reference website exception list is a website cross-site transfer allowed exception list and the list matching result is a list matching type;

[0182] If the reference website exception list is a website rejection cross-site transfer exception list and the list matching result is a list mismatch type, cross-site transfer of the target cache data of the target website to the reference website is prohibited.

[0183] Optionally, when the processor 801 prohibits the target cache data of the target website from being transferred across sites to the reference website, the following steps are specifically performed:

[0184] Determine the cross-site transfer type of the browser cache cross-site transfer attribute;

[0185] If the cross-site transfer type is the cross-site transfer rejection type, the target cache data of the target website is prohibited from being transferred across sites to the reference website;

[0186] If the cross-site transfer type is the cross-site transfer type allowed, the browser cache cross-site transfer attribute configuration processing is performed on the target website to prohibit the target cache data of the target website from being transferred across the site to the reference website.

[0187] Optionally, when the processor 801 performs a browser cache cross-site transfer attribute configuration process on the target website to prohibit the target cache data of the target website from being transferred across the site to the reference website, the following steps are specifically performed:

[0188] For the target website, modify the browser cache cross-site transfer property of the browser to deny cross-site transfer type to prohibit the cross-site transfer of the target cache data of the target website to the reference website; or,

[0189] Create a temporary browser cache cross-site transfer attribute for the target website, set the temporary browser cache cross-site transfer attribute to the temporary cross-site transfer rejection type, so that after the cross-site cache transfer request fails, the temporary cross-site transfer rejection type can be unconfigured.

[0190] Optionally, when the processor 801 determines to transfer the target cache data of the target website to the reference website across sites, the processor 801 specifically performs the following steps:

[0191] Determine the cross-site transfer type of the browser cache cross-site transfer attribute;

[0192] If the cross-site transfer type is a type that allows cross-site transfer, the target cache data of the target website is transferred across the site to the reference website;

[0193] If the cross-site transfer type is a cross-site transfer rejection type, the browser cache cross-site transfer attribute configuration processing is performed on the target website to transfer the target cache data of the target website to the reference website across the site.

[0194] Optionally, when the processor 801 performs a browser cache cross-site transfer attribute configuration process on the target website to transfer the target cache data of the target website to the reference website across the website, the following steps are specifically performed:

[0195] For the target website, modify the browser cache cross-site transfer property of the browser to allow cross-site transfer type, so as to transfer the target cache data of the target website to the reference website across sites; or,

[0196] Create a temporary browser cache cross-site transfer attribute for the target website, set the temporary browser cache cross-site transfer attribute to the temporary allow cross-site transfer type to transfer the target cache data of the target website across sites to the reference website, and unconfigure the temporary allow cross-site transfer type after the target cache data is transferred.

[0197] In the several embodiments provided in the embodiments of the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules, which can be electrical, mechanical or other forms.

[0198] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0199] In addition, each functional module in each embodiment of the present application can be integrated into a processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules.

[0200] If the integrated module is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program code.

[0201] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the embodiments of the present application are not limited by the described order of actions, because according to the embodiments of the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the embodiments of the present application.

[0202] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0203] The above is a description of a cross-site cache data processing method, device, terminal and storage medium provided in an embodiment of the present application. For technical personnel in this field, according to the ideas of the embodiments of the present application, there may be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as a limitation on the embodiments of the present application.

Claims

1. A cross-site cache data transmission method, wherein: The method comprises: Determine a browser cache cross-site transfer attribute corresponding to the browser, and obtain a reference website exception list corresponding to the browser cache cross-site transfer attribute; When the browser receives a cross-site cache transfer request from a reference website to a target website, based on the browser cache cross-site transfer attribute, the reference website and the reference website exception list, it is determined to cross-site transfer the target cache data of the target website to the reference website.

2. The method according to claim 1, wherein: The obtaining of the reference website exception list corresponding to the browser cache cross-site transfer attribute includes: Determine the cross-site transfer type of the browser cache cross-site transfer attribute; If the cross-site transfer type is a cross-site transfer allowed type, obtaining a cross-site transfer allowed exception list of the website; If the cross-site transfer type is a cross-site transfer rejection type, then a cross-site transfer rejection exception list of the website is obtained.

3. The method according to claim 1, wherein: The determining to transfer the target cache data of the target website to the reference website across sites based on the browser cache cross-site transfer attribute, the reference website and the reference website exception list includes: Performing list matching processing on the reference website based on the reference website exception list to obtain a list matching result; Based on the list matching result and the reference website exception list, it is determined to transfer the target cache data of the target website to the reference website across sites.

4. The method according to claim 3, wherein: The step of determining to transfer the target cache data of the target website to the reference website across sites based on the list matching result and the reference website exception list includes: If the reference website exception list is a website cross-site transfer exception list and the list matching result is a list mismatch type, determining to cross-site transfer the target cache data of the target website to the reference website; If the reference website exception list is a website rejection cross-site transfer exception list and the list matching result is a list matching type, it is determined to cross-site transfer the target cache data of the target website to the reference website.

5. The method according to claim 3, wherein: The method further comprises: If the reference website exception list is a website cross-site transfer exception list and the list matching result is a list matching type, then the target cache data of the target website is prohibited from being transferred across sites to the reference website; If the reference website exception list is a website rejection cross-site transfer exception list and the list matching result is a list mismatch type, cross-site transfer of the target cache data of the target website to the reference website is prohibited.

6. The method according to claim 5, wherein: The prohibiting of transferring the target cache data of the target website to the reference website across sites includes: Determine the cross-site transfer type of the browser cache cross-site transfer attribute; If the cross-site transfer type is a cross-site transfer rejection type, the target cache data of the target website is prohibited from being transferred across the site to the reference website; If the cross-site transfer type is a type that allows cross-site transfer, a browser cache cross-site transfer attribute configuration process is performed on the target website to prohibit the target cache data of the target website from being transferred across sites to the reference website.

7. The method according to claim 6, wherein: The performing browser cache cross-site transfer attribute configuration processing on the target website to prohibit the target cache data of the target website from being transferred across sites to the reference website includes: For the target website, modify the browser cache cross-site transfer attribute of the browser to a cross-site transfer rejection type to prohibit the target cache data of the target website from being transferred across sites to the reference website; or, A temporary browser cache cross-site transfer attribute is newly created for the target website, and the temporary browser cache cross-site transfer attribute is set to a temporary cross-site transfer rejection type, so that after the cross-site cache transfer request fails, the temporary cross-site transfer rejection type is unconfigured.

8. A cross-site cache data processing device, wherein: The device comprises: A determination module, adapted to determine a browser cache cross-site transfer attribute corresponding to the browser, and obtain a reference website exception list corresponding to the browser cache cross-site transfer attribute; The access module is adapted to determine, when the browser receives a cross-site cache transfer request from a reference website to a target website, to transfer the target cache data of the target website to the reference website across sites based on the browser cache cross-site transfer attribute, the reference website and the reference website exception list.

9. A terminal, wherein: The terminal includes: Processor; and A memory arranged to store computer executable instructions which, when executed, cause the processor to perform a method according to any one of claims 1 to 7.

10. A computer-readable storage medium, wherein: The computer-readable storage medium stores one or more programs, which, when executed by a processor, implement the method of any one of claims 1 to 7.

Images