CN116208676A - Data back-source method, device, computer equipment, storage medium and program product - Google Patents

Abstract

The present application relates to a data back-to-source method, device, computer equipment, storage medium and computer program product. The method includes: receiving a data back-to-source request, the data back-to-source request carrying a domain name and a back-to-source path; rewriting the back-to-source path according to the domain name to obtain a rewritten back-to-source path, and the rewritten back-to-source path The domain name in the source path corresponds to the first-level directory in the source site, and the return-to-source path is the resource path under the first-level directory; query the source site according to the rewritten back-to-source path to obtain the corresponding data, and return The queried data. By adopting this method, resources can be isolated, and subsequent maintenance is simple.

Description

Data return method, device, computer equipment, storage medium and program product

technical field

The present application relates to the technical field of cloud computing, and in particular to a method, device, computer equipment, storage medium and computer program product for data back-to-source.

Background technique

A CDN (Content Delivery Network) is established and covered on the bearer network, and is a distributed network composed of edge node server groups all over the world. The CDN can share the pressure of the source station, avoid network congestion, and ensure Accelerate the distribution of website content in different regions and scenarios, and improve the speed of resource access. It is often used in the deployment of static web pages) domain name back to the source of an OSS bucket (OSS: Object Storage OSS (Object Storage Service) is a massive, safe, low-cost , Highly reliable cloud storage service. Bucket: means storage space, which is a container for users to store objects (Object). All objects must belong to a certain storage space. Storage space has various configuration attributes, including region, Access rights, storage types, etc. Users can create different types of storage space to store different data according to actual needs.) is one of the commonly used management methods for traditional static web page deployment. This method has fast access speed and convenient web page management and update. Advantage. However, as the business scale expands and the number of CDN domain names increases, the number of OSS buckets will also increase, leading to fragmented management and high maintenance costs in the later period.

In the traditional technology, there are still multiple CDN domain names back to the same OSS bucket, and each domain name uses the management method of a first-level folder of the OSS bucket according to the agreement. However, in this method, the resources of multiple domain names are not completely isolated. For example, the resource path under the domain name A plus the domain name B can access the resources of the domain name B. Therefore, complete resource isolation is not achieved, and later maintenance is difficult.

Contents of the invention

Based on this, it is necessary to provide a method, device, computer equipment, computer-readable storage medium, and computer program product capable of isolating resources and enabling simple subsequent maintenance to address the above-mentioned technical problems.

In the first aspect, the present application provides a data back-to-source method, the method comprising:

Receive a data back-to-source request, the data back-to-source request carries a domain name and a back-to-source path;

Rewrite the origin-returning path according to the domain name to obtain a rewritten origin-returning path, the domain name in the rewritten origin-returning path corresponds to the first-level directory in the origin station, and the origin-returning path is the first-level directory The resource path under;

Query the source site according to the rewritten back-to-source path to obtain corresponding data, and return the queried data.

In one of the embodiments, before querying the source site according to the rewritten back-to-source path to obtain the corresponding data, it also includes:

Query whether there is corresponding data cached in the node according to the rewritten back-to-source path;

When the corresponding data is cached in the node, the corresponding data is obtained from the node and returned;

When there is no corresponding data cached in the node, continue to the step of querying the source station to obtain corresponding data according to the rewritten back-to-source path.

In one of the embodiments, the rewriting the back-to-source path according to the domain name to obtain the rewritten back-to-source path includes:

Rewriting the back-to-source path to obtain an initial back-to-source path with a domain name;

Obtain the parameters in the data back-to-source request;

Perform rewriting to the rewritten back-to-source path according to the initial back-to-source path and the parameters.

In one of the embodiments, after rewriting the back-to-source path according to the domain name to obtain the rewritten back-to-source path, it further includes:

Added a rewrite back-to-source path in the request response header information;

The method also includes:

When debugging, query and display the rewritten back-to-origin path in the request response header information.

In one embodiment, the method also includes:

receiving a new domain name request, the new domain name request carrying at least one new domain name;

Configure the newly added domain name to be the same origin site;

A first-level directory corresponding to the added domain name is generated in the source site, and data corresponding to the added domain name is managed under the first-level directory.

In one of the embodiments, after configuring the newly added domain name to be the same origin site, it also includes:

Configure the return-to-origin path rewriting rules for the newly added domain name;

The rewriting of the back-to-source path according to the domain name to obtain the rewritten back-to-source path includes:

Obtain the rewriting rules of the back-to-source path corresponding to the domain name;

According to the rewriting rule of the back-to-source path, the back-to-source path is rewritten according to the domain name to obtain a rewritten back-to-source path.

In the second aspect, the present application also provides a device for returning data to the source, and the device includes:

A data back-to-source request receiving module, configured to receive a data back-to-source request, the data back-to-source request carrying a domain name and a back-to-source path;

A rewriting module, configured to rewrite the back-to-source path according to the domain name to obtain a rewritten back-to-source path, the domain name in the rewritten back-to-source path corresponds to the first-level directory in the source station, and the back-to-source path is the resource path under the first-level directory;

The back-to-source module is used to query the source station to obtain corresponding data according to the rewritten back-to-source path, and return the queried data.

In a third aspect, the present application further provides a computer device, including a memory and a processor, the memory stores a computer program, and the processor implements the steps of the method in any one of the above embodiments when executing the computer program.

In a fourth aspect, the present application further provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps of the method in any one of the above-mentioned embodiments are implemented.

In a fifth aspect, the present application further provides a computer program product, including a computer program, and when the computer program is executed by a processor, the steps of the method in any one of the above-mentioned embodiments are implemented.

The above data back-to-source method, device, computer equipment, storage medium and computer program product, after receiving the data back-to-source request, rewrite the back-to-source path according to the domain name to obtain the rewritten back-to-source path, because each domain name Share a source site and correspond to the first-level directory in the source site, so that different domain names do not need to use a first-level directory as agreed, which realizes the isolation of files, and the path back to the source is the resource path under the first-level directory. In this way, the domain names of different data are the same, and their back-to-source paths are also different, so the resources under each domain name are not related to each other, and there will be no problem that A domain name can access B domain name resources, and because only one source site is applicable, Domain names are divided into first-level directories, the rules are simple and clear, and it is also convenient for later management and maintenance.

Description of drawings

Fig. 1 is an application environment diagram of the method for data back-to-source in an embodiment;

Fig. 2 is a schematic flow chart of a data back-to-source method in an embodiment;

Fig. 3 is a flow chart of returning to the same OSS bucket after the back-to-origin request is rewritten by the edge script in an embodiment of the back-to-origin path;

FIG. 4 is a schematic flow chart of a data back-to-source method in another embodiment;

Figure 5 is a flow chart of the rewriting steps in one embodiment;

Fig. 6 is a structural block diagram of a data back-to-source device in an embodiment;

Figure 7 is an internal block diagram of a computer device in one embodiment.

Detailed ways

In order to make the purpose, technical solution and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present application, and are not intended to limit the present application.

The data back-to-source method provided in the embodiment of this application can be applied to the application environment shown in FIG. 1 . Wherein, the terminal 102 communicates with the server 104 through the network, and the server 104 communicates with the source station 106 .

Among them, the terminal 102 generates a data back-to-source request based on the domain name and the back-to-source path, and sends the data back-to-source request to the server 104, and the server 104 rewrites the back-to-source path according to the domain name to obtain a rewritten back-to-source path, and rewrites the back-to-source path The domain name in is corresponding to the first-level directory of the source station, and the return-to-source path is the resource path under the first-level directory, and the source station 106 is queried according to the rewritten back-to-source path to obtain the corresponding data, and the queried data is returned to the terminal 102 .

In this way, after receiving the data back-to-source request, the server 104 rewrites the back-to-source path according to the domain name to obtain the rewritten back-to-source path. Since each domain name shares one source site and corresponds to the first-level directory in the source site, In this way, different domain names do not need to use a first-level directory according to the agreement, which realizes the isolation of files, and the return-to-source path is the resource path under the above-mentioned first-level directory. In this way, the domain names of different data are the same, and their return-to-source paths are also different. , so the resources under each domain name are not related to each other, and there will be no problem that A domain name can access the resources of B domain name, and because only one source site is applicable, the domain name is divided by the first-level directory. The rules are simple and clear, and it is convenient Later management and maintenance.

Among them, the terminal 102 can be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, Internet of Things devices and portable wearable devices, and the Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart vehicle-mounted devices, etc. . Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, and the like. The server 104 can be implemented by an independent server or a server cluster composed of multiple servers. Among them, for the convenience of understanding, the server 104 in this application can be regarded as a CDN (Content Delivery Network, a content distribution network CDN is a distributed network that is established and covered on the bearer network and is composed of edge node server groups all over the world. CDN It can share the pressure of the source station, avoid network congestion, ensure the accelerated distribution of website content in different regions and scenarios, and improve resource access speed. It is often used for the deployment of static web pages.) clusters, including CDN gateways and CDN nodes, of which CDN gateways It is used to rewrite back to the source path, and there is data cached in the CDN node. The source site 106 is used to store back-to-source data, which may refer to an OSS Bucket, where Object Storage OSS (Object Storage Service) is a massive, safe, low-cost, and highly reliable cloud storage service. Bucket means a storage space, and it is a container for users to store objects. All objects must belong to a certain storage space. Storage spaces have various configuration properties, including region, access rights, storage type, and more. Users can create different types of storage space to store different data according to actual needs.

Back-to-origin means that when a client requests to access a resource, if the resource is not cached on the CDN node, the CDN node will go back to the origin site to obtain the resource.

In one embodiment, as shown in FIG. 2 , a data back-to-source method is provided. The method is applied to the server in FIG. 1 as an example for illustration, including the following steps:

S202: Receive a data back-to-source request, where the data back-to-source request carries a domain name and a back-to-source path.

Specifically, the data back-to-source request is a request for querying original data, and the data back-to-source request carries a domain name and a back-to-source path. The data back-to-source request can be regarded as the CDN link sent by the terminal.

Wherein the domain name is the electronic location of the source site composed of a string of names separated by dots, which can identify the location of the source site. The back-to-source path is the storage path of data in the origin server, such as the path for file access.

S204: Rewrite the origin-returning path according to the domain name to obtain the rewritten origin-returning path, the domain name in the rewritten origin-returning path corresponds to the first-level directory in the origin site, and the origin-returning path is a resource path under the first-level directory.

Specifically, the rewritten back-to-source path is obtained by modifying the back-to-source path according to the domain name, for example, combining the domain name and the back-to-source path according to the rewriting rules to obtain the The file path for data storage is generated. In this embodiment, in order to facilitate the data storage in the source site to the corresponding domain name folder, that is to say, the source site includes multiple first-level directories, and each first-level directory corresponds to a Domain name, for example, each first-level directory uses the corresponding domain name to execute commands. The data corresponding to the domain name is stored in the first-level directory corresponding to each domain name, and different data are stored in different folders. In this way, resources under multiple domain names They are not related to each other, and there will be no problem that domain name A can access resources in domain name B, and the CDN access link will not be affected by the OSS first-level directory, and there is no perception of use. In addition, because the OSS Bucket only uses one, the first-level folder Divided by domain name, the rules are simple and clear, and the cost of later management and maintenance is low. Subsequently, the path of the folder where the data is located can be rewritten by adding the domain name to the path to the source. Therefore, the rewriting rule is to add the path of the folder, that is, the path to the source to the corresponding domain name, that is, the domain name and the path to the source. stitching. The rewriting rules can be generated with the help of custom edge scripts, which can be used to customize and configure back-to-source logic like building blocks. EdgeScript (ES for short) is a toolbox for quickly implementing customized CDN/DCDN configurations. When CDN/DCDN When the standard configuration on the console cannot meet business needs, you can try to use edge scripts for simple programming.

S206: Query the source site according to the rewritten back-to-source path to obtain corresponding data, and return the queried data.

The source site is a storage space for storing data. The server queries the corresponding folder of the source site according to the rewritten back-to-source path to obtain the data, and returns the data to the terminal.

The server first queries the first-level directory according to the domain name in the rewritten back-to-source path, and then continues to obtain the corresponding data from the corresponding folder under the first-level directory according to the back-to-source path, and returns the read data to the terminal.

