CN111931100B - Request processing system, method, apparatus, electronic device, and computer readable medium - Google Patents
Request processing system, method, apparatus, electronic device, and computer readable medium Download PDFInfo
- Publication number
- CN111931100B CN111931100B CN202010576545.2A CN202010576545A CN111931100B CN 111931100 B CN111931100 B CN 111931100B CN 202010576545 A CN202010576545 A CN 202010576545A CN 111931100 B CN111931100 B CN 111931100B
- Authority
- CN
- China
- Prior art keywords
- resource
- address
- target
- target resource
- parameter information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000012545 processing Methods 0.000 title claims abstract description 39
- 238000000034 method Methods 0.000 title claims description 24
- 238000006243 chemical reaction Methods 0.000 claims abstract description 108
- 238000003672 processing method Methods 0.000 claims abstract description 12
- 230000008859 change Effects 0.000 claims description 65
- 230000005540 biological transmission Effects 0.000 claims description 27
- 238000004590 computer program Methods 0.000 claims description 9
- 230000004044 response Effects 0.000 claims description 6
- 230000009466 transformation Effects 0.000 claims 1
- 238000010586 diagram Methods 0.000 description 19
- 238000004891 communication Methods 0.000 description 9
- 238000013519 translation Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 238000012546 transfer Methods 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
- G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
Abstract
The embodiment of the application discloses a request processing system, a request processing method, a request processing device, an electronic device and a computer readable medium. The system comprises front-end equipment, a proxy server, a resource conversion server and a back-end server; the proxy server is used for forwarding a resource address acquisition request sent by the front-end equipment to the back-end server so as to receive an original resource address returned by the back-end server; replacing the original IP address in the original resource address with the IP address of the resource conversion server, and returning the modified resource address to the front-end equipment; the front-end equipment is used for sending a target resource acquisition request containing parameter information to the resource conversion server based on the IP address in the modified resource address; the resource conversion server is used for determining the current resource address of the target resource based on the parameter information, acquiring the target resource from the current resource address, and returning the target resource to the front-end equipment. The embodiment improves the safety and stability of the system when the resource address is changed frequently.
Description
Technical Field
Embodiments of the present application relate to the field of computer technology, and in particular, to a request processing system, a method, an apparatus, an electronic device, and a computer readable medium.
Background
With the development of internet technology, the resource access amount of each platform is increased. The front-end device typically may send a request to the back-end server by the browser to obtain the required resources.
In the prior art, when the front-end device interacts with the back-end server, a request of the front-end device is generally forwarded to the back-end server through a proxy server (such as nginnx, etc.), and an address of a resource (such as a picture, a video, a text, etc.) returned by the back-end server is forwarded to the front-end device through the proxy server. Therefore, when the user views or downloads the resource in the front-end page, the user can request the corresponding resource according to the resource address returned by the proxy server. However, when the resource address is changed frequently, the request processing manner needs to modify the data in the back-end server frequently, which results in a large workload. Meanwhile, each time modification is performed, the back-end server needs to be restarted once, so that the safety and stability of the system are poor.
Disclosure of Invention
The embodiment of the application provides a request processing system, a request processing method, a request processing device, an electronic device and a computer readable medium, so as to reduce the workload when a resource address is changed frequently and improve the safety and the stability of the system when the resource address is changed frequently.
In a first aspect, an embodiment of the present application provides a request processing system, including: front-end equipment, a proxy server, a resource conversion server and a back-end server; the proxy server is used for forwarding a resource address acquisition request sent by the front-end equipment to the back-end server and receiving an original resource address returned by the back-end server, wherein the original resource address comprises an original IP address of equipment where the target resource is located and parameter information of the target resource; replacing the original IP address with the IP address of the resource conversion server to obtain a modified resource address; returning the modified resource address to the front-end equipment; the front-end equipment is used for sending a target resource acquisition request containing parameter information to the resource conversion server based on the IP address in the modified resource address; and the resource conversion server is used for determining the current resource address of the target resource based on the parameter information, acquiring the target resource from the current resource address and returning the target resource to the front-end equipment.
In a second aspect, an embodiment of the present application provides a request processing method, which is applied to a resource conversion server, where the resource conversion server is communicatively connected to a front-end device, and the front-end device is communicatively connected to a back-end server through a proxy server, where the method includes: receiving a target resource acquisition request sent by front-end equipment, wherein the target resource acquisition request comprises parameter information of target resources, the parameter information is acquired from a resource address by the front-end equipment, the resource address is acquired by a proxy server after modifying an IP address in an original resource address, and the original resource address is returned by a back-end server after receiving the resource address acquisition request forwarded by the front-end equipment through the proxy server; determining a current resource address of the target resource based on the parameter information; and acquiring the target resource from the current resource address, and returning the target resource to the front-end equipment.
In a third aspect, an embodiment of the present application provides a request processing apparatus, including: the device is applied to a resource conversion server, the resource conversion server is in communication connection with front-end equipment, and the front-end equipment is in communication connection with a back-end server through a proxy server, and the device comprises: the receiving unit is configured to receive a target resource acquisition request sent by the front-end equipment, wherein the target resource acquisition request comprises parameter information of target resources, the parameter information is acquired from a resource address by the front-end equipment, the resource address is obtained by the proxy server by replacing an original IP address in the original resource address with an IP address of the resource conversion server, and the original resource address is returned by the rear-end server after receiving the resource address acquisition request forwarded by the front-end equipment through the proxy server; a determining unit configured to determine a current resource address of the target resource based on the parameter information; and the return unit is configured to acquire the target resource from the current resource address and return the target resource to the front-end equipment.
In a fourth aspect, an embodiment of the present application provides an electronic device, including: one or more processors; and a storage device having one or more programs stored thereon, which when executed by the one or more processors, cause the one or more processors to implement the method as described in the second aspect.
In a fifth aspect, embodiments of the present application provide a computer readable medium having stored thereon a computer program which, when executed by a processor, implements a method as described in the second aspect.
The request processing system, the method, the device, the electronic equipment and the computer readable medium provided by the embodiment of the application forward the resource address acquisition request sent by the front-end equipment to the back-end server through the proxy server, so as to receive the original resource address returned by the back-end server, wherein the original resource address comprises the original IP address of the equipment where the target resource is located and the parameter information of the target resource. And then the original IP address is replaced by the IP address of the resource conversion server through the proxy server to obtain a modified resource address, so that the modified resource address is returned to the front-end equipment. And then, sending a target resource acquisition request containing parameter information to a resource conversion server through the front-end equipment based on the IP address in the modified resource address. And finally, determining the current resource address of the target resource based on the parameter information through the resource conversion server, acquiring the target resource from the current resource address, and returning the target resource to the front-end equipment. Therefore, a resource conversion server independent of the back-end server is introduced into the system, the current resource address of the target resource is determined through the resource conversion server, when the resource address is changed frequently, the data in the back-end server does not need to be modified frequently, the back-end server does not need to be restarted frequently, so that the workload is reduced, and the safety and the stability of the system are improved.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the accompanying drawings in which:
FIG. 1 is a schematic diagram of an interaction process between devices of a request processing system according to the present application;
FIG. 2 is a schematic diagram of an application scenario of a request processing system according to the present application;
FIG. 3 is a schematic diagram of an application scenario of a request processing system according to the present application;
FIG. 4 is a schematic diagram of an application scenario of a request processing system according to the present application;
FIG. 5 is a schematic diagram of an application scenario of a request processing system according to the present application;
FIG. 6 is a schematic diagram of an application scenario of a request processing system according to the present application;
FIG. 7 is a flow chart of one embodiment of a request processing method according to the present application;
FIG. 8 is a schematic diagram illustrating one embodiment of a request processing apparatus in accordance with the present application;
Fig. 9 is a schematic diagram of a computer system suitable for use in implementing an embodiment of the application.
Detailed Description
The application is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting of the application. It should be noted that, for convenience of description, only the portions related to the present application are shown in the drawings.
It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be combined with each other. The application will be described in detail below with reference to the drawings in connection with embodiments.
With further reference to FIG. 1, a schematic diagram of the various device interaction processes of a request processing system is shown. The request processing system comprises front-end equipment, a proxy server, a resource conversion server and a back-end server.
Here, the front-end device may be hardware or software. When the front-end device is hardware, it may be a variety of electronic devices supporting network information transfer, including but not limited to smartphones, tablet computers, electronic book readers, laptop portable computers, desktop computers, wearable devices, and the like. At this time, the head-end apparatus may make a request transmission through an application (e.g., browser) installed thereon. When the front-end device is software, the front-end device can be installed in the electronic device listed above. Which may be implemented as multiple software or software modules (e.g., to provide distributed services), or as a single software or software module. The present invention is not particularly limited herein.
Here, the proxy server may be a proxy web (network) server such as Nginx (engine x) or the like. The request (e.g., resource address acquisition request) of the front-end device may be forwarded to the back-end server, and the address of the resource (e.g., picture, video, text, etc.) returned by the back-end server may be forwarded to the front-end device. Thus, isolation of the front-end equipment from the back-end server is achieved.
Here, the resource conversion server may be a device that provides a resource conversion service, and the device may be hardware or software. When the apparatus is hardware, the apparatus may be implemented as a distributed server cluster formed by a plurality of servers, or may be implemented as a single server. When the apparatus is software, it may be implemented as a plurality of software or software modules (e.g. to provide distributed services), or as a single software or software module. The present invention is not particularly limited herein.
Here, the backend server may be a server that provides data support for the front-end devices. The backend server may interact with the front-end device through a proxy server to process resource address acquisition requests and the like. Similarly, the resource conversion server may be hardware or software. When the device is hardware, the device may be implemented as a distributed server cluster formed by a plurality of servers, or may be implemented as a single server. When the device is software, it may be implemented as a plurality of software or software modules (e.g., to provide distributed services), or as a single software or software module. The present invention is not particularly limited herein.
The device interaction process of the request processing system may include the steps of:
in step 101, the front-end device sends a resource address acquisition request to the proxy server.
In this embodiment, the front-end device may send a resource address acquisition request to the proxy server through the browser application in which it is installed. Here, a resource address acquisition request may be used to request a resource address. The resource address may refer to an access address of the resource, and in particular may refer to a URL (Uniform Resource Locator ) of the resource. The resources herein may be various network data such as pictures, video, text, etc.
In practice, the user may trigger the sending of the resource address acquisition request in various ways. For example, if a user clicks a certain link on a certain page through a browser, a resource address acquisition request may be sent through the browser to request a URL of a resource corresponding to the link. For another example, when a user inputs a certain search term in the search engine and clicks a search button, a resource address acquisition request may be sent through the browser to request a URL of a search result corresponding to the search term.
In step 102, the proxy server forwards the resource address acquisition request to the backend server.
In this embodiment, after receiving the resource address acquisition request sent by the front-end device, the proxy server may forward the resource address acquisition request to the back-end server.
Step 103, the back-end server returns the original resource address to the proxy server.
In this embodiment, after receiving the resource address acquisition request, the backend server may query and return the original resource address of the target resource requested by the resource address acquisition request. It should be noted that, the data returned by the back-end server to the proxy server may include other data besides the original resource address for supporting network communication, which is not limited in this embodiment.
In this embodiment, the original resource address may be the original URL of the target resource. It will be appreciated that the URL of the resource may be changed according to the business requirements, and thus the original URL may be the URL prior to the change of the target resource, i.e. the URL to be changed.
In this embodiment, the original resource address may include an original IP (Internet Protocol ) address of the device where the target resource is located and parameter information of the target resource. The device where the target resource is located is the device where the target resource is stored. Since the URL of the resource may be changed according to the service requirement and the changed content may be the IP address of the device where the target resource is located, the IP address in the original resource address may be referred to as the original IP address.
It should be noted that, the URL generally includes various information such as an IP address, a port, URL parameters, a path, a transmission protocol, and the like, and thus, parameter information herein may refer to information other than the IP address in the original URL of the target resource. Such as ports, URL parameters, paths, transport protocol information, etc.
And 104, the proxy server replaces the original IP address with the IP address of the resource conversion server to obtain the modified resource address.
In this embodiment, the proxy server may replace the original IP address in the original resource address with the IP address of the resource conversion server, thereby obtaining the modified resource address.
As an example, if the proxy server is nginix, the original IP address may be replaced by the IP address of the resource conversion server through the sub_filter module of the nginix. Specifically, if the original IP address is denoted by IP1 and the IP address of the resource translation server is denoted by IPs, the original IP address (i.e., IP 1) in the original resource address may be replaced with the IP address (i.e., IPs) of the resource translation server by adding the code sub_filter 'IP1"IPs', so that the modified resource address is directed to the resource translation server.
The proxy server returns the modified resource address to the head-end equipment, step 105.
And step 106, the front-end equipment sends a target resource acquisition request containing parameter information to the resource conversion server based on the IP address in the modified resource address.
In this embodiment, the IP address in the modified resource address (i.e., the modified URL) obtained by the front-end device is the IP address of the resource conversion server, and thus, the modified resource address points to the resource conversion server. In this regard, a target resource acquisition request may be sent to the resource conversion server to acquire the target resource. The target resource acquisition request herein may contain parameter information in the modified resource address that is the same as the parameter information in the original resource address.
In step 107, the resource conversion server determines the current resource address of the target resource based on the parameter information.
In this embodiment, the resource conversion server may determine the current resource address of the target resource based on the parameter information in the received target resource acquisition request. Here, different resource address conversion rules may be preset for different changing scenarios of the resource address, and the current resource address of the target resource may be generated based on the resource address conversion rules.
As an example, if the current resource address change scenario is to change the IP address in the original resource address (i.e., original URL), a new IP address may be stored in the resource conversion server in advance. After the resource conversion server receives the target resource acquisition request, the new IP address is combined with the parameter information in the target resource acquisition request to obtain a new URL, namely the current resource address. Here, the new URL is a URL obtained by replacing the IP address in the original URL with the new IP address.
As yet another example, if the current resource address change scenario is to change the path rule in the original resource address (i.e., the original URL), the correspondence between the original path and the new path may be preset, and the correspondence may be stored in the resource conversion server. After the resource conversion server receives the target resource acquisition request, the original path in the parameter information carried by the target resource acquisition request can be replaced by a new path corresponding to the original path.
In some scenarios, the proxy server will replace the original IP address with the IP address of the resource server if and only if the original IP address in the original resource address is some specified IP address. In this scenario, the resource conversion server may store the original IP address (i.e., the specified IP address) in advance, so that after replacing the original path in the parameter information with a new path, the original IP address is combined with the parameter information after updating the path to obtain a new URL, i.e., the current resource address.
In other scenarios, the original IP address may not be limited, e.g., the proxy server may replace the original IP address in the original resource address with the IP address of the resource server every time the proxy server receives the original resource address returned by the back-end server. In this scenario, the resource conversion server may also store in advance a correspondence between the resource ID and the IP address of the device where the resource is located. The original path in the parameter information carried by the target resource acquisition request can contain a resource ID, and the IP address of the equipment where the target resource is located can be determined based on the resource ID and the corresponding relation. Therefore, after the original path in the parameter information is replaced by a new path, the IP address of the equipment where the target resource is located and the parameter information after the path is updated can be combined to obtain a new URL, namely the current resource address.
It should be noted that, in the second scenario, when the IP address of the device where the target resource is located is not changed, the IP address recorded in the correspondence is the original IP address. When the IP address of the equipment where the target resource is located changes, the IP address recorded in the corresponding relation is the latest IP address, and the resource conversion server can maintain the corresponding relation so as to update the corresponding relation in real time. Therefore, when the IP address of the equipment where the target resource is located and the path of the resource are changed at the same time, the resource conversion server can also determine the current resource address.
Here, the resource address changing scenario and the resource address conversion rule may be set as needed, and the present invention is not limited to the above example.
In step 108, the resource translation server obtains the target resource from the current resource address.
In this embodiment, after determining the current resource address of the target resource, the resource conversion server may acquire the target resource from the current resource address.
In step 109, the resource conversion server returns the target resource to the head-end equipment.
As an example, fig. 2 shows a schematic diagram of an application scenario of a request processing system. As shown in fig. 2, after the browser (i.e., the front-end device) first initiates a request (e.g., a resource address acquisition request) to nglnx (which may be considered as a proxy server), the browser may jump to the back-end through the proxy server. The backend service cluster may return the original resource address based on the request. The original resource address contains the original IP address of the equipment where the target resource is located. Then, the negnx may modify the IP address in the original resource address to be the IP address of the resource conversion server through the sub_filter module, so that the modified resource address points to the resource conversion server. Thereafter, the nmginx can return the modified resource address to the browser. The browser receives the modified resource address, and can request the resource from the resource conversion server. After receiving the request of the browser, the resource conversion server can determine a new resource address (i.e. the current resource address) and acquire the resource from the new resource address, so as to forward the acquired resource to the browser. Here, the acquired resources may be resources in the new IP address, resources under the new rule path, third party resources, and the like.
Thus, the required resources can be acquired by the resource conversion server independent of the back-end server under the conditions of IP address change, path rule change, storage position change and the like. Therefore, when the resource address is changed frequently, the data in the back-end server does not need to be modified frequently, and the back-end server does not need to be restarted frequently, so that the workload is reduced, and the safety and the stability of the system are improved. In addition, under other changing scenes, the resource conversion server can also be used for determining the current resource address based on other rules, so that the expandability of the changing scene of the resource address is improved.
In some optional implementations of this embodiment, the resource translation server may first determine the resource address change type of the target resource when determining the current resource address of the target resource. Wherein the resource address change type may include, but is not limited to, at least one of: the IP address of the equipment where the target resource is located is changed, the path of the target resource is changed and the transmission protocol is changed. Then, the resource conversion server may determine the current resource address of the target resource based on the parameter information and the resource address change type.
In one scenario, the resource address change type is that the IP address of the device where the target resource is located is changed. At this time, the resource conversion server may acquire the current IP address of the device where the target resource is located. Then, the current resource address of the target resource is determined based on the current IP address and the parameter information. The current resource address is obtained by combining the current IP address and the parameter information.
As an example, fig. 3 shows a schematic diagram of an application scenario of a request processing system herein. As shown in fig. 3, after the browser (i.e., the front-end device) first initiates a request (e.g., a resource address acquisition request) to nglnx (which may be considered as a proxy server), the browser may jump to the back-end through the proxy server. The backend service cluster may return the original resource address based on the request. The original resource address contains the original IP address of the equipment where the target resource is located. Then, the nginnx may modify the original IP address (e.g., IP1 in fig. 3) in the original resource address to the IP address (e.g., IPs in fig. 3) of the resource conversion server through the sub_filter module, so that the modified resource address points to the resource conversion server. Thereafter, the nmginx can return the modified resource address to the browser. The browser receives the modified resource address, and can request the resource from the resource conversion server. Here, the IP address (e.g., IP1 in fig. 3) of the device where the target resource is located may be changed to IP2, IP3, IP4, or the like in fig. 3. After receiving the request of the browser, the resource conversion server can determine a new resource address based on the new IP address (such as IP2, IP3, or IP 4) and the parameter information carried in the request. Finally, the resource may be retrieved from the new resource address, thereby forwarding the retrieved resource to the browser.
Therefore, when the IP address in the resource address is changed, the resource is acquired by pointing to the changed IP address through the resource conversion server independent of the back-end server, data in the back-end server is not required to be modified, the back-end server is not required to be restarted, so that the workload is reduced, and the safety and the stability of the system are improved.
In another scenario, the original path of the target resource may be included in the parameter information. The path of the resource address change type as the target resource is changed. At this time, the resource conversion server may replace the original path in the parameter information with the current path of the target resource. Then, the current resource address of the target resource can be determined based on the original IP address of the storage device of the target resource and the parameter information after the path is replaced. The current resource address is obtained by combining the original IP address and the parameter information after the path replacement, and the like.
As an example, fig. 4 shows a schematic diagram of an application scenario of a request processing system herein. As shown in fig. 4, after the browser (i.e., the front-end device) first initiates a request (e.g., a resource address acquisition request) to nglnx (which may be considered as a proxy server), the browser may jump to the back-end through the proxy server. The backend service cluster may return the original resource address based on the request. The original resource address contains the original IP address of the equipment where the target resource is located. Then, the nginnx may modify the original IP address (e.g., IP in fig. 4) in the original resource address to the IP address (e.g., IPs in fig. 4) of the resource conversion server through the sub_filter module, so that the modified resource address points to the resource conversion server. Thereafter, the nmginx can return the modified resource address to the browser. The browser receives the modified resource address, and can request the resource from the resource conversion server. Here, the original path is path1, and the new path (path) may be path2, path3, path4, or the like. Thus, the resource conversion server can replace the original path1 in the parameter information with a new path (path 2, path3, path4, or the like). The resource conversion server may then obtain the required resources from the device to which the original IP address points according to the parameter information replaced with the new path, thereby forwarding the obtained resources to the browser.
Therefore, when the path in the resource address is changed, the resource is acquired by pointing to the resource address after the path is changed through the resource conversion server independent of the back-end server, data in the back-end server is not required to be modified, the back-end server is not required to be restarted, so that the workload is reduced, and the safety and the stability of the system are improved.
It should be noted that, the IP address of the device where the target resource is located and the path in the resource address may be changed at the same time. At this time, the operations of fig. 3 and 4 may be combined at the same time, and the target resource may be acquired according to the changed path in the device to which the changed IP address points.
In another scenario, the parameter information may include an identification (e.g., an ID) of the target resource. The resource conversion server may be connected or deployed with a database. The database may store the latest resource address corresponding to each resource identifier. At this time, the resource conversion server may query the database for a resource address associated with the identification of the target resource after receiving the target resource acquisition request. Thus, the queried resource address may be determined as the current resource address of the target resource.
As an example, fig. 5 shows a schematic diagram of an application scenario of a request processing system herein. As shown in fig. 5, after the browser (i.e., the front-end device) first initiates a request (e.g., a resource address acquisition request) to nglnx (which may be considered as a proxy server), the browser may jump to the back-end through the proxy server. The backend service cluster may return the original resource address based on the request. The original resource address contains the original IP address of the equipment where the target resource is located. Then, the nginnx may modify the original IP address (e.g., IP in fig. 5) in the original resource address to the IP address (e.g., IPs in fig. 5) of the resource conversion server through the sub_filter module, so that the modified resource address points to the resource conversion server. Thereafter, the nmginx can return the modified resource address to the browser. The browser receives the modified resource address, and can request the resource from the resource conversion server. At this time, the resource conversion server may query the database based on the ID of the resource in the parameter information in the request, thereby acquiring a new URL (i.e., new resource address) of the required resource. The database may include new URLs corresponding to respective resources. Different resources have different IDs, such as ID1, ID2, etc., respectively. The resource conversion server can acquire the resource according to the new URL after acquiring the new URL of the required resource, so that the acquired resource is forwarded to the browser.
Therefore, the resource conversion server independent of the back-end server queries the current resource address of the target resource from the database based on the identification of the target resource, data in the back-end server is not required to be modified, the back-end server is not required to be restarted, and therefore workload is reduced, and safety and stability of the system are improved.
In another scenario, the resource address change type is a change in a transfer Protocol, such as converting HTTP (Hyper Text Transfer Protocol ) to FTP (FILE TRANSFER Protocol, file transfer Protocol). At this time, the resource conversion server may acquire the IP address of the device where the target resource following the current transmission protocol is located. Then, the transport protocol information in the parameter information is replaced with the changed target transport protocol information (i.e., new transport protocol information). Finally, the current resource address of the target resource can be determined based on the acquired IP address and the parameter information after the transmission protocol replacement. The current resource address is obtained by combining the IP address with the parameter information after the transmission protocol replacement, and the like.
As an example, fig. 6 shows a schematic diagram of an application scenario of a request processing system herein. As shown in fig. 6, after the browser (i.e., the front-end device) first initiates a request (e.g., a resource address acquisition request) to nglnx (which may be considered as a proxy server), the browser may jump to the back-end through the proxy server. The backend service cluster may return the original resource address based on the request. The original resource address contains the original IP address of the equipment where the target resource is located. Then, the nginnx may modify the original IP address (e.g., IP in fig. 6) in the original resource address to the IP address (e.g., IPs in fig. 6) of the resource conversion server through the sub_filter module, so that the modified resource address points to the resource conversion server. Thereafter, the nmginx can return the modified resource address to the browser. The browser receives the modified resource address, and can request the resource from the resource conversion server. Here, the transmission protocol is changed from HTTP to FTP. The IP address of the device (e.g., FTP server) where the target resource following the current transmission protocol is located may be preconfigured in the resource conversion server. At this time, the resource conversion server may directly acquire the IP address from the local, so that a required resource is acquired from the FTP server pointed to by the IP address according to the parameter information, and the acquired resource is forwarded to the browser.
Therefore, when the transmission protocol is changed, the resource conversion server independent of the back-end server acquires the resource from the equipment following the changed transmission protocol, the data in the back-end server is not required to be modified, and the back-end server is not required to be restarted, so that the workload is reduced, and the safety and the stability of the system are improved.
According to the request processing system provided by the embodiment of the application, the resource address acquisition request sent by the front-end equipment is forwarded to the back-end server through the proxy server, so that the original resource address returned by the back-end server is received, wherein the original resource address comprises the original IP address of the equipment where the target resource is located and the parameter information of the target resource. And then the original IP address is replaced by the IP address of the resource conversion server through the proxy server to obtain a modified resource address, so that the modified resource address is returned to the front-end equipment. And then, sending a target resource acquisition request containing parameter information to a resource conversion server through the front-end equipment based on the IP address in the modified resource address. And finally, determining the current resource address of the target resource based on the parameter information through the resource conversion server, acquiring the target resource from the current resource address, and returning the target resource to the front-end equipment. Therefore, a resource conversion server independent of the back-end server is introduced into the system, the current resource address of the target resource is determined through the resource conversion server, when the resource address is changed frequently, the data in the back-end server does not need to be modified frequently, the back-end server does not need to be restarted frequently, so that the workload is reduced, and the safety and the stability of the system are improved.
Referring to FIG. 7, a flow 700 of one embodiment of a request processing method according to the present application is shown. The request processing method is applied to a resource conversion server, the resource conversion server is in communication connection with front-end equipment, and the front-end equipment is in communication connection with a back-end server through a proxy server. The request processing method comprises the following steps:
step 701, receiving a target resource acquisition request sent by a front-end device.
In this embodiment, the execution body of the request processing method (such as the above-described resource conversion server) may receive the target resource acquisition request sent by the front-end device. The target resource obtaining request may include parameter information of the target resource. The parameter information may be obtained from the resource address by the head-end equipment. The resource address may be obtained by modifying the IP address in the original resource address by the proxy server (e.g., modifying the original IP address of the device where the target resource is located to the IP address of the resource translation server, so as to direct the modified resource address to the resource translation server). The original resource address may be returned by the back-end server after receiving the resource address acquisition request forwarded by the front-end device via the proxy server.
Step 702, determining a current resource address of the target resource based on the parameter information.
In this embodiment, the execution body may determine the current resource address of the target resource based on the parameter information.
In some optional implementations of this embodiment, the execution body may determine a resource address change type of the target resource. The resource address change type comprises one or more of change of an IP address of equipment where the target resource is located, change of a path of the target resource and change of a transmission protocol. Then, the current resource address of the target resource may be determined based on the parameter information and the resource address change type.
In some optional implementations of this embodiment, in response to the change of the IP address of the device where the target resource is located in the resource address change type, the executing body may obtain a current IP address of the device where the target resource is located. Then, the current resource address of the target resource may be determined based on the current IP address and the parameter information.
In some optional implementations of this embodiment, the parameter information includes an original path of the target resource. In response to the change of the path of the target resource by the resource address change type, the execution body may replace the original path in the parameter information with the current path of the target resource. Then, the current resource address of the target resource may be determined based on the original IP address of the storage device of the target resource and the parameter information after the path is replaced.
In some optional implementations of this embodiment, the parameter information includes an identification of the target resource. The executing entity may query the database for the resource address associated with the identification. The queried resource address may then be determined to be the current resource address of the target resource.
In some optional implementations of this embodiment, in response to the change of the resource address type to the transport protocol, the executing entity may obtain the IP address of the device where the target resource that complies with the current transport protocol is located. Then, the current resource address of the target resource may be determined based on the acquired IP address and the parameter information.
Step 703, obtaining the target resource from the current resource address, and returning the target resource to the front-end device.
It should be noted that, the steps 701 to 703 may refer to the corresponding steps in the corresponding embodiment of fig. 1, and are not described herein.
According to the method provided by the embodiment of the application, the resource conversion server receives the target resource acquisition request containing the parameter information sent by the front-end equipment, then determines the current resource address of the target resource based on the parameter information, finally acquires the target resource from the current resource address, and returns the target resource to the front-end equipment. Thus, the current resource address of the target resource can be determined by the resource translation server independent of the backend server. When the resource address is changed frequently, the data in the back-end server does not need to be modified frequently, and the back-end server does not need to be restarted frequently, so that the workload is reduced, and the safety and the stability of the system are improved.
With further reference to fig. 8, as an implementation of the method shown in the foregoing figures, the present application provides an embodiment of a request processing apparatus, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 1, and the apparatus may be specifically applied to a resource conversion server, where the resource conversion server is communicatively connected to a front-end device, and where the front-end device is communicatively connected to a back-end server through a proxy server.
As shown in fig. 8, the request processing apparatus 800 according to the present embodiment includes: a receiving unit 801 configured to receive a target resource acquisition request sent by a front-end device, where the target resource acquisition request includes parameter information of a target resource, where the parameter information is acquired by the front-end device from a resource address, where the resource address is obtained by the proxy server by replacing an original IP address in an original resource address with an IP address of the resource conversion server, and where the original resource address is returned by the back-end server after receiving the resource address acquisition request forwarded by the front-end device via the proxy server; a determining unit 802 configured to determine a current resource address of the target resource based on the parameter information; and a return unit 803 configured to acquire the target resource from the current resource address, and return the target resource to the front-end device.
In some optional implementations of this embodiment, the determining unit 802 is further configured to: determining a resource address change type of the target resource, wherein the resource address change type comprises one or more of change of an IP address of equipment where the target resource is located, change of a path of the target resource and change of a transmission protocol; and determining the current resource address of the target resource based on the parameter information and the resource address change type.
In some optional implementations of this embodiment, the determining unit 802 is further configured to: responding to the change of the IP address of the equipment where the target resource is located by the resource address change type, and acquiring the current IP address of the equipment where the target resource is located; and determining the current resource address of the target resource based on the current IP address and the parameter information.
In some optional implementations of this embodiment, the parameter information includes an original path of the target resource; and the determining unit 802 is further configured to replace an original path in the parameter information with a current path of the target resource in response to a path change of the resource address change type to the target resource; and determining the current resource address of the target resource based on the original IP address of the storage device of the target resource and the parameter information after the path replacement.
In some optional implementations of this embodiment, the parameter information includes an identifier of the target resource; and, the determining unit 802 is further configured to query the database for a resource address associated with the identifier; and determining the queried resource address as the current resource address of the target resource.
In some optional implementations of this embodiment, the determining unit 802 is further configured to: responding to the resource address change type that the transmission protocol is changed, and acquiring the IP address of the equipment where the target resource conforming to the current transmission protocol is located; replacing the transmission protocol information in the parameter information with changed target transmission protocol information; and determining the current resource address of the target resource based on the acquired IP address and the parameter information of the parameter information after replacing the transmission information.
According to the device provided by the embodiment of the application, the resource conversion server receives the target resource acquisition request containing the parameter information sent by the front-end equipment, then determines the current resource address of the target resource based on the parameter information, finally acquires the target resource from the current resource address, and returns the target resource to the front-end equipment. Thus, the current resource address of the target resource can be determined by the resource translation server independent of the backend server. When the resource address is changed frequently, the data in the back-end server does not need to be modified frequently, and the back-end server does not need to be restarted frequently, so that the workload is reduced, and the safety and the stability of the system are improved.
Referring now to FIG. 9, there is illustrated a schematic diagram of a computer system 900 suitable for use in implementing an electronic device of an embodiment of the present application. The electronic device shown in fig. 9 is only an example, and should not impose any limitation on the functions and scope of use of the embodiments of the present application.
As shown in fig. 9, the computer system 900 includes a Central Processing Unit (CPU) 901, which can execute various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 902 or a program loaded from a storage section 908 into a Random Access Memory (RAM) 903. In the RAM 903, various programs and data necessary for the operation of the system 900 are also stored. The CPU 901, ROM 902, and RAM 903 are connected to each other through a bus 904. An input/output (I/O) interface 905 is also connected to the bus 904.
The following components are connected to the I/O interface 905: an input section 906 including a keyboard, a mouse, and the like; an output portion 907 including a display such as a Liquid Crystal Display (LCD) and a speaker; a storage portion 908 including a hard disk or the like; and a communication section 909 including a network interface card such as a LAN card, a modem, or the like. The communication section 909 performs communication processing via a network such as the internet. The drive 910 is also connected to the I/O interface 905 as needed. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on the drive 910 so that a computer program read out therefrom is installed into the storage section 908 as needed.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from the network via the communication portion 909 and/or installed from the removable medium 911. The above-described functions defined in the method of the present application are performed when the computer program is executed by a Central Processing Unit (CPU) 901. The computer readable medium according to the present application may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present application, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present application may be implemented in software or in hardware. The described units may also be provided in a processor, wherein the names of the units do not in some cases constitute a limitation of the unit itself.
As another aspect, the present application also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer readable medium carries one or more programs which, when executed by the apparatus, cause the apparatus to: receiving a target resource acquisition request sent by front-end equipment, wherein the target resource acquisition request comprises parameter information of target resources, the parameter information is acquired from a resource address by the front-end equipment, the resource address is obtained by modifying an IP address in an original resource address by the proxy server, and the original resource address is returned by the back-end server after receiving the resource address acquisition request forwarded by the front-end equipment through the proxy server; determining a current resource address of the target resource based on the parameter information; and acquiring the target resource from the current resource address, and returning the target resource to the front-end equipment.
The above description is only illustrative of the preferred embodiments of the present application and of the principles of the technology employed. It will be appreciated by persons skilled in the art that the scope of the application referred to in the present application is not limited to the specific combinations of the technical features described above, but also covers other technical features formed by any combination of the technical features described above or their equivalents without departing from the inventive concept described above. Such as the above-mentioned features and the technical features disclosed in the present application (but not limited to) having similar functions are replaced with each other.
Claims (13)
1. A request processing system, comprising: front-end equipment, a proxy server, a resource conversion server and a back-end server;
The proxy server is used for forwarding the resource address acquisition request sent by the front-end equipment to the back-end server and receiving an original resource address returned by the back-end server, wherein the original resource address comprises an original IP address of equipment where the target resource is located and parameter information of the target resource; replacing the original IP address with the IP address of the resource conversion server to obtain a modified resource address; returning the modified resource address to the front-end equipment;
the front-end equipment is used for sending a target resource acquisition request containing the parameter information to the resource conversion server based on the IP address in the modified resource address;
the resource conversion server is configured to determine a current resource address of the target resource based on the parameter information and the resource address change type:
The resource address change type comprises one or more of change of an IP address of equipment where the target resource is located, change of a path of the target resource and change of a transmission protocol;
Acquiring the target resource from the current resource address, and returning the target resource to the front-end equipment;
The original path in the parameter information of the target resource contains a resource ID, a corresponding relation exists between the resource ID and the IP address of the equipment where the target resource is located, and the corresponding relation is stored in the resource conversion server in advance.
2. The request processing system of claim 1, wherein the resource transformation server is further configured to:
Responding to the change of the IP address of the equipment where the target resource is located, and acquiring the current IP address of the equipment where the target resource is located;
and determining the current resource address of the target resource based on the current IP address and the parameter information.
3. The request processing system according to claim 1, wherein the parameter information includes an original path of the target resource; and
The resource conversion server is further configured to:
The original path in the parameter information is replaced by the current path of the target resource in response to the change of the path of the target resource by the resource address change type;
and determining the current resource address of the target resource based on the original IP address of the storage device of the target resource and the parameter information after the path replacement.
4. The request processing system of claim 1, wherein the parameter information includes an identification of the target resource; and
The resource conversion server is further configured to:
querying a database for a resource address associated with the identity;
and determining the queried resource address as the current resource address of the target resource.
5. The request processing system of claim 1, wherein the parameter information comprises transport protocol information; and
The resource conversion server is further configured to:
Responding to the resource address change type that the transmission protocol is changed, and acquiring the IP address of the equipment where the target resource conforming to the current transmission protocol is located;
replacing the transmission protocol information in the parameter information with changed target transmission protocol information;
And determining the current resource address of the target resource based on the acquired IP address and the parameter information after replacing the transmission information.
6. A method for processing a request, the method being applied to a resource conversion server, the resource conversion server being communicatively connected to a front-end device, the front-end device being communicatively connected to a back-end server through a proxy server, the method comprising:
Receiving a target resource acquisition request sent by front-end equipment, wherein the target resource acquisition request comprises parameter information of target resources, the parameter information is acquired from a resource address by the front-end equipment, the resource address is obtained by modifying an IP address in an original resource address into an IP address of a resource conversion server by the proxy server, and the original resource address is returned by the back-end server after receiving the resource address acquisition request forwarded by the front-end equipment through the proxy server;
determining a current resource address of the target resource based on the parameter information and the determined resource address change type:
The resource address change type comprises one or more of change of an IP address of equipment where the target resource is located, change of a path of the target resource and change of a transmission protocol;
Acquiring the target resource from the current resource address, and returning the target resource to the front-end equipment;
The original path in the parameter information of the target resource contains a resource ID, a corresponding relation exists between the resource ID and the IP address of the equipment where the target resource is located, and the corresponding relation is stored in the resource conversion server in advance.
7. The request processing method according to claim 6, wherein the determining the current resource address of the target resource based on the parameter information and the resource address change type of the target resource includes:
Responding to the change of the IP address of the equipment where the target resource is located, and acquiring the current IP address of the equipment where the target resource is located;
and determining the current resource address of the target resource based on the current IP address and the parameter information.
8. The request processing method according to claim 6, wherein the parameter information includes an original path of the target resource; and
The determining the current resource address of the target resource based on the parameter information and the resource address change type of the target resource includes:
The original path in the parameter information is replaced by the current path of the target resource in response to the change of the path of the target resource by the resource address change type;
and determining the current resource address of the target resource based on the original IP address of the storage device of the target resource and the parameter information after the path replacement.
9. The request processing method according to claim 6, wherein the parameter information includes an identification of the target resource; and
The determining the current resource address of the target resource based on the parameter information and the resource address change type of the target resource includes:
querying a database for a resource address associated with the identity;
and determining the queried resource address as the current resource address of the target resource.
10. The request processing method according to claim 6, wherein the determining the current resource address of the target resource based on the parameter information and the resource address change type of the target resource includes:
Responding to the resource address change type that the transmission protocol is changed, and acquiring the IP address of the equipment where the target resource conforming to the current transmission protocol is located;
And determining the current resource address of the target resource based on the acquired IP address and the parameter information.
11. A request processing apparatus for use with a resource conversion server, the resource conversion server being communicatively coupled to a head-end device, the head-end device being communicatively coupled to a back-end server via a proxy server, the apparatus comprising:
The receiving unit is configured to receive a target resource acquisition request sent by front-end equipment, wherein the target resource acquisition request comprises parameter information of target resources, the parameter information is acquired from a resource address by the front-end equipment, the resource address is obtained by the proxy server by replacing an original IP address in an original resource address with the IP address of the resource conversion server, and the original resource address is returned by the back-end server after receiving the resource address acquisition request forwarded by the front-end equipment through the proxy server;
a determining unit configured to determine a resource address change type of the target resource, and determine a current resource address of the target resource based on the parameter information and the resource address change type;
The resource address change type comprises one or more of change of an IP address of equipment where the target resource is located, change of a path of the target resource and change of a transmission protocol;
a return unit configured to acquire the target resource from the current resource address and return the target resource to the front-end device;
The original path in the parameter information of the target resource contains a resource ID, a corresponding relation exists between the resource ID and the IP address of the equipment where the target resource is located, and the corresponding relation is stored in the resource conversion server in advance.
12. An electronic device, comprising:
One or more processors;
a storage device having one or more programs stored thereon,
When executed by the one or more processors, causes the one or more processors to implement the method of any of claims 6-10.
13. A computer readable medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any of claims 6-10.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010576545.2A CN111931100B (en) | 2020-06-22 | 2020-06-22 | Request processing system, method, apparatus, electronic device, and computer readable medium |
| PCT/CN2020/118867 WO2021258575A1 (en) | 2020-06-22 | 2020-09-29 | Request processing system, method and apparatus, and electronic device and computer-readable medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010576545.2A CN111931100B (en) | 2020-06-22 | 2020-06-22 | Request processing system, method, apparatus, electronic device, and computer readable medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111931100A CN111931100A (en) | 2020-11-13 |
| CN111931100B true CN111931100B (en) | 2024-04-26 |
Family
ID=73317623
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010576545.2A Active CN111931100B (en) | 2020-06-22 | 2020-06-22 | Request processing system, method, apparatus, electronic device, and computer readable medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN111931100B (en) |
| WO (1) | WO2021258575A1 (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113468445B (en) * | 2021-05-24 | 2024-06-04 | 北京旷视科技有限公司 | Request processing method, apparatus, electronic device and computer readable medium |
| CN114500505B (en) * | 2022-01-19 | 2024-05-28 | 北京百度网讯科技有限公司 | Text processing method and device and electronic equipment |
| CN115118624B (en) * | 2022-06-28 | 2024-04-05 | 平安银行股份有限公司 | Method and device for diverting production flow, electronic equipment and storage medium |
| CN115314552B (en) * | 2022-06-30 | 2023-08-22 | 中汽创智科技有限公司 | Data processing method and device, electronic equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102104636A (en) * | 2009-12-22 | 2011-06-22 | 英特尔公司 | Domain name system lookup latency reduction |
| EP2536097A1 (en) * | 2011-06-15 | 2012-12-19 | Juniper Networks, Inc. | Network integrated dynamic resource routing |
| CN104105007A (en) * | 2013-04-09 | 2014-10-15 | 腾讯科技（深圳）有限公司 | Video loading method of mobile terminal, devices and system |
| CN108696481A (en) * | 2017-04-07 | 2018-10-23 | 北京京东尚科信息技术有限公司 | leak detection method and device |
| WO2020077497A1 (en) * | 2018-10-15 | 2020-04-23 | 华为技术有限公司 | Method and device for domain name resolution by sending key value to grs server |
| CN111107134A (en) * | 2019-11-29 | 2020-05-05 | 北京三快在线科技有限公司 | Connection control method and device, electronic equipment and readable storage medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10218633B2 (en) * | 2014-03-28 | 2019-02-26 | Amazon Technologies, Inc. | Implementation of a service that coordinates the placement and execution of containers |
| CN110661826B (en) * | 2018-06-28 | 2023-06-02 | 北京京东尚科信息技术有限公司 | Method for processing network request by proxy server side and proxy server |
| US10594602B2 (en) * | 2018-06-30 | 2020-03-17 | Hewlett Packard Enterprise Development Lp | Web services across virtual routing and forwarding |
-
2020
- 2020-06-22 CN CN202010576545.2A patent/CN111931100B/en active Active
- 2020-09-29 WO PCT/CN2020/118867 patent/WO2021258575A1/en active Application Filing
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102104636A (en) * | 2009-12-22 | 2011-06-22 | 英特尔公司 | Domain name system lookup latency reduction |
| EP2536097A1 (en) * | 2011-06-15 | 2012-12-19 | Juniper Networks, Inc. | Network integrated dynamic resource routing |
| CN104105007A (en) * | 2013-04-09 | 2014-10-15 | 腾讯科技（深圳）有限公司 | Video loading method of mobile terminal, devices and system |
| CN108696481A (en) * | 2017-04-07 | 2018-10-23 | 北京京东尚科信息技术有限公司 | leak detection method and device |
| WO2020077497A1 (en) * | 2018-10-15 | 2020-04-23 | 华为技术有限公司 | Method and device for domain name resolution by sending key value to grs server |
| CN111107134A (en) * | 2019-11-29 | 2020-05-05 | 北京三快在线科技有限公司 | Connection control method and device, electronic equipment and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2021258575A1 (en) | 2021-12-30 |
| CN111931100A (en) | 2020-11-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111931100B (en) | Request processing system, method, apparatus, electronic device, and computer readable medium | |
| CN108282529B (en) | System, method and device for publishing and subscribing data | |
| CN110557284B (en) | Data aggregation method and device based on client gateway | |
| CN112788126B (en) | Resource downloading method, device, server and storage medium | |
| CN111913738B (en) | Access request processing method, device, computing equipment and medium | |
| ATE293809T1 (en) | DIGITAL COMPUTER SYSTEM AND METHOD FOR ANSWERING INQUIRIES RECEIVED VIA AN EXTERNAL NETWORK | |
| CN107302597B (en) | Message file pushing method and device | |
| CN111581563A (en) | Page response method and device, storage medium and electronic equipment | |
| CN109831466B (en) | Micro-service business processing method and nginx server | |
| US20190102465A1 (en) | Api query extension | |
| CN113315706B (en) | Private cloud flow control method, device and system | |
| CN108924183B (en) | Method and device for processing information | |
| CN112579928A (en) | Page jump method, page jump device, computer equipment and computer readable storage medium | |
| US10868881B1 (en) | Loading web resources using remote resource pushing | |
| CN110267077B (en) | Offline caching method, device, terminal and readable storage medium | |
| JP7217181B2 (en) | WEARABLE DEVICE, INFORMATION PROCESSING METHOD, APPARATUS AND SYSTEM | |
| US9684638B2 (en) | Accessing location-based information on a mobile device | |
| CN113468445B (en) | Request processing method, apparatus, electronic device and computer readable medium | |
| CN110647327A (en) | Method and device for dynamic control of user interface based on card | |
| WO2015074058A2 (en) | Just-in-time processing of images | |
| CN112579877B (en) | Control method, device, storage medium and equipment of information source system | |
| CN111953718B (en) | Page debugging method and device | |
| CN112783842B (en) | Log collection method and device | |
| CN109005250B (en) | Method and device for accessing server | |
| US12001458B2 (en) | Multi-cloud object store access |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |