Method for preventing cache breakdown, source station gateway, product, equipment and storage medium

Abstract

The invention discloses a method for preventing cache breakdown, a source station gateway, a product, equipment and a storage medium, and relates to the field of data caching, and the method comprises the steps: calling a preset interference parameter elimination script to carry out interference parameter elimination on an initial parameter string of each interface request, the method comprises the following steps: acquiring a parameter string only comprising a source station access condition parameter corresponding to a uniform resource identifier, splicing the uniform resource identifier and the parameter string, acquiring a resource unique identifier corresponding to each interface request, and accessing a source station based on the resource unique identifier. And sending the obtained resource request result to a sending end of each interface request corresponding to the resource unique identifier. According to the method and the device, the interference parameters in the initial parameter string are eliminated, so that the influence of randomly changed parameters in the parameter string on the cache hit rate is avoided, and the resource request results corresponding to the plurality of interface requests with the same resource unique identifier can be obtained only by accessing the source station for one time based on the resource unique identifier; and the access pressure to the source station is reduced.

Description

Technical Field

[0001] The present application relates to the field of data cache technology, and in particular to a method, source station gateway, product, device and storage medium for preventing cache breakdown. Background Art

[0002] To prevent the source site from being impacted by a large number of interface requests generated by the front-end, existing technologies typically configure multiple external gateways, allowing the front-end to obtain the requested resources by accessing the external gateway's cache, thereby reducing the access pressure on the source site. Existing external gateway caches typically use the Uniform Resource Locator (URL) in the interface request as the unique identifier (key) for the resource in the cache. The Uniform Resource Locator (URI) consists of a Uniform Resource Identifier (URI) and a parameter string. The URI uniquely identifies the address information of the resource requested by the interface request, and the parameter string includes other parameters, including access verification condition parameters.

[0003] However, since all parameters in the parameter string of the interface request, except for the access verification condition parameter string, can be changed at will by the user, when a malicious user modifies the parameter string and generates a large number of abnormal interface requests, the URLs of the abnormal interface requests change, making it impossible for the external gateway to hit the cache based on the URL of the abnormal interface request, resulting in external gateway cache failure. This in turn puts the source station at risk of crashing due to the pressure of a large number of malicious interface requests. Therefore, how to prevent cache failure from causing source station crashes has become an urgent problem to be solved. Summary of the Invention

[0004] In view of the above problems, this application provides a method, source station gateway, product, device, and storage medium for preventing cache breakdown to achieve the purpose of avoiding cache breakdown and causing source station crashes. The specific solution is as follows: In a first aspect, the present application provides a method for preventing cache breakdown, which is applied to an origin gateway. The method for preventing cache breakdown includes: Parsing the Uniform Resource Locator of each received interface request respectively to obtain the Uniform Resource Identifier and initial parameter string of each interface request; Calling a preset interference parameter elimination script to eliminate interference parameters from the initial parameter string to obtain a parameter string that only includes the source station access condition parameters corresponding to the uniform resource identifier; Concatenate the uniform resource identifier and the parameter string of each interface request to obtain a resource unique identifier corresponding to each interface request; The source station is accessed based on the resource unique identifier, and the resource request result fed back by the source station is sent to the sending end of each interface request corresponding to the resource unique identifier.

[0005] In a possible implementation, calling a preset interference parameter elimination script to eliminate interference parameters from the initial parameter string to obtain a parameter string that includes only the source station access condition parameters corresponding to the uniform resource identifier includes: For each of the interface requests: Obtaining a rejection rule identifier corresponding to the uniform resource identifier requested by the interface by querying a preset correspondence table, and importing a rejection rule file corresponding to the rejection rule identifier into the preset interference parameter rejection script for initialization configuration; The preset interference parameter elimination script that has been initialized and configured is called to eliminate other interference parameters in the initial parameter string except the source station access condition parameter to obtain the parameter string.

[0006] In a possible implementation, accessing the source station based on the resource unique identifier and sending the resource request result fed back by the source station to the sender of each interface request corresponding to the resource unique identifier includes: Counting the number of accesses of the interface requests with the same resource unique identifier within a preset time period, and when the number of accesses is greater than a preset threshold, performing source station access based on the resource unique identifier of the target interface request, and obtaining a resource request result corresponding to the resource unique identifier of the target interface request fed back by the source station, where the target interface request is any one of multiple interface requests with the same resource unique identifier; The resource request result and the correspondence between the resource request result and the resource unique identifier are cached, and based on the correspondence between the resource unique identifier and the interface request, and the correspondence between the resource request result and the resource unique identifier, the resource request result is sent to the sending end of each interface request.

[0007] In a possible implementation, before accessing the source site based on the resource unique identifier requested by the target interface, the method further includes: Determine whether the resource request result having a corresponding relationship with the resource unique identifier corresponding to the target interface request is stored in the local cache; if so, based on the corresponding relationship between the resource unique identifier and the interface request, and the corresponding relationship between the resource request result and the resource unique identifier, send the resource request result in the local cache to the sending end of each interface request; If not, the operation step of accessing the source site based on the resource unique identifier requested by the target interface is executed.

[0008] In a possible implementation, when the number of accesses is not greater than the preset threshold, the method further includes: The source station is accessed concurrently based on the resource unique identifiers corresponding to the respective interface requests to obtain the resource request results corresponding to the respective resource unique identifiers.

[0009] In a possible implementation, before caching the resource request result and the corresponding relationship between the resource request result and the resource unique identifier, the method further includes: Determine whether the HTTP status code in the resource request result is an HTTP status code indicating a successful resource request; if so, execute the step of caching the resource request result and the correspondence between the resource request result and the resource unique identifier; If not, after sending the resource request result to the sending end of each interface request based on the correspondence between the resource unique identifier and the interface request, and the correspondence between the resource request result and the resource unique identifier, the resource request result including the HTTP status code that does not represent the success of the resource request will be deleted.