Specifically, as shown in FIG. 3 , FIG. 3 is a flow chart of returning to the same OSS bucket after the back-to-origin request is rewritten by the edge script to the back-to-origin path in one embodiment. Wherein, a terminal (shown as a client in the figure) sends a CDN link request. It should be noted that in this embodiment, for convenience, multiple terminals or one terminal can send multiple link requests, which is not specifically limited here. For example, there is Link Request 1: http://www.exampledomain.com/examplefile1.html . Link request 2: http://www.exampledomain1.com/examplefile3.html , etc., which will not be repeated here. When the request reaches the server, that is, the CDN edge node, the server (shown as the CDN edge node in the figure) rewrites the link request's back-to-source path. For example, link request 1 is rewritten from the back-to-source path examplefile1.html Write to rewrite back to the source path /www.exampledomain.com/examplefile1.html . Link request 2 is rewritten from the back-to-source path examplefile3.html to rewrite the back-to-source path /www.exampledomain1.com/examplefile3.html . Follow up by rewriting the back-to-source path to query the corresponding data in the OSS Bucket, as shown in the file directory structure of the OSS Bucket in Figure 3, in which the first-level directory is the domain name, and the second-level and above directories form the back-to-source path, which is convenient for query .

In the above data back-to-source method, after receiving the data back-to-source request, the back-to-source path is rewritten according to the domain name to obtain the rewritten back-to-source path. Directory correspondence, so that different domain names do not need to use a first-level directory according to the agreement, which realizes the isolation of files, and the return-to-source path is the resource path under the first-level directory. In this way, the domain names of different data are the same, and the return-to-source path They are also different, so the resources under each domain name are not related to each other, and there will be no problem that A domain name can access B domain name resources, and because only one origin site is applicable, the domain name is divided by the first-level directory, and the rules are simple and clear , It is also convenient for later management and maintenance.

In one of the embodiments, before querying the source site according to the rewritten back-to-source path to obtain the corresponding data, it also includes: querying whether there is corresponding data cached in the node according to the rewritten back-to-source path; when there is corresponding data cached in the node , get the corresponding data from the node, and return it; if there is no corresponding data cached in the node, continue to query the source station to obtain the corresponding data according to the rewritten back-to-source path.

The node refers to a CDN node, where some back-to-source data is stored in the cache of the CDN node.

Specifically, as shown in FIG. 4, FIG. 4 is a flow chart of a data back-to-source method in another embodiment. When a terminal request reaches a CDN node, the node gateway will process the request according to the pre-written edge script rules. If If the processed request hits the cache of the node, the result will be returned. If the request does not hit the cache, it will continue to return to the source OSS bucket. The edge script here is a piece of script code that can be run on the CDN node. Running refers to running the script code; the edge script has many built-in functions and methods to process requests, so it is called a toolbox. Developers write based on these functions and methods Script program code to achieve customized goals.

In one of the embodiments, rewriting the back-to-source path according to the domain name to obtain the rewritten back-to-source path includes: rewriting the back-to-source path to obtain an initial back-to-source path with a domain name; obtaining parameters in the data back-to-source request; The source path and parameters are rewritten to rewrite back to the source path.

Specifically, as shown in FIG. 5 , FIG. 5 is a flow chart of the rewriting steps in an embodiment. In this embodiment, the rewriting process for the back-to-source path mainly includes two steps. The first step is to construct a The initial back-to-source path, that is, to build a member uri with a domain name, and then rewrite the back-to-source and cached uri to keep the parameters unchanged. Among them, the first step is to construct the required uri and temporarily store it as a variable, but it has not yet been rewritten. Write, the second step is to use the variables of the first step to rewrite, keeping the parameters unchanged: it means that a link request may be followed by splicing parameters such as https://bixin.cn/m-ypp? source=1&test=1,? and? The following string is a parameter, which is not fixed and can be spliced at will by the request initiator.

In one of the embodiments, after rewriting the back-to-source path according to the domain name to obtain the rewritten back-to-source path, it also includes: adding a rewritten back-to-source path in the request response header information; the method also includes: during debugging, query And display the rewritten back-to-origin path in the request response header information.

Specifically, continue to combine with Figure 5, where the response header (request response header information) adds X-CDN-FILE-PATH, X is a customary naming convention, generally the prefix of custom header information, and CDN-FILE-PATH is CDN file path, this field is convenient for developers to check the actual path back to the source, and it is convenient for debugging and completion information.

