WO2021258575A1

WO2021258575A1 - Request processing system, method and apparatus, and electronic device and computer-readable medium

Info

Publication number: WO2021258575A1
Application number: PCT/CN2020/118867
Authority: WO
Inventors: 李小强; 张亮; 任彦达
Original assignee: 北京旷视科技有限公司
Priority date: 2020-06-22
Filing date: 2020-09-29
Publication date: 2021-12-30
Also published as: CN111931100B; CN111931100A

Abstract

Disclosed are a request processing system, method and apparatus, and an electronic device and a computer-readable medium. The system comprises a front-end device, a proxy server, a resource transformation server and a back-end server, wherein the proxy server is used for forwarding, to the back-end server, a resource address acquisition request sent by the front-end device, so as to receive an original resource address returned by the back-end server, replacing an original IP address in the original resource address with an IP address of the resource transformation server, and returning a modified resource address to the front-end device; the front-end device is used for sending, to the resource transformation server and on the basis of the IP address in the modified resource address, a target resource acquisition request that includes parameter information; and the resource transformation server is used for determining the current resource address of a target resource on the basis of the parameter information, acquiring the target resource from the current resource address, and returning the target resource to the front-end device. By means of the embodiments, the security and stability of a system are improved when frequent changes occur in terms of a resource address.

Description

Request processing system, method, device, electronic equipment and computer readable medium

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on June 22, 2020, the application number is 202010576545. 2, and the invention title is "request processing system, method, device, electronic equipment and computer readable medium", all of which The content is incorporated in this application by reference.

Technical field

The embodiments of the present application relate to the field of computer technology, and specifically relate to request processing systems, methods, devices, electronic equipment, and computer-readable media.

Background technique

With the development of Internet technology, the amount of resource visits on various platforms is increasing. The front-end device can usually send a request to the back-end server through a browser to obtain the required resources.

In the prior art, when a front-end device interacts with a back-end server, a proxy server (such as Nginx, etc.) is usually used to forward the request of the front-end device to the back-end server, and the resources returned by the back-end server ( Such as pictures, videos, texts, etc.) The address is forwarded to the front-end equipment. Therefore, when users view or download resources on the front-end page, they can request corresponding resources according to the resource address returned by the proxy server. However, when the resource address is frequently changed, this request processing method requires frequent modification of the data in the back-end server, resulting in a large workload. At the same time, every time a modification is made, the back-end server needs to be restarted, resulting in poor system security and stability.

Summary of the invention

The embodiment of the application proposes a request processing system, method, device, electronic device, and computer readable medium to reduce the workload when the resource address is frequently changed, and improve the security and stability of the system when the resource address is frequently changed .

In the first aspect, an embodiment of the present application provides a request processing system, including: a front-end device, a proxy server, a resource conversion server, and a back-end server; the proxy server is used to forward the resource address acquisition request sent by the front-end device to the back-end Server, and receive the original resource address returned by the back-end server, where the original resource address includes the original IP address of the device where the target resource is located and the parameter information of the target resource; the original IP address is replaced with the IP address of the resource conversion server to get the modification The resource address after the modification; the modified resource address is returned to the front-end device; the front-end device is used to send 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 uses To determine the current resource address of the target resource based on the parameter information, obtain the target resource from the current resource address, and return the target resource to the front-end device.

In the second aspect, the embodiments of the present application provide a request processing method, which is applied to a resource conversion server. The resource conversion server communicates with a front-end device, and the front-end device communicates with the back-end server through a proxy server. The method includes: receiving the front-end device The sent target resource acquisition request, where the target resource acquisition request includes parameter information of the target resource, the parameter information is obtained by the front-end device from the resource address, and the resource address is obtained by the proxy server by modifying the IP address in the original resource address, 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; based on the parameter information, the current resource address of the target resource is determined; the target resource is obtained from the current resource address, and the target resource is returned To the front-end equipment.

In a third aspect, an embodiment of the present application provides a request processing device. The device includes: applied to a resource conversion server, the resource conversion server communicates with a front-end device, and the front-end device communicates with the back-end server through a proxy server. The device includes : The receiving unit is configured to receive the target resource acquisition request sent by the front-end device. The target resource acquisition request includes parameter information of the target resource. The original IP address in the resource address is obtained by replacing the IP address of the resource conversion server. 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; the determining unit is configured to be based on parameters The information determines the current resource address of the target resource; the returning unit is configured to obtain the target resource from the current resource address and return the target resource to the front-end device.

In a fourth aspect, an embodiment of the present application provides an electronic device, including: one or more processors; a storage device, on which one or more programs are stored, when one or more programs are used by one or more processors Execution causes one or more processors to implement the method as described in the second aspect.

In the fifth aspect, an embodiment of the present application provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, the method as described in the second aspect is implemented.