[0010] A second aspect of the present application provides a source station gateway, the source station gateway comprising: A parameter parsing module, configured to parse the uniform resource locators of each received interface request respectively to obtain the uniform resource identifier and initial parameter string of each interface request; a parameter elimination module, configured to call a preset interference parameter elimination script to eliminate interference parameters from the initial parameter string, and obtain a parameter string including only the source station access condition parameters corresponding to the uniform resource identifier; A parameter splicing module, configured to splice the uniform resource identifier and the parameter string of each interface request to obtain a resource unique identifier corresponding to each interface request; The resource sending module is used to access the source station based on the resource unique identifier and send the resource request result fed back by the source station to the sending end of each interface request corresponding to the resource unique identifier.

[0011] In a possible implementation, the parameter elimination module is configured as follows: For each of the interface requests: Obtaining a rejection rule identifier corresponding to the uniform resource identifier requested by the interface by querying a preset correspondence table, and importing a rejection rule file corresponding to the rejection rule identifier into the preset interference parameter rejection script for initialization configuration; The preset interference parameter elimination script that has been initialized and configured is called to eliminate other interference parameters in the initial parameter string except the source station access condition parameter to obtain the parameter string.

[0012] In a possible implementation, the resource sending module is configured to: Counting the number of accesses of the interface requests with the same resource unique identifier within a preset time period, and when the number of accesses is greater than a preset threshold, performing source station access based on the resource unique identifier of the target interface request, and obtaining a resource request result corresponding to the resource unique identifier of the target interface request fed back by the source station, where the target interface request is any one of multiple interface requests with the same resource unique identifier; The resource request result and the correspondence between the resource request result and the resource unique identifier are cached, and based on the correspondence between the resource unique identifier and the interface request, and the correspondence between the resource request result and the resource unique identifier, the resource request result is sent to the sending end of each interface request.

[0013] In a possible implementation, the resource sending module is further configured to: Before the source station is accessed based on the resource unique identifier of the target interface request, it is determined whether the local cache stores the resource request result having a corresponding relationship with the resource unique identifier corresponding to the target interface request; if so, based on the corresponding relationship between the resource unique identifier and the interface request, and the corresponding relationship between the resource request result and the resource unique identifier, the resource request result in the local cache is sent to the sending end of each interface request; If not, the operation step of accessing the source site based on the resource unique identifier requested by the target interface is executed.

[0014] In a possible implementation, the resource sending module is further configured to: When the access quantity is not greater than the preset threshold, the source station is accessed concurrently based on the resource unique identifier corresponding to each of the interface requests to obtain the resource request results corresponding to each of the resource unique identifiers.

[0015] In a possible implementation, the resource sending module is further configured to: Before caching the resource request result and the corresponding relationship between the resource request result and the resource unique identifier, determining whether the HTTP status code in the resource request result is an HTTP status code indicating a successful resource request, and if so, executing the step of caching the resource request result and the corresponding relationship between the resource request result and the resource unique identifier; If not, after sending the resource request result to the sending end of each interface request based on the correspondence between the resource unique identifier and the interface request, and the correspondence between the resource request result and the resource unique identifier, the resource request result including the HTTP status code that does not represent the success of the resource request will be deleted.

[0016] A third aspect of the present application provides a computer program product comprising computer-readable instructions. When the computer-readable instructions are executed on an electronic device, the electronic device implements the method for preventing cache breakdown according to the first aspect or any implementation of the first aspect.

[0017] A fourth aspect of the present application provides an electronic device, comprising at least one processor and a memory connected to the processor, wherein: The memory is used to store computer programs; The processor is used to execute the computer program so that the electronic device can implement the method for preventing cache breakdown according to the first aspect or any implementation of the first aspect.

[0018] In a fifth aspect, the present application provides a computer storage medium, which carries one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement the method for preventing cache breakdown according to the first aspect or any implementation of the first aspect.

[0019] By means of the above technical solution, the method, source station gateway, product, device and storage medium for preventing cache breakdown provided by the present application eliminate interference parameters of the initial parameter string of each interface request by calling the preset interference parameter elimination script corresponding to each uniform resource identifier of each interface request, and obtain a parameter string that only includes the source station access condition parameters corresponding to the uniform resource identifier, and splices the uniform resource identifier and the parameter string to obtain the resource unique identifier corresponding to each interface request, thereby avoiding the influence of the parameters changed arbitrarily in the parameter string on the cache hit rate. Subsequently, by configuring the access to the source station based on the resource unique identifier, and sending the resource request result fed back by the source station to the sending end of each interface request corresponding to the resource unique identifier, in the case of multiple interface requests with the same resource unique identifier, only one access to the source station based on the resource unique identifier is required to obtain the resource request results corresponding to the multiple interface requests, thereby reducing the access pressure on the source station and avoiding the risk of the source station being unable to withstand the access pressure of a large number of malicious interface requests and crashing. It can be seen that the present application avoids the risk of the source station crashing due to cache breakdown. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The above and other features, advantages, and aspects of the various embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that the originals and elements are not necessarily drawn to scale.

[0021] Figure 1 A schematic diagram of an external gateway cache provided for this application; Figure 2 A schematic diagram of using a virtual interface request to penetrate an external gateway cache provided by this application; Figure 3 A flowchart of a method for preventing cache breakdown provided by this application; Figure 4 A schematic diagram of a method for preventing cache breakdown provided by this application; Figure 5 A flowchart of a method for preventing cache breakdown provided in a possible implementation of the present application; Figure 6 A block diagram of a source station gateway provided for this application; Figure 7 This is a schematic diagram of the structure of an electronic device provided in this application. DETAILED DESCRIPTION

[0022] The following describes the embodiments of the present application in conjunction with the accompanying drawings. The terms used in the implementation methods of the present application are only used to explain the specific embodiments of the present application and are not intended to limit the present application.