In one of the embodiments, the above-mentioned data back-to-source method further includes: receiving a request for adding a new domain name, and the request for adding a domain name carries at least one new domain name; configuring the new domain name to be the same origin site; Add the first-level directory corresponding to the domain name, and manage the data corresponding to the newly added domain name under the first-level directory.

Specifically, in this embodiment, it is mainly the configuration process when adding a new domain name, in which CDN adds multiple domain names, and at this time the source site for configuring multiple domain names is the same source site, that is, the OSS Bucket, where the source site The first-level directory corresponds to the domain name. The name of the first-level directory in the preferred source site is the corresponding domain name. That is to say, when adding a domain name, add a first-level folder of the same domain name in the OSS bucket, and add Files can be managed here, and files in multiple folders do not affect each other.

In one of the embodiments, after configuring the newly added domain name as the same source site, it also includes: configuring the return-to-source path rewriting rules for the newly added domain name; rewriting the return-to-source path according to the domain name to obtain the rewritten return-to-source path, including : Obtain the origin-returning path rewriting rules corresponding to the domain name; through the rewriting rules of the origin-returning path, rewrite the origin-returning path according to the domain name to obtain the rewritten origin-returning path.

Specifically, configuring the return-to-origin path rewriting rule for the newly added domain name means writing the core code of the edge script’s return-to-origin path redirection; the return-to-origin path rewriting rule mainly realizes the following functions: construct a return-to-origin uri with a domain name, and splicing the domain names Before the path, modify the back-to-origin and cache uri, keep the parameters unchanged, and add X-CDN-FILE-PATH to the response header to identify the uri for back-to-origin redirection.

In the above example, multiple domain names are returned to the same OSS bucket. And introduce the use of CDN edge scripts to customize the back-to-source logic. The edge script rewrites the return-to-origin path to a path with a domain name prefix. The first-level folders in the OSS bucket are named after domain names, which facilitates the management of multi-domain files.

It should be understood that although the steps in the flow charts involved in the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed sequentially in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least some of the steps in the flow charts involved in the above embodiments may include multiple steps or stages, and these steps or stages are not necessarily executed at the same time, but may be executed at different times, The execution order of these steps or stages is not necessarily performed sequentially, but may be executed in turn or alternately with other steps or at least a part of steps or stages in other steps.

Based on the same inventive concept, an embodiment of the present application further provides a data return-to-source device for implementing the above-mentioned data return-to-source method. The solution to the problem provided by the device is similar to the implementation described in the above method, so the specific limitations in one or more embodiments of the data return device provided below can be referred to above for the data return method limited and will not be repeated here.

In one embodiment, as shown in FIG. 6 , a data back-to-source device is provided, including: a data back-to-source request receiving module 601, a rewriting module 602, and a back-to-source module 603, wherein:

The data back-to-source request receiving module 601 is configured to receive the data back-to-source request, and the data back-to-source request carries a domain name and a back-to-source path;

The rewriting module 602 is used to rewrite the back-to-source path according to the domain name to obtain the rewritten back-to-source path. The domain name in the rewritten back-to-source path corresponds to the first-level directory in the source station, and the back-to-source path is the resource under the first-level directory path;

The back-to-source module 603 is used to query the source site according to the rewritten back-to-source path to obtain corresponding data, and return the queried data.

In one of the embodiments, the above data returning device further includes:

The query module is used to query whether there is corresponding data cached in the node according to the rewritten back-to-source path; when the corresponding data is cached in the node, the corresponding data is obtained from the node and returned; data, continue to query the source site to obtain the corresponding data according to the rewritten back-to-source path.

In one of the embodiments, the above-mentioned rewriting module 602 includes:

The rewriting unit is used to rewrite the back-to-source path to obtain the initial back-to-source path with a domain name;

A parameter acquisition unit, configured to acquire parameters in the data back-to-source request;

The first rewriting unit is configured to rewrite to the rewritten back-to-source path according to the initial back-to-source path and parameters.

In one of the embodiments, the above data returning device further includes:

The rewriting module is used to add a rewriting back-to-source path in the request response header information;

The debugging module is used to query and display the rewritten back-to-source path in the request response header information during debugging.

In one of the embodiments, the above data returning device further includes:

A domain name adding module, configured to receive a request for adding a domain name, where the request for adding a domain name carries at least one new domain name;