The request processing system, method, device, electronic device, and computer-readable medium provided by the embodiments of the present application forward the resource address acquisition request sent by the front-end device to the back-end server through the proxy server, thereby receiving the original resource address returned by the back-end server , Where the original resource address includes the original IP address of the device where the target resource is located and the parameter information of the target resource. Then, the original IP address is replaced with the IP address of the resource conversion server through the proxy server, and the modified resource address is obtained, so that the modified resource address is returned to the front-end device. Afterwards, the front-end device sends a target resource acquisition request containing parameter information to the resource conversion server based on the IP address in the modified resource address. Finally, the resource conversion server determines the current resource address of the target resource based on the parameter information, obtains the target resource from the current resource address, and returns the target resource to the front-end device. As a result, a resource conversion server independent of the back-end server is introduced into the system. The resource conversion server determines the current resource address of the target resource. When the resource address changes frequently, there is no need to frequently modify the data in the back-end server. There is no need to restart the back-end server frequently, which reduces the workload and improves the security and stability of the system.

Description of the drawings

By reading the detailed description of the non-limiting embodiments with reference to the following drawings, other features, purposes, and advantages of the present application will become more apparent:

Fig. 1 is a schematic diagram of the interaction process between devices of the request processing system according to the present application;

Fig. 2 is a schematic diagram of an application scenario of the request processing system according to the present application;

Fig. 3 is a schematic diagram of an application scenario of the request processing system according to the present application;

Fig. 4 is a schematic diagram of an application scenario of the request processing system according to the present application;

Fig. 5 is a schematic diagram of an application scenario of the request processing system according to the present application;

Fig. 6 is a schematic diagram of an application scenario of the request processing system according to the present application;

Fig. 7 is a flowchart of an embodiment of a request processing method according to the present application;

Fig. 8 is a schematic structural diagram of an embodiment of a request processing apparatus according to the present application;

Fig. 9 is a schematic structural diagram of a computer system suitable for implementing an electronic device according to an embodiment of the present application.

Specific embodiment

The application will be further described in detail below with reference to the drawings and embodiments. It can be understood that the specific embodiments described here are only used to explain the related invention, but not to limit the invention. In addition, it should be noted that, for ease of description, only the parts related to the relevant invention are shown in the drawings.

It should be noted that the embodiments in this application and the features in the embodiments can be combined with each other if there is no conflict. Hereinafter, the present application will be described in detail with reference to the drawings and in conjunction with the embodiments.

With further reference to FIG. 1, it shows a schematic diagram of the interaction process of each device of the request processing system. The request processing system includes front-end equipment, proxy server, resource conversion server and back-end server.

Here, the front-end equipment can be hardware or software. When the front-end device is hardware, it can be various electronic devices that support network information transmission, including but not limited to smart phones, tablet computers, e-book readers, laptop portable computers, desktop computers, and wearable devices. At this time, the front-end device can send the request through an application (such as a browser) installed on it. When the front-end device is software, it can be installed in the electronic devices listed above. It can be implemented as multiple software or software modules (for example, to provide distributed services), or as a single software or software module. There is no specific limitation here.

Here, the proxy server may be a proxy web (network) server such as Nginx (engine x). The request of the front-end device (such as a resource address acquisition request) can be forwarded to the back-end server, and the address of the resource (such as pictures, videos, text, etc.) returned by the back-end server can be forwarded to the front-end device. In this way, the front-end equipment and the back-end server are isolated.

Here, the resource conversion server may be a device that provides resource conversion services, and the device may be hardware or software. When the device is hardware, it can be implemented as a distributed server cluster composed of multiple servers, or as a single server. When the device is software, it can be implemented as multiple software or software modules (for example, to provide distributed services), or as a single software or software module. There is no specific limitation here.

Here, the back-end server may be a server that provides data support for the front-end device. The back-end server can interact with the front-end device through the proxy server to process resource address acquisition requests and so on. Similarly, the resource conversion server can be hardware or software. When the device is hardware, it can be implemented as a distributed server cluster composed of multiple servers, or as a single server. When the device is software, it can be implemented as multiple software or software modules (for example, to provide distributed services), or as a single software or software module. There is no specific limitation here.

The interaction process of each device of the request processing system may include the following steps:

Step 101: The front-end device sends a resource address acquisition request to the proxy server.

In this embodiment, the front-end device can send a resource address acquisition request to the proxy server through a browser application installed on it. Here, the resource address acquisition request can be used to request the resource address. The resource address may refer to the access address of the resource, and specifically may refer to the URL (Uniform Resource Locator, Uniform Resource Locator) of the resource. The resources here can be various network data, such as pictures, videos, texts, etc.

In practice, the user can trigger the sending of the resource address acquisition request in various ways. For example, if a user clicks on a certain link on a certain page through a browser, he can send a resource address acquisition request through the browser to request the URL of the resource corresponding to the link. For another example, if a user enters a search term in a search engine and clicks a search button, he can send a resource address acquisition request through the browser to request the URL of the search result corresponding to the search term.