[0023] The embodiments of the present application are described below in conjunction with the accompanying drawings. Those skilled in the art will appreciate that, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0024] The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, and this is merely a way of distinguishing the objects of the same attributes when describing them in the embodiments of the present application. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, so that the process, method, system, product or equipment comprising a series of units need not be limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0025] It should be noted that to facilitate understanding of the principle of cache breakdown, an example is provided here to illustrate: like Figure 1 The following diagram shows an external gateway cache. Assume that the current external network includes external gateways A and B. The origin site is configured with an origin gateway. Users include user 1, user 2, and user 3. User 1 and user 2 both access external gateway A, while user 3 accesses external gateway B. External gateways A, B, and the origin gateway are connected in sequence.

[0026] Assume that the target resource that user 1 needs to obtain is not cached in external gateway A and external gateway B.

[0027] User 1 sends a target interface request to external gateway A for obtaining the above-mentioned target resource; external gateway A queries the local cache and does not find the target resource corresponding to the target interface request, so external gateway A forwards the target interface request to external gateway B; external gateway B queries the local cache and does not find the target resource corresponding to the target interface request, so external gateway B forwards the target interface request to the source station gateway; the source station gateway accesses the source station based on the target interface request, and feeds back the target resource fed back by the source station to external gateway B; external gateway B stores the target resource in the local cache and sends the target resource to external gateway A; external gateway A stores the target resource in the local cache and sends the target resource to user 1.

[0028] After the above steps, both external gateway A and external gateway B cache the above target resource.

[0029] User 2 sends the above target interface request to external gateway A; external gateway A queries the local cache to obtain the target resource corresponding to the target interface request, and if a match is found, sends the target resource to user 2. User 3 sends the above target interface request to external gateway B; external gateway B queries the local cache to obtain the target resource corresponding to the target interface request, and if a match is found, sends the target resource to user 3. It can be seen that when users 2 and 3 send interface requests, since external gateways A and B already store the target resource, the interface requests do not need to be sent to the origin server, reducing the access pressure on the origin server.

[0030] In the existing configuration, when the external gateway A and the external gateway B cache the target resource, they will use the Uniform Resource Locator in the target interface request as the resource unique identifier for searching for the target resource. That is, the Uniform Resource Locators in the interface requests sent by the above-mentioned users 1, 2, and 3 are exactly the same. However, since the parameter string of the Uniform Resource Locator can be customized by the user, such as adding random numbers, virtual device version numbers, timestamps and other interference parameters to the string, a large number of virtual Uniform Resource Locators are generated, and then a large number of virtual interface requests are generated. The schematic diagram of using virtual interface requests to penetrate the external gateway cache is shown as follows: Figure 2 As shown: Assume that the current external network includes external gateways A and B. The origin site is configured with an origin gateway. Users include user 1, user 2, and user 3. User 1 and user 2 both access external gateway A, while user 3 accesses external gateway B. External gateways A, B, and the origin gateway are connected in sequence. The local caches of external gateways A and B both store the target resource. The target resource's unique identifier in each gateway's local cache is Uniform Resource Locator A.

[0031] Assuming that user 1 is a normal user, user 1 sends an interface request A with uniform resource locator A to external gateway A; external gateway A searches for the target resource corresponding to uniform resource locator A in the local cache, and feeds back the target resource to user 1 if a hit is found.

[0032] Assume that user 2 is a malicious user. User 2 generates uniform resource locator B by adding a random number to the parameters of uniform resource locator A. User 2 sends interface request B with uniform resource locator B to external gateway A. External gateway A searches for the target resource corresponding to uniform resource locator B in the local cache, and forwards interface request B to external gateway B if no hit is found. External gateway B searches for the target resource corresponding to uniform resource locator B in the local cache, and forwards interface request B to the source station gateway if no hit is found. The source station gateway accesses the source station based on uniform resource locator B.

[0033] While user 2 generates uniform resource locator B, assuming user 3 is a malicious user, user 3 generates uniform resource locator C by adding a timestamp to the parameters of uniform resource locator A; user 3 sends an interface request C with uniform resource locator C to the external gateway B; the external gateway B searches for the target resource corresponding to uniform resource locator C in the local cache, and forwards the interface request C to the source station gateway if no hit is found; the source station gateway accesses the source station based on uniform resource locator C.

[0034] As can be seen from the figure above, when there are multiple malicious users, or when multiple malicious users generate a large number of interface requests including virtual uniform resource locators by arbitrarily modifying parameter strings, since the resources corresponding to the virtual uniform resource locators do not exist in the caches of each external gateway, these interface requests will penetrate the external gateway cache and be sent uniformly to the source gateway, thereby exerting enormous access pressure on the source station and even causing the source station to crash. It can be seen that although the existing method of configuring external gateways can reduce the access pressure on the source station under normal access conditions, it still cannot avoid the risk of cache penetration leading to source station crashes.

[0035] The first aspect of the present application provides a method for preventing cache breakdown, which is applied to a source station gateway, such as Figure 3 As shown, the method for preventing cache breakdown includes: S301: Parse the Uniform Resource Locator of each received interface request respectively to obtain the Uniform Resource Identifier and initial parameter string of each interface request.

[0036] It should be noted that, in actual application scenarios, the above-mentioned source station gateway can be a gateway deployed on the same server as the source station, used to access the source station and extract resources.

[0037] It should be noted that in actual application scenarios, due to the differences in the requesters of different resources and the different probabilities of abnormal requests from different requesters, for example, in the advertising delivery scenario, the requesters of advertising resources include mobile device APPs, large display devices, web pages, etc., among which the request interval period of large display devices is longer and the probability of abnormal requests is smaller. Therefore, if it is determined based on the uniform resource identifier that the requester of the current interface request is a large display device, the source station can be directly accessed based on the current interface request to obtain the corresponding resources, thereby improving the feedback efficiency of resources. Therefore, after obtaining the uniform resource identifier and initial parameter string of each interface request, it can be determined based on the uniform resource identifier whether the following steps can be omitted: Figure 3 The steps S302 to S304 are shown, and the source station is accessed directly based on the interface request. The specific operation steps include the following steps A1 to A2.