The source site configuration module is used to configure the newly added domain name as the same source site;

The origin station processing module is used to generate a first-level directory corresponding to the newly added domain name in the origin station, and manage data corresponding to the newly added domain name under the first-level directory.

In one of the embodiments, the above data returning device further includes:

The rewrite rule configuration module is used to configure the return-to-source path rewrite rules for newly added domain names;

The above-mentioned rewriting module 602 includes:

A rewrite rule acquisition unit, configured to obtain the rewrite rule of the back-to-source path corresponding to the domain name;

The second rewriting unit is configured to rewrite the source-returning path according to the domain name to obtain the rewritten source-returning path through the rewriting rule of the source-returning path.

Each module in the above-mentioned data return-to-source device can be fully or partially realized by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, and can also be stored in the memory of the computer device in the form of software, so that the processor can invoke and execute the corresponding operations of the above-mentioned modules.

In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure may be as shown in FIG. 7 . The computer device includes a processor, a memory, an input/output interface (Input/Output, I/O for short), and a communication interface. Wherein, the processor, the memory and the input/output interface are connected through the system bus, and the communication interface is connected to the system bus through the input/output interface. Wherein, the processor of the computer device is used to provide calculation and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs and databases. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The computer device's database is used to store back-to-source data. The input/output interface of the computer device is used for exchanging information between the processor and external devices. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for returning data to the source is realized.

Those skilled in the art can understand that the structure shown in Figure 7 is only a block diagram of a part of the structure related to the solution of this application, and does not constitute a limitation to the computer equipment on which the solution of this application is applied. The specific computer equipment can be More or fewer components than shown in the figures may be included, or some components may be combined, or have a different arrangement of components.

In one embodiment, a computer device is provided, including a memory and a processor, a computer program is stored in the memory, and the processor implements the following steps when executing the computer program: receiving a data back-to-source request, where the data back-to-source request carries a domain name and the return-to-source path; the rewritten return-to-source path is obtained by rewriting the return-to-source path according to the domain name, the domain name in the rewritten return-to-source path corresponds to the first-level directory in the source station, and the return-to-source path is the resource path under the first-level directory; Query the source site according to the rewritten back-to-source path to obtain the corresponding data, and return the queried data.

In one embodiment, when the processor executes the computer program, before querying the source site according to the rewritten back-to-source path to obtain the corresponding data, it also includes: querying whether there is corresponding data cached in the node according to the rewritten back-to-source path; when When the corresponding data is cached in the node, the corresponding data is obtained from the node and returned; when the corresponding data is not cached in the node, the step of querying the source station to obtain the corresponding data according to the rewritten back-to-source path is continued.

In one embodiment, when the processor executes the computer program, rewriting the back-to-source path according to the domain name to obtain the rewritten back-to-source path includes: rewriting the back-to-source path to obtain an initial back-to-source path with a domain name; obtaining data back-to-source Parameters in the request; rewrite to the rewritten back-to-source path according to the initial back-to-source path and parameters.

In one embodiment, after the processor executes the computer program to rewrite the back-to-source path according to the domain name to obtain the rewritten back-to-source path, it further includes: adding a rewritten back-to-source path in the request response header information; processing The following steps are also implemented when the server executes the computer program: when debugging, query and display the rewritten back-to-source path in the request response header information.

In one embodiment, when the processor executes the computer program, the following steps are also implemented: receiving a request for adding a domain name, and the request for adding a domain name carries at least one new domain name; configuring the new domain name to be the same origin site; generating The first-level directory corresponding to the new domain name, and manage the data corresponding to the new domain name under the first-level directory.

In one embodiment, after the processor executes the computer program, after configuring the newly added domain name to be the same source site, it further includes: configuring the return-to-origin path rewriting rules for the newly added domain name; when the processor executes the computer program, according to the domain name pair Rewriting the back-to-source path to obtain a rewritten back-to-source path includes: obtaining the back-to-source path rewriting rules corresponding to the domain name; rewriting the back-to-source path according to the domain name through the back-to-source path rewriting rules to obtain the rewritten back-to-source path.

In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented: receiving a data back-to-source request, where the data back-to-source request carries a domain name and a back-to-source path; the rewritten path to the source is obtained by rewriting the path to the source according to the domain name. The back-to-source path queries the source site to obtain the corresponding data, and returns the queried data.