Step 102: The proxy server forwards the resource address acquisition request to the back-end 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 back-end server can query and return the original resource address of the target resource requested by the resource address acquisition request. It should be noted that, in addition to the original resource address, the data returned by the back-end server to the proxy server may also include other data 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 is understandable that the URL of the resource may be changed according to business needs, so the original URL may be the URL before the change of the target resource, that is, the URL to be changed.

In this embodiment, the original resource address may include the original IP (Internet Protocol, 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 here is the device storing the target resource. Since the URL of the resource may be changed according to business needs 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 called the original IP address.

It should be noted that the URL usually contains various information such as IP address, port, URL parameters, path, transmission protocol, etc. Therefore, the parameter information here may refer to information other than the IP address in the original URL of the target resource. Such as port, URL parameter, path, transmission protocol information, etc.

Step 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 can replace the original IP address in the original resource address with the IP address of the resource conversion server to obtain the modified resource address.

As an example, if the proxy server is Nginx, the sub_filter module of Nginx can be used to replace the original IP address with the IP address of the resource conversion server. Specifically, if IP1 is used to represent the original IP address and IPs is used to represent the IP address of the resource conversion server, the original IP address (ie IP1) in the original resource address can be replaced with the resource by adding the code sub_filter'IP1''IPs' Convert the IP address (ie IPs) of the server so that the modified resource address points to the resource conversion server.

Step 105: The proxy server returns the modified resource address to the front-end device.

Step 106: The front-end device sends a target resource acquisition request including 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 (that is, the modified URL) obtained by the front-end device is the IP address of the resource conversion server. Therefore, the modified resource address points to the resource conversion server. With this, a target resource acquisition request can be sent to the resource conversion server to acquire the target resource. The target resource acquisition request here may include parameter information in the modified resource address, and the parameter information is the same as the parameter information in the original resource address.

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 can be preset for different resource address change scenarios, and the current resource address of the target resource can be generated based on the resource address conversion rule.

As an example, if the current resource address change scenario is to change the IP address in the original resource address (that is, the original URL), the new IP address can be stored in the resource conversion server in advance. After the resource conversion server receives the target resource acquisition request, it combines the new IP address with the parameter information in the target resource acquisition request to obtain a new URL, that is, the current resource address. Here, the new URL is the URL obtained by replacing the IP address in the original URL with the new IP address.

As another example, if the current resource address change scenario is to change the path rule in the original resource address (or original URL), the corresponding relationship between the original path and the new path can be set in advance, and the corresponding relationship can be stored In the resource conversion server. After the resource conversion server receives the target resource acquisition request, it may replace the original path in the parameter information carried in the target resource acquisition request with a new path corresponding to the original path.

In some scenarios, if and only if the original IP address in the original resource address is a specified IP address, the proxy server will replace the original IP address with the IP address of the resource server. In this scenario, the resource conversion server can pre-store the original IP address (that is, the above-mentioned designated IP address), so that after replacing the original path in the parameter information with the new path, the original IP address and the updated path The parameter information is combined to obtain a new URL, that is, the current resource address.

In other scenarios, the original IP address may not be restricted. For example, every time the proxy server receives the original resource address returned by the back-end server, it can replace the original IP address in the original resource address with the IP address of the resource server . In this scenario, the resource conversion server may also pre-store the 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 in the target resource acquisition request may include a resource ID, and based on the resource ID and the foregoing corresponding relationship, the IP address of the device where the target resource is located can be determined. Therefore, after replacing the original path in the parameter information with the new path, the IP address of the device where the target resource is located can be combined with the updated path parameter information to obtain a new URL, that is, 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 has not changed, the IP address recorded in the correspondence is the original IP address. When the IP address of the device where the target resource is located changes, the IP address recorded in the correspondence is the latest IP address, and the resource conversion server can maintain the correspondence to update the correspondence in real time. Therefore, when the IP address of the device where the target resource is located and the path of the resource change at the same time, the resource conversion server can also determine the current resource address.

Here, the resource address change scenario and the resource address conversion rule can also be set as needed, and are not limited to the above examples.

Step 108: The resource conversion 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 can obtain the target resource from the current resource address.

Step 109: The resource conversion server returns the target resource to the front-end device.

As an example, FIG. 2 shows a schematic diagram of an application scenario of the request processing system. As shown in Figure 2, the browser (that is, the front-end device) first initiates a request (such as a resource address acquisition request) to Nginx (which can be regarded as a proxy server), and then jumps to the back-end through the proxy server. The back-end service cluster can return the original resource address based on the request. The original resource address contains the original IP address of the device where the target resource is located. Then, Nginx can modify the IP address in the original resource address to 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. After that, Nginx can return the modified resource address to the browser. After receiving the modified resource address, the browser can request the resource from the resource conversion server. After receiving the request from the browser, the resource conversion server can determine the new resource address (that is, the current resource address), and obtain the resource from the new resource address, thereby forwarding the obtained 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 so on.

As a result, when the IP address changes, path rules change, storage location changes, etc., the required resources can be obtained through the resource conversion server independent of the back-end server. Therefore, when the resource address is frequently changed, there is no need to frequently modify the data in the back-end server, and there is no need to frequently restart the back-end server, thereby reducing the workload and improving the security and stability of the system. In addition, in other change scenarios, the resource conversion server can also be used to determine the current resource address based on other rules, thereby improving the scalability of the resource address change scenario.

In some optional implementation manners of this embodiment, when determining the current resource address of the target resource, the resource conversion server may first determine the resource address change type of the target resource. The resource address change type may include but is not limited to at least one of the following: the IP address of the device 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 can 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 changes. At this time, the resource conversion server can obtain the current IP address of the device where the target resource is located. Then, based on the current IP address and parameter information, the current resource address of the target resource is determined. For example, by combining the current IP address and parameter information, the current resource address is obtained.

As an example, FIG. 3 shows a schematic diagram of the application scenario of the request processing system. As shown in Figure 3, the browser (that is, the front-end device) first initiates a request (such as a resource address acquisition request) to Nginx (which can be regarded as a proxy server), and then jumps to the back-end through the proxy server. The back-end service cluster can return the original resource address based on the request. The original resource address contains the original IP address of the device where the target resource is located. Then, Nginx can use the sub_filter module to modify the original IP address in the original resource address (IP1 in Figure 3) to the IP address of the resource conversion server (IPs in Figure 3), so that the modified resource address points to the resource conversion server. After that, Nginx can return the modified resource address to the browser. After receiving the modified resource address, the browser can request the resource from the resource conversion server. Here, the IP address of the device where the target resource is located (IP1 in FIG. 3) can be changed to IP2, IP3, or IP4 in FIG. 3, etc. After receiving the request from the browser, the resource conversion server can determine a new resource address based on the new IP address (such as IP2, IP3, or IP4, etc.) and the parameter information carried in the request. Finally, the resource can be obtained from the new resource address, so that the obtained resource is forwarded to the browser.

As a result, when the IP address in the resource address changes, the resource conversion server independent of the back-end server points to the changed IP address to obtain resources, without modifying the data in the back-end server or restarting the back-end server. This reduces the workload and improves the safety and stability of the system.

In another scenario, the parameter information may include the original path of the target resource. The resource address change type is that the path of the target resource changes. 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 replacement path. For example, by combining the original IP address and the parameter information after the replacement path, the current resource address is obtained.

As an example, Fig. 4 shows a schematic diagram of the application scenario of the request processing system. As shown in Figure 4, the browser (that is, the front-end device) first initiates a request (such as a resource address acquisition request) to Nginx (which can be regarded as a proxy server), and then it can jump to the back-end through the proxy server. The back-end service cluster can return the original resource address based on the request. The original resource address contains the original IP address of the device where the target resource is located. Then, Nginx can use the sub_filter module to modify the original IP address in the original resource address (IP in Figure 4) to the IP address of the resource conversion server (IPs in Figure 4), so that the modified resource address points to the resource conversion server. After that, Nginx can return the modified resource address to the browser. After receiving the modified resource address, the browser can request the resource from the resource conversion server. Here, the original path is path1, and the new path (path) can be path2, path3, or path4. Therefore, the resource conversion server can replace the original path path1 in the parameter information with a new path (path2, path3, or path4, etc.). Then, the resource conversion server can obtain the required resources from the device pointed to by the original IP address according to the parameter information replaced with the new path, and thus forward the obtained resources to the browser.

Therefore, when the path in the resource address changes, the resource conversion server independent of the back-end server points to the resource address after the changed path to obtain resources, without modifying the data in the back-end server or restarting the back-end server. This reduces the workload and improves the safety and stability of the system.

It should be noted that the IP address of the device where the target resource is located and the path in the resource address can be changed at the same time. At this time, the operations involved in FIG. 3 and FIG. 4 can be combined at the same time, in the device pointed to by the changed IP address, the target resource can be obtained according to the changed path.

In another scenario, the parameter information may include the identification (such as ID) of the target resource. The resource conversion server can be connected to or deployed with a database. The latest resource address corresponding to each resource identifier can be stored in the database. At this time, after receiving the target resource acquisition request, the resource conversion server may query the database for the resource address associated with the identifier of the target resource. Thus, the resource address that is queried can be determined as the current resource address of the target resource.

As an example, FIG. 5 shows a schematic diagram of the application scenario of the request processing system. As shown in Figure 5, the browser (that is, the front-end device) first initiates a request (such as a resource address acquisition request) to Nginx (which can be regarded as a proxy server), and then jumps to the back-end through the proxy server. The back-end service cluster can return the original resource address based on the request. The original resource address contains the original IP address of the device where the target resource is located. Then, Nginx can use the sub_filter module to modify the original IP address in the original resource address (IP in Figure 5) to the IP address of the resource conversion server (IPs in Figure 5), so that the modified resource address points to the resource conversion server. After that, Nginx can return the modified resource address to the browser. After receiving the modified resource address, the browser can request the resource from the resource conversion server. At this time, the resource conversion server can query the database based on the ID of the resource in the parameter information in the request, so as to obtain the new URL (that is, the new resource address) of the required resource. The database may include the new URL corresponding to each resource. Different resources have different IDs, such as ID1, ID2, and so on. After obtaining the new URL of the required resource, the resource conversion server can obtain the resource according to the new URL, thereby forwarding the obtained resource to the browser.

Therefore, the resource conversion server independent of the back-end server can query the current resource address of the target resource from the database based on the identification of the target resource, without modifying the data in the back-end server, and there is no need to restart the back-end server. The workload has improved the safety and stability of the system.

In another scenario, the type of resource address change is a change in the transfer protocol, such as converting HTTP (Hyper Text Transfer Protocol) to FTP (File Transfer Protocol). At this time, the resource conversion server can obtain the IP address of the device where the target resource that complies with the current transmission protocol is located. Then, the transmission protocol information in the parameter information is replaced with the changed target transmission protocol information (that is, the new transmission 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 replacing the transmission protocol. For example, by combining the IP address and the parameter information after replacing the transmission protocol, the current resource address is obtained.

As an example, FIG. 6 shows a schematic diagram of the application scenario of the request processing system. As shown in Figure 6, the browser (that is, the front-end device) first initiates a request (such as a resource address acquisition request) to Nginx (which can be regarded as a proxy server), and then it can jump to the back-end through the proxy server. The back-end service cluster can return the original resource address based on the request. The original resource address contains the original IP address of the device where the target resource is located. Then, Nginx can use the sub_filter module to modify the original IP address in the original resource address (IP in Figure 6) to the IP address of the resource conversion server (IPs in Figure 6), so that the modified resource address points to the resource conversion server. After that, Nginx can return the modified resource address to the browser. After receiving the modified resource address, the browser can request the resource from the resource conversion server. Here, the transfer protocol is changed from HTTP to FTP. The resource conversion server can be pre-configured with the IP address of the device (such as the FTP server) where the target resource that follows the current transfer protocol is located. At this time, the resource conversion server can directly obtain the IP address locally, thereby obtaining the required resource from the FTP server pointed to by the IP address according to the parameter information, and forwarding the obtained resource to the browser.

Therefore, when the transmission protocol is changed, the resource conversion server independent of the back-end server obtains resources from the devices that comply with the changed transmission protocol, without modifying the data in the back-end server, and without restarting the back-end server. Less workload and improved system safety and stability.

The request processing system provided by the embodiment of the present application forwards the resource address acquisition request sent by the front-end device to the back-end server through the proxy server, thereby receiving the original resource address returned by the back-end server, where the original resource address includes the device where the target resource is located The original IP address and the parameter information of the target resource. Then, the original IP address is replaced with the IP address of the resource conversion server through the proxy server, and the modified resource address is obtained, so that the modified resource address is returned to the front-end device. Afterwards, the front-end device sends a target resource acquisition request containing parameter information to the resource conversion server based on the IP address in the modified resource address. Finally, the resource conversion server determines the current resource address of the target resource based on the parameter information, obtains the target resource from the current resource address, and returns the target resource to the front-end device. As a result, a resource conversion server independent of the back-end server is introduced into the system. The resource conversion server determines the current resource address of the target resource. When the resource address changes frequently, there is no need to frequently modify the data in the back-end server. There is no need to restart the back-end server frequently, which reduces the workload and improves the security and stability of the system.

Please refer to FIG. 7, which shows a flow 700 of an embodiment of a request processing method according to the present application. The request processing method is applied to a resource conversion server, the above-mentioned resource conversion server is in communication connection with a front-end device, and the above-mentioned front-end device is in communication connection with the back-end server through a proxy server. The request processing method includes the following steps:

Step 701: Receive a target resource acquisition request sent by a front-end device.

In this embodiment, the execution subject of the request processing method (such as the aforementioned resource conversion server) can receive the target resource acquisition request sent by the front-end device. Wherein, the target resource acquisition request may include parameter information of the target resource. The above-mentioned parameter information can be obtained by the front-end device from the resource address. The above resource address can be obtained by the proxy server by modifying the IP address in the original resource address (for example, the original IP address of the device where the target resource is located is modified to the IP address of the resource conversion server, so that the modified resource address can point to the resource conversion server). The foregoing 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: Determine the current resource address of the target resource based on the parameter information.

In this embodiment, the above-mentioned execution subject may determine the current resource address of the target resource based on the parameter information.

In some optional implementation manners of this embodiment, the above-mentioned execution subject may determine the resource address change type of the above-mentioned target resource. Wherein, the aforementioned resource address change type includes one or more of the change of the IP address of the device where the target resource is located, the change of the path of the target resource, and the change of the transmission protocol. Then, the current resource address of the target resource can be determined based on the parameter information and the resource address change type.

In some optional implementation manners of this embodiment, in response to the resource address change type being the IP address of the device where the target resource is changed, the execution subject may obtain the current IP address of the device where the target resource is located. Then, the current resource address of the target resource can be determined based on the current IP address and the parameter information.

In some optional implementation manners of this embodiment, the foregoing parameter information includes the original path of the foregoing target resource. In response to the resource address change type being the path of the target resource being changed, the execution subject 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 replacement path.

In some optional implementation manners of this embodiment, the above-mentioned parameter information includes the identifier of the above-mentioned target resource. The above-mentioned execution subject can query the resource address associated with the above-mentioned identifier from the database. Then, the resource address found can be determined as the current resource address of the aforementioned target resource.

In some optional implementation manners of this embodiment, in response to the above-mentioned resource address change type being a transmission protocol change, the above-mentioned executive body may obtain the IP address of the device where the target resource that complies with the current transmission protocol is located. Then, the current resource address of the target resource can be determined based on the obtained IP address and the parameter information.

Step 703: Obtain the target resource from the current resource address, and return the target resource to the front-end device.

It should be noted that the foregoing steps 701 to 703 can refer to the corresponding steps in the embodiment corresponding to FIG. 1, which will not be repeated here.

In the method provided by the foregoing embodiment of the present application, the resource conversion server receives the target resource acquisition request containing parameter information sent by the front-end device, and then determines the current resource address of the target resource based on the parameter information, and finally acquires the target resource from the current resource address. And return the target resource to the front-end equipment. Thus, the current resource address of the target resource can be determined by the resource conversion server independent of the back-end server. When the resource address changes frequently, there is no need to frequently modify the data in the back-end server, and there is no need to frequently restart the back-end server, thereby reducing the workload and improving the security and stability of the system.

With further reference to FIG. 8, as an implementation of the methods shown in the above figures, this application provides an embodiment of a request processing apparatus. The apparatus embodiment corresponds to the method embodiment shown in FIG. Applied to a resource conversion server, the above-mentioned resource conversion server is in communication connection with a front-end device, and the above-mentioned front-end device is in a communication connection with the back-end server through a proxy server.

As shown in FIG. 8, the request processing apparatus 800 in this embodiment includes: a receiving unit 801 configured to receive a target resource acquisition request sent by a front-end device, wherein the target resource acquisition request includes parameter information of the target resource, The above-mentioned parameter information is obtained by the above-mentioned front-end device from the resource address, the above-mentioned resource address is obtained by the above-mentioned proxy server by replacing the original IP address in the original resource address with the IP address of the above-mentioned resource conversion server, and the above-mentioned original resource address is obtained by the above-mentioned back-end The server returns after receiving the resource address acquisition request forwarded by the front-end device via the above-mentioned proxy server; the determining unit 802 is configured to determine the current resource address of the above-mentioned target resource based on the above-mentioned parameter information; the returning unit 803 is configured to obtain the current resource address from the above-mentioned current Obtain the target resource from the resource address, and return the target resource to the front-end device.

In some optional implementation manners of this embodiment, the determining unit 802 is further configured to determine the resource address change type of the target resource, where the resource address change type includes a change in the IP address of the device where the target resource is located. One or more of a change in the path of the target resource and a change in the transmission protocol; based on the above parameter information and the above resource address change type, the current resource address of the above target resource is determined.

In some optional implementation manners of this embodiment, the determining unit 802 is further configured to: in response to the resource address change type being the IP address of the device where the target resource is changed, obtain the current IP of the device where the target resource is located. Address: Based on the current IP address and the parameter information, the current resource address of the target resource is determined.

In some optional implementation manners of this embodiment, the aforementioned parameter information includes the original path of the aforementioned target resource; and, the aforementioned determining unit 802 is further configured to respond to the occurrence of the aforementioned resource address change type being the path of the aforementioned target resource. Change, replace the original path in the parameter information with the current path of the target resource; determine 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 replacement path.

In some optional implementations of this embodiment, the above-mentioned parameter information includes the identifier of the above-mentioned target resource; and, the above-mentioned determining unit 802 is further configured to query the resource address associated with the above-mentioned identifier from the database; The resource address of is determined as the current resource address of the aforementioned target resource.

In some optional implementation manners of this embodiment, the above determining unit 802 is further configured to: in response to the above resource address change type being a transmission protocol change, obtain the IP address of the device where the target resource that complies with the current transmission protocol is located; Replace the transmission protocol information in the above parameter information with the changed target transmission protocol information; determine the current resource address of the above target resource based on the acquired IP address and the parameter information after replacing the transmission information.

The device provided by the foregoing embodiment of the present application receives a target resource acquisition request containing parameter information sent by a front-end device through a resource conversion server, and then determines the current resource address of the target resource based on the parameter information, and finally acquires the target resource from the current resource address, And return the target resource to the front-end equipment. Thus, the current resource address of the target resource can be determined by the resource conversion server independent of the back-end server. When the resource address changes frequently, there is no need to frequently modify the data in the back-end server, and there is no need to frequently restart the back-end server, thereby reducing the workload and improving the security and stability of the system.

Next, referring to FIG. 9, it shows a schematic structural diagram of a computer system 900 suitable for implementing an electronic device according to an embodiment of the present application. The electronic device shown in FIG. 9 is only an example, and should not bring any limitation to the function 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 be based on a program stored in a read-only memory (ROM) 902 or a program loaded from a storage portion 908 into a random access memory (RAM) 903 And perform various appropriate actions and processing. In the RAM 903, various programs and data required for the operation of the system 900 are also stored. The CPU 901, the ROM 902, and the 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, etc.; an output section 907 including a liquid crystal display (LCD), etc., and speakers, etc.; a storage section 908 including a hard disk, etc.; The communication part 909 of a network interface card such as a modem. 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, etc., is installed on the drive 910 as needed, so that the computer program read from it is installed into the storage portion 908 as needed.

In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments of the present disclosure include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program may be downloaded and installed from the network through the communication part 909, and/or installed from the removable medium 911. When the computer program is executed by the central processing unit (CPU) 901, the above-mentioned functions defined in the method of the present application are executed. It should be noted that the computer-readable medium described in this 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 may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or a combination of any of the above. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable Programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above. In this application, the computer-readable storage medium may be any tangible medium that contains or stores a program, and the program may be used by or in combination with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium may include a data signal propagated in a baseband or as a part of a carrier wave, and a computer-readable program code is carried therein. This propagated data signal can take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. The computer-readable signal medium may also be any computer-readable medium other than the computer-readable storage medium. The computer-readable medium may send, propagate, or transmit the program for use by or in combination with the instruction execution system, apparatus, or device . The program code contained on the computer-readable medium can be transmitted by any suitable medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation of the system architecture, functions, and operations of the system, method, and computer program product according to various embodiments of the present application. In this regard, each block in the flowchart or block diagram can represent a module, program segment, or part of code, and the module, program segment, or part of code contains one or more for realizing the specified logic function. Executable instructions. It should also be noted that, in some alternative implementations, the functions marked in the block may also occur in a different order from the order marked in the drawings. For example, two blocks shown one after the other can actually be executed substantially in parallel, or they can sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and/or flowchart, and the combination of the blocks in the block diagram and/or flowchart, can be implemented by a dedicated hardware-based system that performs the specified functions or operations Or it can be realized by a combination of dedicated hardware and computer instructions.

The units involved in the embodiments described in this application can be implemented in software or hardware. The described units can also be arranged in the processor, where the names of these units do not constitute a limitation on the unit itself under certain circumstances.

As another aspect, the present application also provides a computer-readable medium, which may be included in the device described in the above embodiment; or it may exist alone without being assembled into the device. The above-mentioned computer-readable medium carries one or more programs. When the above-mentioned one or more programs are executed by the apparatus, the apparatus is caused to receive a target resource acquisition request sent by the front-end equipment, wherein the target resource acquisition request The parameter information of the target resource, the parameter information is obtained by the front-end device from the resource address, the resource address is obtained by the proxy server by modifying the IP address in the original resource address, and the original resource address is obtained by the source The back-end server returns after receiving the resource address acquisition request forwarded by the front-end device via the proxy server; determines the current resource address of the target resource based on the parameter information; acquires the target from the current resource address Resource, and return the target resource to the front-end device.

The above description is only a preferred embodiment of the present application and an explanation of the applied technical principles. Those skilled in the art should understand that the scope of the invention involved in this application is not limited to the technical solutions formed by the specific combination of the above technical features, and should also cover the above technical features or technical solutions without departing from the above inventive concept. Other technical solutions formed by arbitrarily combining the equivalent features. For example, the above-mentioned features and the technical features disclosed in this application (but not limited to) with similar functions are mutually replaced to form a technical solution.

Claims

A request processing system, which is characterized by comprising: a front-end device, a proxy server, a resource conversion server, and a back-end server;

The proxy server is configured to forward the resource address acquisition request sent by the front-end device to the back-end server, and receive the original resource address returned by the back-end server, wherein the original resource address includes the target resource The original IP address of the device and the parameter information of the target resource; replace the original IP address with the IP address of the resource conversion server to obtain the modified resource address; return the modified resource address to the front-end device ；

The front-end device is configured to send a target resource acquisition request including 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 the current resource address of the target resource based on the parameter information, obtain the target resource from the current resource address, and return the target resource to the front-end device.
The request processing system according to claim 1, wherein the resource conversion server is further configured to:

Determine the resource address change type of the target resource, where the resource address change type includes one or more of changes in the IP address of the device where the target resource is located, changes in the path of the target resource, and changes in the transmission protocol;

Determine the current resource address of the target resource based on the parameter information and the resource address change type.
The request processing system according to claim 2, wherein the resource conversion server is further configured to:

In response to the resource address change type being that the IP address of the device where the target resource is located is changed, acquiring the current IP address of the device where the target resource is located;

Determine the current resource address of the target resource based on the current IP address and the parameter information.
The request processing system according to claim 2, wherein the parameter information includes the original path of the target resource; and,

The resource conversion server is further used for:

In response to the resource address change type being that the path of the target resource is changed, replacing the original path in the parameter information with the current path of the target resource;

Determine 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 replacement path.
The request processing system according to claim 2, wherein the parameter information includes an identifier of the target resource; and,

The resource conversion server is further used for:

Query the resource address associated with the identifier from the database;

The inquired resource address is determined as the current resource address of the target resource.
The request processing system according to claim 2, wherein the parameter information includes transmission protocol information; and,

The resource conversion server is further used for:

In response to the resource address change type being a transmission protocol change, obtaining the IP address of the device where the target resource that complies with the current transmission protocol is located;

Replacing the transmission protocol information in the parameter information with the changed target transmission protocol information;

Determine the current resource address of the target resource based on the acquired IP address and the parameter information after replacing the transmission information.
A request processing method, characterized in that it is applied to a resource conversion server, the resource conversion server is in communication connection with a front-end device, and the front-end device is in communication connection with a back-end server through a proxy server, and the method includes:

Receive a target resource acquisition request sent by a front-end device, where the target resource acquisition request includes parameter information of the target resource, the parameter information is acquired by the front-end device from a resource address, and the resource address is acquired by the proxy server Obtained by modifying the IP address in the original resource address to the IP address of the resource conversion server. The original resource address is obtained by the back-end server after receiving the resource address acquisition request forwarded by the front-end device via the proxy server return;

Determine the current resource address of the target resource based on the parameter information;

Obtain the target resource from the current resource address, and return the target resource to the front-end device.
The request processing method according to claim 7, wherein the determining the current resource address of the target resource based on the parameter information comprises:

Determine the resource address change type of the target resource, where the resource address change type includes one or more of changes in the IP address of the device where the target resource is located, changes in the path of the target resource, and changes in the transmission protocol;

Determine the current resource address of the target resource based on the parameter information and the resource address change type.
The request processing method according to claim 8, 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 comprises:

In response to the resource address change type being that the IP address of the device where the target resource is located is changed, acquiring the current IP address of the device where the target resource is located;

Determine the current resource address of the target resource based on the current IP address and the parameter information.
The request processing method according to claim 8, wherein the parameter information includes the 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:

In response to the resource address change type being that the path of the target resource is changed, replacing the original path in the parameter information with the current path of the target resource;

Based on the original IP address of the storage device of the target resource and the parameter information after the replacement path, the current resource address of the target resource is determined.
The request processing method according to claim 8, wherein the parameter information includes an identifier 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:

Query the resource address associated with the identifier from the database;

The inquired resource address is determined as the current resource address of the target resource.
The request processing method according to claim 8, 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 comprises:

In response to the resource address change type being a transmission protocol change, obtaining the IP address of the device where the target resource that complies with the current transmission protocol is located;

Based on the obtained IP address and the parameter information, the current resource address of the target resource is determined.
A request processing device, characterized in that it is applied to a resource conversion server, the resource conversion server is in communication connection with a front-end device, and the front-end device is in communication connection with a back-end server through a proxy server, and the device includes:

The receiving unit is configured to receive a target resource acquisition request sent by a front-end device, wherein the target resource acquisition request includes parameter information of the target resource, and the parameter information is acquired by the front-end device from the resource address, and the resource The address is obtained by the proxy server by replacing the original IP address in the original resource address with the IP address of the resource conversion server, and the original resource address is received by the back-end server after the front-end device passes the proxy server The forwarded resource address will be returned after obtaining the request;

The determining unit is configured to determine the current resource address of the target resource based on the parameter information;

The returning unit is configured to obtain the target resource from the current resource address and return the target resource to the front-end device.
An electronic device, characterized in that it comprises:

One or more processors;

A storage device on which one or more programs are stored,

When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 7-12.
A computer-readable medium with a computer program stored thereon, wherein the program is executed by a processor to implement the method according to any one of claims 7-12.