[0038] Step A1: for each interface request: determine whether the interface request uniform resource identifier is stored in the preset verification identifier list. If so, trigger the execution of the following steps: Figure 1 If not, step A2 is triggered.

[0039] Step A2: access the source site based on the uniform resource locator of the interface request, and obtain the resource request result corresponding to the uniform resource locator fed back by the source site.

[0040] It should be noted that in actual application scenarios, since the resource identifier and parameter string in the uniform resource locator are often separated by fixed characters, the above Figure 1 The illustrated step S301 may be implemented using a character recognition and segmentation script, and a specific implementation may include the following steps B1 to B2.

[0041] In step B1, a preset character recognition and segmentation script is used to identify and locate a target separator in a uniform resource locator, and step B2 is triggered.

[0042] It should be noted that, in actual application scenarios, the above-mentioned preset character recognition and segmentation script can be constructed based on the string operation function (split). This application does not make too many restrictions or redundant descriptions on the construction process of the above-mentioned preset character recognition and segmentation script.

[0043] Step B2: Based on the identification and positioning result of step B1, extract the character string before the target delimiter to obtain a uniform resource identifier; extract the character string after the target delimiter to obtain an initial parameter string.

[0044] S302: Call a preset interference parameter elimination script to eliminate interference parameters from the initial parameter string, and obtain a parameter string that only includes source site access condition parameters corresponding to the uniform resource identifier.

[0045] It should be noted that in actual application scenarios, the above-mentioned source station access condition parameters refer to the parameters required by the source station to verify access rights, such as: requester account, password, verification code, etc. Since the above-mentioned initial parameter string includes source station access condition parameters and interference parameters, and in the process of requesting resources, the above-mentioned interference parameters do not participate in the resource request process. Therefore, this application removes interference parameters from the initial parameter string by configuring and calling a preset interference parameter removal script, and removes interference parameters without affecting the subsequent resource request process, thereby avoiding the risk of cache breakdown caused by arbitrarily changed parameters in the parameter string, thereby increasing the access pressure on the source station.

[0046] It should be noted that in actual application scenarios, the preset interference parameter removal script can be based on a character search and replace function (Replace). Because the source station access condition parameters and interference parameters in the initial parameter string are arranged in a certain order, this application configures the preset interference parameter removal script to extract the interference parameters based on the order in which the source station access condition parameters and interference parameters are arranged in the initial parameter string, thereby obtaining a parameter string that only includes the source station access condition parameters corresponding to the uniform resource identifier.

[0047] S303: Concatenate the uniform resource identifier and parameter string of each interface request to obtain the resource unique identifier corresponding to each interface request.

[0048] It should be noted that this application configures the uniform resource identifier of each interface request to be concatenated with the parameter string after removing interference parameters to obtain a resource unique identifier that uniquely represents the requested resource. This allows accurate identification of a large number of interface requests requesting the same resource.

[0049] S304: Access the source station based on the resource unique identifier, and send the resource request result fed back by the source station to the sending end of each interface request corresponding to the resource unique identifier.

[0050] It should be noted that in actual application scenarios, this application configures access to the source station based on the resource unique identifier, and sends the resource request results fed back by the source station to the sending end of each interface request corresponding to the resource unique identifier. In this way, when there are multiple interface requests with the same resource unique identifier, only one access to the source station based on the resource unique identifier is required to obtain the resource request results corresponding to multiple interface requests, thereby reducing the access pressure on the source station and avoiding the risk of the source station collapsing due to being unable to withstand the access pressure of a large number of malicious interface requests.

[0051] It should be noted that in actual application scenarios, due to the Figure 1 The method for preventing cache penetration shown is applied to the source station gateway, so it is only necessary to execute the above-mentioned Figure 1 The program or configuration file of the method for preventing cache breakdown shown can be loaded into the source station gateway without the need for adaptive configuration modification of the external gateway, thereby improving the deployment convenience of the present application.

[0052] It should be noted that in actual application scenarios, when implementing the Figure 1 The method for preventing cache breakdown shown above can avoid the risk of origin server crash due to cache breakdown. Specifically: like Figure 4 A schematic diagram showing a method for preventing cache punchthrough is shown below: Assume that the current external network includes external gateway A and external gateway B. The source station is configured with a source station gateway, and the source station gateway is loaded with a program for executing the above-mentioned Figure 1 The configuration file for the cache breakdown prevention method shown in the figure includes users 1, 2, and 3. User 1 and 2 both access external gateway A, while user 3 accesses external gateway B. External gateway A, external gateway B, and the origin gateway are connected in sequence.

[0053] Assume that User 1, User 2, and User 3 are all malicious users, and each malicious user modifies the parameter string parameters to generate their own virtual interface requests based on the Uniform Resource Locator (URL) and initial parameter string of the real interface request: User 1 generates virtual interface request A, User 2 generates virtual interface request B, and User 3 generates virtual interface request C. The URLs in these three virtual interface requests are the same, the source site access condition parameters in the initial parameter strings in these three virtual interface requests are the same, and the interference parameters in the initial parameter strings in these three virtual interface requests are different.

[0054] Because both external gateway A and external gateway B use Uniform Resource Locators (URLs) as unique identifiers for resources in their caches, after user 1 sends virtual interface request A to external gateway A, user 2 sends virtual interface request B to external gateway A, and user 3 sends virtual interface request C to external gateway B, external gateways A and B fail to find the target resource corresponding to the URL in the virtual interface request in their local caches, resulting in cache breakdown. At this point, external gateway A sends virtual interface request A and virtual interface request B to external gateway B, and external gateway B sends virtual interface request A, virtual interface request B, and virtual interface request C to the source gateway.