In one embodiment, when the computer program is executed by the processor, before querying the source site according to the rewritten back-to-source path to obtain the corresponding data, it further includes: querying whether there is corresponding data cached in the node according to the rewritten back-to-source path; When the corresponding data is cached in the node, the corresponding data is obtained from the node and returned; when the corresponding data is not cached in the node, continue the step of querying the source site to obtain the corresponding data according to the rewritten back-to-source path.

In one embodiment, when the computer program is executed by the processor, rewriting the back-to-source path according to the domain name to obtain the rewritten back-to-source path includes: rewriting the back-to-source path to obtain an initial back-to-source path with a domain name; Parameters in the source request; rewrite to the rewritten back-to-source path according to the initial back-to-source path and parameters.

In one embodiment, after the computer program is executed by the processor to rewrite the back-to-source path according to the domain name to obtain the rewritten back-to-source path, it further includes: adding the rewritten back-to-source path in the request response header information; When the computer program is executed by the processor, the following steps are also implemented: during debugging, query and display the rewritten back-to-source path in the request response header information.

In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: receiving a new domain name request, the new domain name request carries at least one new domain name; configuring the new domain name to be the same source site; Generate a first-level directory corresponding to the newly added domain name, and manage data corresponding to the newly added domain name under the first-level directory.

In one embodiment, after the computer program is executed by the processor, after configuring the newly added domain name to be the same source site, it further includes: configuring the return-to-origin path rewriting rules for the newly added domain name; when the computer program is executed by the processor, according to The domain name rewrites the back-to-source path to obtain the rewritten back-to-source path, including: obtaining the back-to-source path rewriting rules corresponding to the domain name; through the back-to-source path rewriting rules, rewriting the back-to-source path according to the domain name to obtain the rewritten back-to-source path path.

In one embodiment, a computer program product is provided, including a computer program. When the computer program is executed by a processor, the following steps are implemented: receiving a data back-to-source request, where the data back-to-source request carries a domain name and a back-to-source path; according to the domain name Rewrite the back-to-source path to obtain the rewritten back-to-source path, the domain name in the rewritten back-to-source path corresponds to the first-level directory in the source site, and the back-to-source path is the resource path under the first-level directory; query based on the rewritten back-to-source path The source station obtains the corresponding data and returns the queried data.

In one embodiment, when the computer program is executed by the processor, before querying the source site according to the rewritten back-to-source path to obtain the corresponding data, it further includes: querying whether there is corresponding data cached in the node according to the rewritten back-to-source path; When the corresponding data is cached in the node, the corresponding data is obtained from the node and returned; when the corresponding data is not cached in the node, continue the step of querying the source site to obtain the corresponding data according to the rewritten back-to-source path.

In one embodiment, when the computer program is executed by the processor, rewriting the back-to-source path according to the domain name to obtain the rewritten back-to-source path includes: rewriting the back-to-source path to obtain an initial back-to-source path with a domain name; Parameters in the source request; rewrite to the rewritten back-to-source path according to the initial back-to-source path and parameters.

In one embodiment, after the computer program is executed by the processor to rewrite the back-to-source path according to the domain name to obtain the rewritten back-to-source path, it further includes: adding the rewritten back-to-source path in the request response header information; When the computer program is executed by the processor, the following steps are also implemented: during debugging, query and display the rewritten back-to-source path in the request response header information.

In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: receiving a new domain name request, the new domain name request carries at least one new domain name; configuring the new domain name to be the same source site; Generate a first-level directory corresponding to the newly added domain name, and manage data corresponding to the newly added domain name under the first-level directory.

In one embodiment, after the computer program is executed by the processor, after configuring the newly added domain name to be the same source site, it further includes: configuring the return-to-origin path rewriting rules for the newly added domain name; when the computer program is executed by the processor, according to The domain name rewrites the back-to-source path to obtain the rewritten back-to-source path, including: obtaining the back-to-source path rewriting rules corresponding to the domain name; through the back-to-source path rewriting rules, rewriting the back-to-source path according to the domain name to obtain the rewritten back-to-source path path.