[0055] The source station gateway parses the uniform resource locators in the virtual interface request A, the virtual interface request B, and the virtual interface request C respectively, obtains the uniform resource identifier and the initial parameter string of each virtual interface request, and calls the preset interference parameter removal script to remove the interference parameters of each initial parameter string to obtain each parameter string; splices the uniform resource identifier and the parameter string of each virtual interface request to obtain the resource unique identifier corresponding to each virtual interface request; accesses the source station based on the resource unique identifier; and sends the resource request result fed back by the source station to the external gateway B; the external gateway B stores the resource request result in the local cache, and sends the resource request result to user 3; the external gateway B sends the resource request result to the external gateway A; the external gateway A stores the resource request result in the local cache, and sends the resource request result to user 1 and user 2 respectively. It can be seen that if the method provided by this application is not adopted, Figure 1If the method for preventing cache breakdown is used as shown, the source station gateway will simultaneously initiate three accesses to the source station. However, after adopting the method for preventing cache breakdown provided by this application, the source station gateway only needs to initiate one access to the source station, reducing the access pressure on the source station.

[0056] This application removes interference parameters from the initial parameter string of each interface request by calling the preset interference parameter removal script corresponding to each uniform resource identifier of each interface request, and obtains a parameter string that only includes the source station access condition parameters corresponding to the uniform resource identifier, and splices the uniform resource identifier and the parameter string to obtain the resource unique identifier corresponding to each interface request, thereby avoiding the influence of arbitrarily changed parameters in the parameter string on the cache hit rate. Subsequently, by configuring the access to the source station based on the resource unique identifier, and sending the resource request result fed back by the source station to the sending end of each interface request corresponding to the resource unique identifier, in the case of multiple interface requests with the same resource unique identifier, only one access to the source station based on the resource unique identifier is required to obtain the resource request results corresponding to multiple interface requests, thereby reducing the access pressure on the source station and avoiding the risk of the source station crashing due to being unable to withstand the access pressure of a large number of malicious interface requests. It can be seen that this application avoids the risk of the source station crashing due to cache breakdown.

[0057] In one possible implementation, a preset interference parameter elimination script is called to eliminate interference parameters from the initial parameter string, and a parameter string including only the source station access condition parameters corresponding to the uniform resource identifier is obtained, including: Requests for each interface: Obtain a rejection rule identifier corresponding to the uniform resource identifier of the interface request by querying the preset correspondence table, and import the rejection rule file corresponding to the rejection rule identifier into the preset interference parameter rejection script for initialization configuration; The preset interference parameter elimination script that has been initialized and configured is called to eliminate other interference parameters in the initial parameter string except the source station access condition parameter to obtain a parameter string.

[0058] It should be noted that, in actual application scenarios, the above-mentioned preset correspondence table can be a data table that stores the correspondence between the uniform resource identifier and the elimination rule identifier. For different types of resources, the source station access condition parameters in their initial parameter strings are different. For example, the source station access condition parameters in the initial parameter string of type A resources are 20 consecutive characters, and the source station access parameters in the initial parameter string of type B resources include two strings separated by a separator, each string has 5 consecutive characters. Therefore, the present application configures the above-mentioned preset correspondence table, and obtains the elimination rule identifier corresponding to the uniform resource identifier requested by the interface by querying the preset correspondence table, thereby realizing the flexible elimination of interference parameters in the parameter strings corresponding to different types of resources, thereby improving the elimination accuracy and elimination flexibility.

[0059] In a possible implementation, the content of the above-mentioned exclusion rule file can be: assuming that the initial parameter strings of type A resources and type B resources are both "a=A&b=B&ts=1714039515524", where "ts=1714039515524" is the interference parameter, the content of the exclusion rule file for type A resources is to retain only the full characters before the first separator "&", and the content of the exclusion rule file for type B resources is to remove all characters after the last separator "&".

[0060] In a possible implementation, accessing the source station based on the resource unique identifier and sending the resource request result fed back by the source station to the sender of each interface request corresponding to the resource unique identifier includes: Counting the number of accesses to the interface request with the same resource unique identifier within a preset time period, and when the number of accesses is greater than a preset threshold, performing source site access based on the resource unique identifier of the target interface request, and obtaining a resource request result corresponding to the resource unique identifier of the target interface request fed back by the source site, where the target interface request is any one of multiple interface requests with the same resource unique identifier; The resource request result and the correspondence between the resource request result and the resource unique identifier are cached, and based on the correspondence between the resource unique identifier and the interface request, and the correspondence between the resource request result and the resource unique identifier, the resource request result is sent to the sending end of each interface request.

[0061] It should be noted that in actual application scenarios, the above-mentioned preset threshold value can be the maximum number of accesses that the source station can receive within a preset time period without reaching the performance limit. Since in actual application scenarios, the above-mentioned interface requests will continuously arrive at the source station gateway, this application configures the statistics to count the number of accesses of interface requests with the same resource unique identifier within the preset time period, thereby avoiding the problem of reduced processing efficiency caused by processing interface requests one by one.

[0062] It should be noted that in actual application scenarios, this application accesses the source station by configuring a resource unique identifier based on the target interface request, and obtains the resource request result corresponding to the resource unique identifier of the target interface request fed back by the source station. Therefore, when the source station gateway receives a large number of interface requests with the same resource unique identifier, it only needs to access the source station once to obtain the resource request results corresponding to a large number of interface requests, thereby reducing the access pressure on the source station and improving the feedback efficiency of the resource request results.

[0063] It should be noted that in actual application scenarios, after the source station gateway caches the resource request results and the correspondence between the resource request results and the resource unique identifier, the source station gateway can directly send the resource request results to the sending end of each interface request, or it can send the resource request results and the correspondence between the resource request results and the resource unique identifier to an external gateway that is communicated with the sending end, so that the external gateway caches the resource request results and the correspondence between the resource request results and the resource unique identifier and then sends them to the sending end, thereby further reducing the access pressure on the source station and the source station gateway.

[0064] In a possible implementation, before accessing the source site based on the unique identifier of the resource requested by the target interface, the following is further included: Determine whether a resource request result having a corresponding relationship with the resource unique identifier corresponding to the target interface request is stored in the local cache; if so, send the resource request result in the local cache to the sending end of each interface request based on the corresponding relationship between the resource unique identifier and the interface request, and the corresponding relationship between the resource request result and the resource unique identifier; If not, the operation steps for accessing the source site based on the resource unique identifier requested by the target interface are executed.

[0065] It should be noted that in actual application scenarios, the above local cache is the cache of the source station gateway.

[0066] It should be noted that this application configures the resource request result and the correspondence between the resource request result and the resource unique identifier for caching, and configures that before accessing the source station based on the resource unique identifier of the target interface request, it determines whether the local cache stores a resource request result that has a corresponding relationship with the resource unique identifier corresponding to the target interface request. Therefore, when the source station gateway receives an interface request with a resource unique identifier corresponding to the resource request result, it does not need to access the source station, but extracts the resource request result from the cache of the source station gateway for feedback, thereby further reducing the pressure on source station access.

[0067] In a possible implementation, when the number of accesses is not greater than a preset threshold, the method further includes: Based on the resource unique identifiers corresponding to each interface request, the source station is accessed concurrently to obtain the resource request results corresponding to each resource unique identifier.

[0068] It should be noted that in actual application scenarios, since the above-mentioned preset threshold can be the maximum number of accesses that the source station can receive within a preset time period without reaching the performance upper limit, this application configures the number of accesses of interface requests with the same resource unique identifier within a preset time period to be no greater than the preset threshold, and concurrently accesses the source station based on the resource unique identifier corresponding to each interface request to obtain the resource request results corresponding to each resource unique identifier, thereby improving the processing efficiency of the interface request without causing the source station to crash.

[0069] In a possible implementation, before caching the resource request result and the corresponding relationship between the resource request result and the resource unique identifier, the following is further included: Determine whether the HTTP status code in the resource request result is an HTTP status code indicating a successful resource request. If so, execute the operation step of caching the resource request result and the correspondence between the resource request result and the resource unique identifier; If not, after sending the resource request result to the sending end of each interface request based on the correspondence between the resource unique identifier and the interface request, and the correspondence between the resource request result and the resource unique identifier, the resource request result including the HTTP status code that does not represent the success of the resource request will be deleted.

[0070] It should be noted that, in actual application scenarios, the above-mentioned HTTP status code (HTTP Status Code) uses a 3-digit code to identify the server Hypertext Transfer Protocol response status. Since the content of the HTTP status code does not indicate a successful resource request, it indicates that the source station has not fed back the requested resource corresponding to the interface request. At this time, since there is no requested resource, the source station gateway obtains only the HTTP status code in the resource request result. Therefore, this application is configured based on the correspondence between the resource unique identifier and the interface request, and the correspondence between the resource request result and the resource unique identifier, and after sending the resource request result to the sending end of each interface request, the resource request result including the HTTP status code that does not indicate a successful resource request is deleted, thereby reducing the occupancy of the source station gateway cache.

[0071] In order to facilitate the above Figure 3 The understanding of the method for preventing cache breakdown shown is explained here in conjunction with a possible implementation of the present application: like Figure 5 FIG. 1 is a flow chart of a method for preventing cache breakdown, and the specific steps are as follows: Step S501: parse the Uniform Resource Locator of each received interface request to obtain the Uniform Resource Identifier and initial parameter string of each interface request, and trigger step S502.

[0072] Step S502, for each interface request: determine whether the uniform resource identifier of the interface request is stored in the preset verification identifier list, if not, trigger step S503, if yes, trigger step S504.

[0073] Step S503: for each interface request whose uniform resource identifier is stored in the preset verification identifier list, a preset interference parameter elimination script is called to eliminate interference parameters from the initial parameter string of the interface request to obtain the parameter string of the interface request, and step S505 is triggered.

[0074] Step S504, for each interface request whose uniform resource identifier is not stored in the preset verification identifier list: access the source site based on the uniform resource locator of the interface request, and after storing the resource request result fed back by the source site and the correspondence between the uniform resource locator and the resource request result in the local cache, feed back the resource request result to the sender of the interface request.

[0075] In step S505, the uniform resource identifier and parameter string of each interface request are concatenated to obtain the resource unique identifier corresponding to each interface request, and step S506 is triggered.

[0076] Step S506: for each resource unique identifier, count the number of access requests from the interface with the same resource unique identifier within a preset time period, and trigger step S507.

[0077] Step S507: Determine whether the number of visits is greater than a preset threshold. If yes, step S508 is triggered; if not, step S509 is triggered.

[0078] Step S508: Access the source site based on the unique resource identifier, and trigger step S510.

[0079] It should be noted that, in an actual application scenario, the above step S508 may be an operation step for concurrently processing multiple different resource unique identifiers.

[0080] It should be noted that, in an actual application scenario, the resource unique identifier in the above step S508 is any one of the resource unique identifiers in the above step S506.

[0081] Step S509: Determine whether the local cache stores a resource request result corresponding to the resource unique identifier. If yes, step S511 is triggered; if not, step S508 is triggered.

[0082] Step S510: Obtain the resource request result corresponding to the unique resource identifier fed back by the source station, and trigger step S512.

[0083] Step S511 , based on the correspondence between the resource unique identifier and the interface request, and the correspondence between the resource request result and the resource unique identifier, the resource request result in the local cache is sent to the sender of each interface request corresponding to the resource unique identifier.

[0084] Step S512: Determine whether the HTTP status code in the resource request result corresponding to the resource unique identifier is an HTTP status code indicating a successful resource request. If so, step S513 is triggered; if not, step S514 is triggered.