It should be noted that the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all It is information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above-mentioned embodiments can be completed by instructing related hardware through computer programs, and the computer programs can be stored in a non-volatile computer-readable memory In the medium, when the computer program is executed, it may include the processes of the embodiments of the above-mentioned methods. Wherein, any reference to storage, database or other media used in the various embodiments provided in the present application may include at least one of non-volatile and volatile storage. Non-volatile memory can include read-only memory (Read-Only Memory, ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive variable memory (ReRAM), magnetic variable memory (Magnetoresistive Random Access Memory, MRAM), Ferroelectric Random Access Memory (FRAM), Phase Change Memory (Phase Change Memory, PCM), graphene memory, etc. The volatile memory may include random access memory (Random Access Memory, RAM) or external cache memory. As an illustration and not a limitation, RAM can be in various forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (Dynamic Random Access Memory, DRAM). The databases involved in the various embodiments provided in this application may include at least one of a relational database and a non-relational database. The non-relational database may include a blockchain-based distributed database, etc., but is not limited thereto. The processors involved in the various embodiments provided by this application can be general-purpose processors, central processing units, graphics processors, digital signal processors, programmable logic devices, data processing logic devices based on quantum computing, etc., and are not limited to this.

The technical features of the above embodiments can be combined arbitrarily. To make the description concise, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features, they should be It is considered to be within the range described in this specification.

The above-mentioned embodiments only express several implementation modes of the present application, and the description thereof is relatively specific and detailed, but should not be construed as limiting the patent scope of the present application. It should be noted that those skilled in the art can make several modifications and improvements without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application should be determined by the appended claims.

Claims (10)

1. A method of data back source, the method comprising:

receiving a data source return request, wherein the data source return request carries a domain name and a source return path;

the source return path is rewritten according to the domain name to obtain a rewritten source return path, the domain name in the rewritten source return path corresponds to a primary directory in a source station, and the source return path is a resource path under the primary directory;

and inquiring the source station according to the rewritten source return path to obtain corresponding data, and returning the inquired data.

2. The method of claim 1, wherein before querying the source station for the corresponding data according to the rewriteback source path, further comprises:

inquiring whether corresponding data is cached in a node according to the rewriting source path;

when the corresponding data is cached in the node, acquiring the corresponding data from the node and returning the data;

and when the corresponding data is not cached in the node, continuing to query the source station according to the rewriting source path to obtain the corresponding data.

3. The method according to claim 1 or 2, wherein the overwriting the source-back path according to the domain name to obtain an overwriting source-back path comprises:

rewriting the source return path to obtain an initial source return path with a domain name;

acquiring parameters in the data source request;

and rewriting to a rewriting source-returning path according to the initial source-returning path and the parameters.

4. The method according to claim 1 or 2, wherein after the rewriting the source-return path according to the domain name to obtain the rewritten source-return path, the method further comprises:

newly adding a rewriting source-returning path in the request response header information;

the method further comprises the steps of:

and inquiring and displaying a rewriting source path in the request response header information when debugging.

5. The method according to claim 1 or 2, characterized in that the method further comprises:

receiving a new domain name adding request, wherein the new domain name adding request carries at least one new domain name;

configuring the newly added domain name as the same source station;

and generating a primary catalog corresponding to the newly added domain name in the source station, and managing data corresponding to the newly added domain name under the primary catalog.

6. The method of claim 5, wherein after said configuring said added domain name as the same source station, further comprising:

configuring a source return path rewriting rule of the newly added domain name;

and the step of rewriting the source return path according to the domain name to obtain a rewritten source return path, which comprises the following steps:

acquiring a source return path rewriting rule corresponding to the domain name;

and rewriting the source-returning path according to the domain name by the source-returning path rewriting rule to obtain a rewritten source-returning path.

7. A data source device, the device comprising:

the data back source request receiving module is used for receiving a data back source request, wherein the data back source request carries a domain name and a back source path;

the rewriting module is used for rewriting the source return path according to the domain name to obtain a rewritten source return path, the domain name in the rewritten source return path corresponds to a primary directory in a source station, and the source return path is a resource path under the primary directory;

and the source returning module is used for inquiring the source station according to the rewriting source returning path to obtain corresponding data and returning the inquired data.

8. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 6 when the computer program is executed.

9. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.

10. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.

Images