[0085] Step S513, cache the resource request result and the correspondence between the resource request result and the resource unique identifier, and send the resource request result to the sending end of each interface request based on the correspondence between the resource unique identifier and the interface request, and the correspondence between the resource request result and the resource unique identifier.

[0086] Step S514, based on the correspondence between the resource unique identifier and the interface request, and the correspondence between the resource request result and the resource unique identifier, after sending the resource request result to the sending end of each interface request, the resource request result including the HTTP status code that does not represent the success of the resource request is deleted.

[0087] The second aspect of the present application provides a source station gateway, such as Figure 6 As shown, the source gateway includes: The parameter parsing module 601 is used to parse the uniform resource locator of each received interface request to obtain the uniform resource identifier and initial parameter string of each interface request; A parameter elimination module 602 is configured to call a preset interference parameter elimination script to eliminate interference parameters from the initial parameter string, thereby obtaining a parameter string that only includes the source station access condition parameters corresponding to the uniform resource identifier; The parameter concatenation module 603 is used to concatenate the uniform resource identifier and parameter string of each interface request to obtain the resource unique identifier corresponding to each interface request; The resource sending module 604 is configured to access the source station based on the resource unique identifier, and send the resource request result fed back by the source station to the sending end of each interface request corresponding to the resource unique identifier.

[0088] In a possible implementation, the parameter elimination module 602 is configured as follows: Requests for each interface: Obtain a rejection rule identifier corresponding to the uniform resource identifier of the interface request by querying the preset correspondence table, and import the rejection rule file corresponding to the rejection rule identifier into the preset interference parameter rejection script for initialization configuration; The preset interference parameter elimination script that has been initialized and configured is called to eliminate other interference parameters in the initial parameter string except the source station access condition parameter to obtain a parameter string.

[0089] In a possible implementation, the resource sending module 604 is configured to: Counting the number of accesses to the interface request with the same resource unique identifier within a preset time period, and when the number of accesses is greater than a preset threshold, performing source site access based on the resource unique identifier of the target interface request, and obtaining a resource request result corresponding to the resource unique identifier of the target interface request fed back by the source site, where the target interface request is any one of multiple interface requests with the same resource unique identifier; The resource request result and the correspondence between the resource request result and the resource unique identifier are cached, and based on the correspondence between the resource unique identifier and the interface request, and the correspondence between the resource request result and the resource unique identifier, the resource request result is sent to the sending end of each interface request.

[0090] In a possible implementation, the resource sending module 604 is further configured to: Before accessing the source site based on the resource unique identifier of the target interface request, determine whether a resource request result having a corresponding relationship with the resource unique identifier corresponding to the target interface request is stored in the local cache; if so, based on the corresponding relationship between the resource unique identifier and the interface request, and the corresponding relationship between the resource request result and the resource unique identifier, send the resource request result in the local cache to the sending end of each interface request; If not, the operation steps for accessing the source site based on the resource unique identifier requested by the target interface are executed.

[0091] In a possible implementation, the resource sending module 604 is further configured to: When the number of accesses is not greater than a preset threshold, the source station is accessed concurrently based on the resource unique identifiers corresponding to the interface requests to obtain the resource request results corresponding to the resource unique identifiers.

[0092] In a possible implementation, the resource sending module 604 is further configured to: Before caching the resource request result and the corresponding relationship between the resource request result and the resource unique identifier, determining whether the HTTP status code in the resource request result is an HTTP status code indicating a successful resource request, and if so, executing the step of caching the resource request result and the corresponding relationship between the resource request result and the resource unique identifier; If not, after sending the resource request result to the sending end of each interface request based on the correspondence between the resource unique identifier and the interface request, and the correspondence between the resource request result and the resource unique identifier, the resource request result including the HTTP status code that does not represent the success of the resource request will be deleted.

[0093] A third aspect of the present application provides a computer program product comprising computer-readable instructions. When the computer-readable instructions are executed on an electronic device, the electronic device implements the method for preventing cache breakdown according to the first aspect or any implementation of the first aspect.

[0094] A fourth aspect of the present application provides an electronic device, comprising at least one processor and a memory connected to the processor, wherein: Memory is used to store computer programs; The processor is used to execute a computer program so that the electronic device can implement the method for preventing cache breakdown of the above-mentioned first aspect or any implementation manner of the first aspect.

[0095] The structural diagram of the electronic device provided in the fourth aspect of this application is as follows Figure 7 The electronic devices in the embodiments of the present application may include, but are not limited to, fixed terminals such as mobile phones, laptop computers, PDAs (personal digital assistants), PADs (tablet computers), desktop computers, and the like. Figure 7 The electronic device shown is merely an example and should not limit the functions and scope of use of the embodiments of the present application.

[0096] like Figure 7 As shown, the electronic device may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 701, which can perform various appropriate actions and processes based on programs stored in a read-only memory (ROM) 702 or programs loaded from a storage device 708 into a random access memory (RAM) 703. When the electronic device is powered on, the RAM 703 also stores various programs and data required for the operation of the electronic device. The processing device 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0097] Typically, the following devices may be connected to the I / O interface 705: an input device 706 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 707 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 708 including, for example, a memory card, a hard disk, etc.; and a communication device 709. The communication device 709 may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. Figure 7 The electronic device is shown with various devices, but it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed instead.

[0098] In a fifth aspect, the present application provides a computer storage medium, which carries one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement the method for preventing cache breakdown according to the first aspect or any implementation of the first aspect.

[0099] It should also be noted that the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed across multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment. In addition, in the drawings of the device embodiments provided in this application, the connection relationship between the modules indicates that there is a communication connection between them, which can be specifically implemented as one or more communication buses or signal lines.

[0100] Through the description of the above embodiments, those skilled in the art can clearly understand that the present application can be implemented by means of software plus necessary general hardware, and of course can also be implemented by special hardware including application-specific integrated circuits, special CPUs, special memories, special components, etc. In general, all functions performed by computer programs can be easily implemented with corresponding hardware, and the specific hardware structures used to implement the same function can also be diverse, such as analog circuits, digital circuits or special circuits, etc. However, for the present application, software program implementation is a better implementation method in most cases. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a readable storage medium, such as a computer's floppy disk, USB flash drive, mobile hard disk, ROM, RAM, magnetic disk or optical disk, etc., and includes a number of instructions to enable a computer device (which can be a personal computer, training equipment, or network equipment, etc.) to execute the methods described in each embodiment of the present application.

[0101] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.

[0102] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, a computer, a training device or a data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, training device or data center. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a training device, a data center that includes one or more available media integrations. The available medium can be a magnetic medium, (for example, a floppy disk, a hard disk, a tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid-state drive (SSD)).

Claims

1. A method for preventing cache breakdown, characterized in that: Applied to the source station gateway, the method for preventing cache breakdown includes: Parsing the uniform resource locators of each received interface request respectively to obtain the uniform resource identifier and initial parameter string of each interface request; Calling a preset interference parameter elimination script to eliminate interference parameters from the initial parameter string, and obtaining a parameter string that only includes the source station access condition parameters corresponding to the uniform resource identifier; Concatenate the uniform resource identifier and the parameter string of each interface request to obtain a resource unique identifier corresponding to each interface request; The source station is accessed based on the resource unique identifier, and the resource request result fed back by the source station is sent to the sending end of each interface request corresponding to the resource unique identifier.

2. The method for preventing cache breakdown according to claim 1, characterized in that: The calling of a preset interference parameter elimination script to eliminate interference parameters from the initial parameter string to obtain a parameter string including only the source station access condition parameters corresponding to the uniform resource identifier includes: For each of the interface requests: Obtaining a rejection rule identifier corresponding to the uniform resource identifier of the interface request by querying a preset corresponding relationship table, and importing a rejection rule file corresponding to the rejection rule identifier into the preset interference parameter rejection script for initialization configuration; The preset interference parameter elimination script that has been initialized and configured is called to eliminate other interference parameters in the initial parameter string except the source station access condition parameter to obtain the parameter string.

3. The method for preventing cache breakdown according to claim 1, characterized in that: The accessing the source station based on the resource unique identifier and sending the resource request result fed back by the source station to the sending end of each interface request corresponding to the resource unique identifier includes: Counting the number of accesses of the interface requests with the same resource unique identifier within a preset time period, and when the number of accesses is greater than a preset threshold, performing source station access based on the resource unique identifier of the target interface request, and obtaining a resource request result corresponding to the resource unique identifier of the target interface request fed back by the source station, wherein the target interface request is any one of the multiple interface requests with the same resource unique identifier; The resource request result and the correspondence between the resource request result and the resource unique identifier are cached, and based on the correspondence between the resource unique identifier and the interface request and the correspondence between the resource request result and the resource unique identifier, the resource request result is sent to the sending end of each interface request.

4. The method for preventing cache breakdown according to claim 3, characterized in that: Before the source station access is performed based on the resource unique identifier requested by the target interface, the method further includes: Determine whether the resource request result having a corresponding relationship with the resource unique identifier corresponding to the target interface request is stored in the local cache; if so, based on the corresponding relationship between the resource unique identifier and the interface request, and the corresponding relationship between the resource request result and the resource unique identifier, send the resource request result in the local cache to the sending end of each interface request; If not, the operation step of accessing the source site based on the unique identifier of the resource requested by the target interface is executed.

5. The method for preventing cache breakdown according to claim 3, characterized in that: In the case where the number of accesses is not greater than the preset threshold, the method further includes: Based on the resource unique identifiers corresponding to the interface requests, the source station is accessed concurrently to obtain the resource request results corresponding to the resource unique identifiers.

6. The method for preventing cache breakdown according to claim 3, characterized in that: Before caching the resource request result and the corresponding relationship between the resource request result and the resource unique identifier, the method further includes: Determine whether the HTTP status code in the resource request result is an HTTP status code indicating a successful resource request, and if so, execute the operation step of caching the resource request result and the corresponding relationship between the resource request result and the resource unique identifier; If not, then based on the correspondence between the resource unique identifier and the interface request, and the correspondence between the resource request result and the resource unique identifier, after the resource request result is sent to the sending end of each interface request, the resource request result including the HTTP status code that does not represent the success of the resource request will be deleted.

7. A source station gateway, characterized in that: The source station gateway includes: A parameter parsing module, used to parse the uniform resource locator of each received interface request respectively, and obtain the uniform resource identifier and initial parameter string of each interface request; A parameter elimination module, used for calling a preset interference parameter elimination script to eliminate interference parameters from the initial parameter string, and obtaining a parameter string including only the source station access condition parameters corresponding to the uniform resource identifier; A parameter concatenation module, used to concatenate the uniform resource identifier and the parameter string of each interface request to obtain a resource unique identifier corresponding to each interface request; The resource sending module is used to access the source station based on the resource unique identifier, and send the resource request result fed back by the source station to the sending end of each interface request corresponding to the resource unique identifier.

8. A computer program product, characterized in that The method comprises computer-readable instructions, and when the computer-readable instructions are executed on an electronic device, the electronic device implements the method for preventing cache breakdown as claimed in any one of claims 1 to 6.

9. An electronic device, characterized in that: The method comprises at least one processor and a memory connected to the processor, wherein: The memory is used to store computer programs; The processor is used to execute the computer program so that the electronic device can implement the method for preventing cache breakdown as claimed in any one of claims 1 to 6.

10. A computer storage medium, characterized in that: The storage medium carries one or more computer programs, and when the one or more computer programs are executed by an electronic device, the electronic device can implement the method for preventing cache breakdown as described in any one of claims 1 to 6.

Images