CN105959413B - Network proxy method and proxy system - Google Patents

Abstract

The present invention provides a proxy method for a network, comprising: performing domain name resolution on an access request, resolving the access request to a first proxy server among a plurality of proxy servers, the plurality of proxy servers being deployed in different regions; and proxying the access request by the first proxy server to a server cluster in a preferred region based on its own configuration information.

Description

Network proxy method and proxy system

technical field

The present invention relates to Internet technology, in particular to a network proxy method and proxy system.

Background technique

The network proxy function is a common Internet function performed by a proxy server, that is, proxy network users to obtain network information. To put it figuratively, a proxy server is a transfer station for network information. Under normal circumstances, when we use a client, such as a web browser, to directly connect to other Internet sites to obtain network information, we must send an access request to get an answer, and then the other party sends the information back. The proxy server is a server between the browser and the web server. With it, the browser does not directly go to the web server to retrieve the web page but sends a request to the proxy server. The access request will be sent to the proxy server first, and the proxy server will retrieve the information required by the browser and transmit it to your browser. Moreover, most proxy servers have the function of buffering, like a large Cache, which has a large storage space, and it continuously stores the newly obtained data to its local memory. If the data requested by the browser is in the Its local memory already exists and is up-to-date, so it does not fetch data from the Web server again, but directly transmits the data in the memory to the user's browser, which can significantly improve browsing speed and efficiency.

SUMMARY OF THE INVENTION

A brief summary of one or more aspects is presented below to provide a basic understanding of the aspects. This summary is not an exhaustive overview of all contemplated aspects and is neither intended to identify key or critical elements of all aspects nor attempt to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

According to an aspect of the present invention, there is provided a proxy method for a network, comprising:

Performing domain name resolution on the access request, and resolving the access request to a first proxy server among multiple proxy servers, the multiple proxy servers being deployed in different regions; and

The first proxy server proxies the access request to a server cluster in the preferred region based on its own configuration information.

In an example, the performing domain name resolution includes: resolving the access request to the first proxy server based on the originating location of the access request, where the originating location of the access request falls within the first region where the first proxy server is located .

In one example, based on the configuration information, the server cluster in the preferred region is the server cluster in the first region.

In an example, the proxying the access request to a server cluster in the preferred region further includes: proxying the access request to a server in the server cluster in the preferred region based on a load balancing policy.

In an example, the proxying the access request to the server cluster in the preferred region further includes: if the proxyed server responds abnormally, proxying the access request to the server cluster in the preferred region based on the load balancing policy again other servers in the server until the access request gets a normal response.

In an example, the proxying the access request to the server cluster in the preferred region further includes: if all the servers in the server cluster in the preferred region respond abnormally, the first proxy server will send the proxy server based on its own configuration information. The access request is proxied to a server cluster in another region.

In one example, the proxy method further includes: after proxying the access request to a server cluster in another region and the access request is normally responded, modifying the configuration information to configure the other region as a preferred region.

In an example, the load balancing strategy includes at least one of the following: round-robin balancing, weighted round-robin balancing, random balancing, response speed balancing, least number of connections balancing, processing power balancing, and DNS response balancing.

In an example, the access request includes a header part and a body part, and the proxy method further includes: parsing, by the first proxy server, the body part of the access request to obtain a user ID, which is used for identification of the load balancing policy.

In one example, the first proxy server performs parsing of the body portion of the access request based on a locally stored request format for the access request.

According to another aspect of the present invention, there is provided a proxy system for a network, comprising:

Domain name resolution server, used to perform domain name resolution on access requests;

Multiple proxy servers, the multiple proxy servers are deployed in different regions;

Multiple server clusters, the multiple server clusters are deployed in different regions,

The domain name resolution server resolves the access request to a first proxy server among the plurality of proxy servers, and the first proxy server is configured to proxy the access request to a server cluster in a preferred region based on its own configuration information.

In an example, the domain name resolution server resolves the access request to the first proxy server based on the originating location of the access request, and the originating location of the access request falls within the first region where the first proxy server is located.

In one example, based on the configuration information, the server cluster in the preferred region is the server cluster in the first region.

In one example, the first proxy server is further configured to proxy the access request to a server in the server cluster in the preferred region based on a load balancing policy.

In an example, the first proxy server is further configured to proxy the access request to other servers in the server cluster in the preferred region based on the load balancing policy again if the proxy server responds abnormally until the access request get a normal response.

In an example, the first proxy server is further configured to proxy the access request to a server cluster in another region based on its own configuration information if all servers in the server cluster in the preferred region respond abnormally.

In an example, the first proxy server is further configured to modify its own configuration information to configure the other region as the first choice after the access request is proxied to a server cluster in another region and the access request is normally responded. area.

In an example, the load balancing strategy includes at least one of the following: round-robin balancing, weighted round-robin balancing, random balancing, response speed balancing, least number of connections balancing, processing power balancing, and DNS response balancing.

In an example, the access request includes a header part and a body part, and the first proxy server further includes: a parsing module for parsing the body part of the access request to obtain a user ID, which is used for the identification of the load balancing strategy .

In one example, the first proxy server includes a database in which request formats of various request types are stored, and the parsing module searches the database to perform parsing of the body portion of the access request according to the request format requested by the user .

In the present invention, by adding the concept of regions, it is possible to independently proxy the load to a certain region, or configure multiple regions, perform load proxying for multiple regions, and switch multiple regions, which provides flexibility of the proxy.

In addition, compared to nginx that can only obtain the content related to the load policy from the request header information, the present invention obtains the content of the load policy by parsing the request body information, thereby strengthening the load policy, solving the problem of a single execution mode of the general load policy, and thus supporting the proxy Load balancing diversity, for example, it can support various forms such as WeChat and webservice.

Description of drawings

The above-described features and advantages of the present invention can be better understood after reading the detailed description of the embodiments of the present disclosure in conjunction with the following drawings. In the drawings, components are not necessarily drawn to scale and components with similar related characteristics or features may have the same or similar reference numbers.

1 is a block diagram illustrating a proxy system according to an aspect of the present invention;

Figure 2 is a flowchart illustrating a proxy method according to an aspect of the present invention;

3 is a block diagram illustrating a proxy system according to another aspect of the present invention; and

FIG. 4 is a flowchart illustrating a proxy method according to another aspect of the present invention.

Detailed ways

The present invention will be described in detail below with reference to the accompanying drawings and specific embodiments. Note that the aspects described below in conjunction with the accompanying drawings and specific embodiments are only exemplary, and should not be construed as any limitation to the protection scope of the present invention.

1 is a block diagram illustrating a proxy system 100 according to an aspect of the present invention. As shown in FIG. 1 , the proxy system 100 may include a domain name resolution server 101 , proxy servers 121 and 122 , and server clusters 131 and 132 .

The user initiates an access request via the client. The client here can be a web browser, APP software such as WeChat and so on. The access request initiated by the client first performs domain name resolution through the domain name resolution server 101 . The domain name resolution server 101 is responsible for resolving the access request to one of the proxy servers 121 and 122 .

According to one aspect of the present invention, the proxy function is performed by means of a "territory". The proxy servers 121 and 122 are deployed in different regions, and the server clusters 131 and 132 are also deployed in different regions. In the example shown in FIG. 1 , the proxy server 121 and the server cluster 131 are deployed in the same region 1; the proxy server 122 and the server cluster 132 are deployed in the same region 2.

In the example shown in FIG. 1, only two regions are shown, region 1 and region 2, and only proxy servers and server clusters in these two regions are shown. However, those skilled in the art can understand that there may be two There are more than one region, and corresponding proxy servers and server clusters are deployed in each region, such as a proxy server 12n and a server cluster 13n (where n>2) deployed in region n (not shown).

In one embodiment, the domain name resolution server 101 may decide which proxy server to resolve the access request to based on the originating address of the access request. For example, the domain name resolution server 101 may resolve the access request to a first proxy server, where the originating address of the access request falls in the region where the first proxy server is located.

As an example, the first proxy server may be the proxy server 121, that is, the domain name resolution server 101 resolves the access request to the proxy server 121 in the domain 1.

The proxy server 121 receives the access request by monitoring port 80, for example. The proxy server 121 may determine, based on its own configuration information, to access the server cluster in the request proxy's preferred region. A preferred region may be stored in the configuration information, and the so-called preferred region refers to a server cluster where the proxy server 121 preferentially proxies the access request to the preferred region. A sorted list of other regions sorted by priority may also be stored in the configuration information.

As an example, under normal circumstances, the preferred region in the configuration information of a proxy server is the region where the proxy server itself is located. For example, for the proxy server 121, its preferred region is region 1, and for the proxy server 122, its preferred region is region 2. Of course, the preferred region in the configuration information can be changed. For example, when the server cluster in the preferred region is down and cannot respond normally, the preferred region can be changed, which is described in detail below.

In the example shown in FIG. 1 , the proxy server 121 can proxy the access request to the server cluster 131 in the domain 1 based on its own configuration information.

The server cluster 131 includes multiple servers, such as servers A, B, C, and D. Only four servers are shown here, but it is understood that there may be more servers.

The proxy server 121 can proxy the access request to a server in the server cluster in the preferred region, that is, a server in the server cluster 131 in the region 1 based on the load balancing policy.

Commonly used load balancing strategies include the following types:

Round Robin: Each time a request from the network is distributed to the internal servers in turn, from 1 to N and then restarts. This balancing algorithm is suitable for the situation that all servers in the server group have the same hardware and software configuration and the average service requests are relatively balanced.

Weighted Round Robin: According to the different processing capabilities of the servers, assign different weights to each server so that it can accept service requests with the corresponding weights. For example, the weight of server A is designed to be 1, the weight of B is 3, and the weight of C is 6, then servers A, B, and C will receive 10%, 30%, and 60% of service requests respectively. This balancing algorithm can ensure that high-performance servers get more utilization and avoid overloading low-performance servers.

Random Balance (Random): Randomly distribute requests from the network to multiple internal servers.

Weighted Random: This equalization algorithm is similar to the weighted round-robin algorithm, but it is a process of random selection when processing request sharing.

Response Time: The load balancing device sends a probe request (such as Ping) to each internal server, and then decides which server to respond to the client's service request according to the fastest response time of each internal server to the probe request . This balancing algorithm can better reflect the current running state of the server, but the fastest response time only refers to the fastest response time between the load balancing device and the server, not the fastest response time between the client and the server.

Least Connection (Least Connection): There may be a large difference in the time that the client's service stays on the server for each request. As the working time increases, if a simple round-robin or random balancing algorithm is used, each server The connection process may vary greatly and is not truly load balanced. The least number of connections balancing algorithm has a data record for each server that needs to be loaded internally, recording the number of connections currently being processed by the server. When there is a new service connection request, the current request will be allocated to the server with the least number of connections. The server makes the balance more in line with the actual situation and the load is more balanced. This balancing algorithm is suitable for long-term processing request services, such as FTP.

Processing capacity balancing: This balancing algorithm will allocate service requests to the server with the lightest processing load (converted according to the server CPU model, CPU number, memory size, and current number of connections, etc.), because the processing of the internal server is considered. capacity and current network operating conditions, so this balancing algorithm is relatively more accurate, and is especially suitable for use in Layer 7 (application layer) load balancing.

DNS response balance (Flash DNS): On the Internet, whether it is HTTP, FTP or other service requests, the client generally finds the exact IP address of the server through domain name resolution. Under this balancing algorithm, the load balancing devices located in different geographical locations receive the domain name resolution request from the same client, and resolve the domain name to the IP address of their corresponding server at the same time (that is, the same as the load balancing device). The IP address of the server in the same geographic location) and return it to the client, the client will continue to request the service by resolving the IP address of the domain name received first, and ignore other IP address responses. In the case that this kind of balancing strategy is suitable for global load balancing, it is meaningless for local load balancing.

For example, the proxy server 121 can proxy the access request to the server A in the server cluster 131 based on the load balancing policy. If the server A responds abnormally, it can proxy the access request to other servers in the server cluster 131 based on the load balancing policy again. If the response is still abnormal, the server will be proxied to the next server in the server cluster 131 again, and this operation will be repeated until the access request receives a normal response.

In extreme cases, if all the servers in the server cluster in the preferred region cannot respond normally, the proxy server 121 may proxy the access request to the server cluster in another region based on the configuration information. For example, the priority in the configuration information is only the second Server clusters in the next region of the preferred region. As an example, proxy server 121 may proxy access requests to server cluster 132 within domain 2, for example.

If the server cluster 132 can provide a normal response, the proxy server 121 may modify the configuration information to change the preferred region to region 2. Preferably, when the server cluster 131 in the domain 1 returns to normal, the preferred domain of the proxy server 121 can be changed back to the domain 1 again.

An access request generally includes a header part and a body part. As mentioned earlier, the access request may be sent through a network platform such as WeChat platform. In this case, the information in the header of the access request is the same and cannot be used as an indicator of some common load policies.

In the present invention, the proxy server may include a database and a parsing module (not shown in the figure). Request formats for various request types can be pre-stored in the database. The parsing module can parse the main part of the access request according to the request format of the user request by searching the database to obtain the user ID, which can be used as the identifier of the load balancing strategy.

FIG. 2 is a flow diagram illustrating a proxy method 200 according to an aspect of the present invention. As shown in FIG. 2, the proxy method 200 may include the following steps:

In step 201 , domain name resolution is performed on the access request, and the access request is resolved to a first proxy server among multiple proxy servers, and the multiple proxy servers are deployed in different regions.

The parsing may be performed based on the originating location of the access request, for example, the originating location of the access request falls within the first region where the first proxy server is located.

In step 202 , the first proxy server proxies the access request to the server cluster in the preferred region based on its own configuration information.

A preferred region may be stored in the configuration information. The so-called preferred region refers to a server cluster where the proxy server preferentially proxies the access request to the preferred region. A sorted list of other regions sorted by priority may also be stored in the configuration information. As an example, under normal circumstances, the preferred region in the configuration information of a proxy server is the region where the proxy server itself is located.

Further, the first proxy server may proxy the access request to a server in the server cluster in the preferred region based on the load balancing policy. As mentioned above, common load balancing strategies may include round-robin balancing, weighted round-robin balancing, random balancing, response speed balancing, least number of connections balancing, processing power balancing, DNS response balancing, and the like.

If the proxyed server responds abnormally, the access request is proxied to other servers in the server cluster in the preferred region based on the load balancing policy again until the access request receives a normal response.

If all the servers in the server cluster in the preferred region respond abnormally, the first proxy server will proxy the access request to the server cluster in another region based on its own configuration information. The server cluster in the next region of the region.

After the access request is proxied to a server cluster in another region and the access request is normally responded to, the configuration information is modified to configure the other region as the preferred region. Preferably, when the server cluster in the first region can respond normally, the first region can be changed back to the preferred region.

In one example, the body portion of the access request may be parsed by the first proxy server to obtain the user ID for identification of the load balancing policy. For example, the first proxy server may perform parsing of the body portion of the access request based on a locally stored request format for the access request.

FIG. 3 is a block diagram illustrating a proxy system 300 according to another aspect of the present invention.

As shown in FIG. 3 , the proxy system 300 may include a domain name resolution server 301 , proxy servers 321 and 322 , and server clusters 331 and 332 . The two proxy servers 321 and 322 and the two server clusters 331 and 332 shown in FIG. 3 are only examples. In practice, there may be one proxy server and one server cluster, or there may be more than two proxy servers and more than two a cluster of servers.

According to an aspect of the present invention, each server cluster may include two server groups, wherein one server group is a formal release server group providing access services, and the other is a pre-release server group used for server upgrade. These two sets of server groups are exactly the same, the only difference is that the roles of the two are different, that is, the role of each server group is switched between the "production server group" and the "pre-release server group". When one server group is the "release server group", the other group is the "prerelease server group", and when the server group that was originally the "release server group" is switched to the "prerelease server group", the original The server group with the role of "Pre-release server group" is also switched to "Production server group".

Taking the example in FIG. 3 as an example, the server cluster 331 includes two server groups 3311 and 3312 . The server group 3311 and the server group 3312 are originally two server groups that are mapped to each other, that is, they are exactly the same. However, the server group 3311 is used for providing access responses to users, and the other server group 3312 is not used for providing access responses to users, but for server upgrades. In this case, the server group 3311 can be called the official release server group, and the server group 3312 can be called the pre-release server group at this time.

In one example, during the time that the server group 3312 assumes the role of the pre-release server group, if any upgrade of the server is required, the server group 3311 that assumes the role of the official release server group will not do anything, but only the server group 3312 to perform an upgrade, where the server upgrade may be an update of the server content or a modification of the server configuration.

After the server group 3312 that assumes the role of the pre-release server group is upgraded, the server group 3312 can switch from the role of the pre-release server group to the official release server group, and correspondingly, the server group 3311 switches from the role of the official release server group to the pre-release server group. Publishing server group, the two realize role interchange.

In another example, if the server group 3312 needs to be upgraded during the time that the server group 3312 assumes the role of the pre-release server group, the server group 3312 can be switched to the official server group first, and the server group 3311 can be switched to the pre-release server group at the same time. server group; then, the server group 3311 is upgraded.

After the server group 3311 is upgraded, the server group 3312 is switched to the pre-release server group again, and the upgraded server group 3311 is switched to the official server group.

It should be noted that the above switching is passive switching between server groups. However, in the present invention, when all the formal server groups are abnormal, the pre-release server group can be switched to the formal server group, and the formal server group can be switched to the pre-release server group. In the future, it is also possible to regularly detect whether the abnormal pre-release server group has returned to normal. After the pre-release server group has returned to normal, the restored normal pre-release server is switched to the formal server group, and the formal server group is switched back to the pre-release server group.

The user initiates an access request via the client. The client here can be a web browser, APP software such as WeChat and so on. The access request initiated by the client first performs domain name resolution through the domain name resolution server 301 . The domain name resolution server 301 is responsible for resolving the access request to one of the proxy servers 321 and 322 , such as the proxy server 321 . The proxy server 321 can proxy the access request to a server cluster, such as the official publishing server group of the server cluster 331, based on its own configuration information.

As can be seen from the above, the proxy server always proxies the access request to the official publishing server group in the server cluster. Access requests are always responded to normally because the official publishing server group is always the one that has been upgraded and can provide normal access responses. In addition, although the official release server group switches between the two server groups of the server cluster, the switch is invisible to the user, so the upgrade of the server can be switched seamlessly without restarting the server.

In the presence of multiple proxy servers and multiple server clusters, the proxy function can be performed by means of "regions". For example, the proxy servers 321 and 322 are deployed in different regions, and the server clusters 331 and 332 are also deployed in different regions. In the example shown in FIG. 3 , the proxy server 321 and the server cluster 331 are deployed in the same region 1; the proxy server 322 and the server cluster 332 are deployed in the same region 2.

In one embodiment, the domain name resolution server 301 may decide which proxy server to resolve the access request to based on the originating address of the access request. For example, the domain name resolution server 301 may resolve the access request to a first proxy server, where the originating address of the access request falls in the region where the first proxy server is located.

The proxy server 321 receives the access request by monitoring port 80, for example. In one example, the proxy server 321 may determine, based on its own configuration information, to access a server cluster in the request proxy's preferred region. A preferred region may be stored in the configuration information, and the so-called preferred region refers to a server cluster where the proxy server 321 preferentially proxies the access request to the preferred region. A sorted list of other regions sorted by priority may also be stored in the configuration information.

As an example, under normal circumstances, the preferred region in the configuration information of a proxy server is the region where the proxy server itself is located. For example, for the proxy server 321, its preferred region is region 1, and for the proxy server 322, its preferred region is region 2.

In the example shown in FIG. 3 , the proxy server 321 can proxy the access request to the server cluster 331 in the domain 1 based on its own configuration information.

The proxy server 321 can proxy the access request to the server cluster in the preferred region, that is, the server cluster 331 in the region 1 in the official release server group, such as the servers in the server group 3311 , based on the load balancing policy.

Common load balancing strategies may include round-robin balancing, weighted round-robin balancing, random balancing, response speed balancing, least number of connections balancing, processing power balancing, DNS response balancing, and so on.

For example, the proxy server 321 can proxy the access request to the server A in the official publishing server group 3311 in the server cluster 331 based on the load balancing policy. If the server A responds abnormally, it can proxy the access request to the server group 3311 based on the load balancing policy again. If the response of other servers in the server is still abnormal, it will proxy to the next server in the server group 3311 again, and repeat this operation until the access request gets a normal response.

In extreme cases, if all servers in the official release server group 3311 of the server cluster 331 cannot respond normally, the proxy server 321 can proxy the access request to the next region based on the configuration information, for example, the priority in the configuration information is only the second The production server group in the server cluster in the next region of the preferred region. As an example, proxy server 321 may proxy access requests to a production server group within server cluster 332 within domain 2, for example. If the official publishing server group in the server cluster 332 is the server group 3321 at this time, the access request is proxied to the server group 3321 , otherwise, the access request is proxied to the server group 3322 .

In a more extreme case, if the official publishing server groups of the server clusters in all regions respond abnormally, the proxy server 321 may re-proxy the access request to the pre-publishing server groups of the server clusters in the preferred region, such as the one in region 1. Pre-published server group 3312 in server cluster 331.

If the pre-published server group 3312 in the server cluster 331 of the region 1 cannot respond normally, the access request can be proxied to the next region, for example, the server in the next region whose priority is next to the preferred region in the configuration information The pre-published server group in the cluster, for example, the pre-published server group 3322 in the server cluster 332 of the region 2, until the access request is responded normally.

In the case that the official publishing server group of all server clusters is down, you can check whether the official publishing server group is normal at intervals in the future. If it is officially restored, you can switch back to the official publishing server group.

As mentioned earlier, an access request typically includes a header portion and a body portion. The access request may be sent through the WeChat platform, webservice, etc. In this case, the information in the header part of the access request is the same and cannot be used as an indicator of some common load policies.

In the present invention, the proxy server may include a database and a parsing module (not shown in the figure). Request formats for various request types can be pre-stored in the database. The parsing module can parse the main part of the access request according to the request format of the user request by searching the database to obtain the user ID, which can be used as the identifier of the load balancing strategy.

FIG. 4 is a flow diagram illustrating a proxy method 400 according to an aspect of the present invention. As shown in FIG. 4, the proxy method 400 may include the following steps:

In step 401 , domain name resolution is performed on the access request, and the access request is resolved to the first proxy server.

In an example, the access request is parsed to the first proxy server among multiple proxy servers based on the originating location of the access request, the multiple proxy servers are deployed in different regions, and a corresponding server cluster is deployed in each region . The originating location of the access request falls within the first region where the first proxy server is located

At step 402: the first proxy server proxies the access request to a formal publishing server group in a first server cluster based on its own configuration information, where the first server cluster includes a formal publishing server group for providing access services and The pre-release server group for server upgrade, the pre-release server group is switched to the official release server group for providing access services after the upgrade is completed, and the official release server group is correspondingly switched to the pre-release server group for server upgrade.

In the instance where one server cluster is configured in each region, the first server cluster may be the server cluster in the preferred region in the configuration information of the first proxy server.

Further, the first proxy server may proxy the access request to the servers in the official release server group in the first server cluster based on the load balancing policy. Common load balancing strategies may include round-robin balancing, weighted round-robin balancing, random balancing, response speed balancing, least number of connections balancing, processing power balancing, DNS response balancing, and the like.

If all servers in the official release server group of the first server cluster respond abnormally, the first proxy server can proxy the access request to the official release server group in the server cluster in the next region based on its own configuration information until the access request is made get a normal response.

In an extreme case, if the official publishing server group of the server cluster in all regions responds abnormally, the first proxy server can proxy the access request to the pre-publishing server group in the first server cluster based on its own configuration information.

In a more extreme case, if all servers in the pre-release server group of the first server cluster respond abnormally, the first proxy server can proxy the access request to the server cluster in the next region based on its own configuration information. , repeat this operation until the access request is responded normally.

In the case that the official publishing server group of all server clusters is down, you can check whether the official publishing server group is normal at intervals in the future. If it is officially restored, you can switch back to the official publishing server group.

In one example, the body portion of the access request may be parsed by the first proxy server to obtain the user ID for identification of the load balancing policy. For example, the first proxy server may perform parsing of the body portion of the access request based on a locally stored request format for the access request.

Although the above-described methods are illustrated and described as a series of acts for simplicity of explanation, it should be understood and appreciated that these methods are not limited by the order of the acts, as some acts may occur in a different order in accordance with one or more embodiments and/or occur concurrently with other actions from or not shown and described herein but understood by those skilled in the art.

In the present invention, by adding the concept of regions, it is possible to independently proxy the load to a certain region, or configure multiple regions, perform load proxying for multiple regions, and switch multiple regions, which provides flexibility of the proxy. On the other hand, by providing real-time switching between the official release and pre-release environments, it solves the problem that all proxy servers need to be restarted to take effect after modifying the configuration. This technology does not need to restart the server, and any configuration modification will take effect in real time, realizing the dynamic proxy. Effect.

In addition, compared to nginx that can only obtain the content related to the load policy from the request header information, the present invention obtains the content of the load policy by parsing the request body information, thereby strengthening the load policy, solving the problem of a single execution mode of the general load policy, and thus supporting the proxy Load balancing diversity, for example, it can support various forms such as WeChat and webservice.

Those skilled in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

The various illustrative logic modules, and circuits described in connection with the embodiments disclosed herein may be implemented using general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable Logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein are implemented or performed. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integrated into the processor. The processor and storage medium may reside in the ASIC. The ASIC may reside in the user terminal. In the alternative, the processor and storage medium may reside in the user terminal as discrete components.

In one or more exemplary embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software as a computer program product, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage medium can be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, or other magnetic storage devices, or can be used to carry or store instructions or data structures in the form of Any other medium that conforms to program code and that can be accessed by a computer. Any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a web site, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave , then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc as used herein includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc, where disks are often reproduced magnetically data, and discs reproduce the data optically with a laser. Combinations of the above should also be included within the scope of computer-readable media.

The previous description of the present disclosure is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (18)

1. A proxy method for a network, comprising: Performing domain name resolution on the access request, and resolving the access request to a first proxy server among multiple proxy servers, the multiple proxy servers being deployed in different regions; and proxying the access request to a server cluster in the preferred region by the first proxy server based on its own configuration information; The proxying of the access request to the server cluster in the preferred region further includes: If all the servers in the server cluster in the preferred region respond abnormally, the first proxy server will proxy the access request to a server cluster in another region based on its own configuration information. 2. The proxy method according to claim 1, wherein the performing domain name resolution comprises: The access request is parsed to the first proxy server based on the originating location of the access request, where the originating location of the access request falls within the first region where the first proxy server is located. 3 . The proxy method according to claim 2 , wherein, based on the configuration information, the server cluster in the preferred region is the server cluster in the first region. 4 . 4. The proxy method according to claim 1, wherein the proxying the access request to a server cluster in a preferred region further comprises: The access request is proxied to a server in a server cluster in the preferred region based on a load balancing policy. 5. The proxy method according to claim 4, wherein the proxying the access request to a server cluster in a preferred region further comprises: If the proxyed server responds abnormally, the access request is proxied to other servers in the server cluster in the preferred region based on the load balancing policy again until the access request receives a normal response. 6. The proxy method of claim 1, further comprising: After the access request is proxied to a server cluster in another region and the access request is normally responded to, the configuration information is modified to configure the other region as a preferred region. 7. The proxy method according to claim 4, wherein the load balancing strategy comprises at least one of the following: round-robin balancing, weighted round-robin balancing, random balancing, response speed balancing, least number of connections balancing, processing capability Balanced, DNS response balance. 8. The proxy method according to claim 4, wherein the access request comprises a header part and a body part, and the proxy method further comprises: The body part of the access request is parsed by the first proxy server to obtain the user ID, which is used for the identification of the load balancing policy. 9. The proxy method of claim 8, wherein the first proxy server performs parsing on the body portion of the access request based on a locally stored request format for the access request. 10. A proxy system for a network, comprising: Domain name resolution server, used to perform domain name resolution on access requests; Multiple proxy servers, the multiple proxy servers are deployed in different regions; Multiple server clusters, the multiple server clusters are deployed in different regions, The domain name resolution server resolves the access request to a first proxy server among the multiple proxy servers, and the first proxy server is configured to proxy the access request to a proxy server in a preferred region based on its own configuration information server cluster; The first proxy server is further configured to proxy the access request to a server cluster in another region based on its own configuration information if all servers in the server cluster in the preferred region respond abnormally. 11. The proxy system according to claim 10, wherein the domain name resolution server resolves the access request to the first proxy server based on the originating location of the access request, and the originating location of the access request falls within the first region where the first proxy server is located. 12 . The proxy system according to claim 11 , wherein, based on the configuration information, the server cluster in the preferred region is the server cluster in the first region. 13 . 13. The proxy system of claim 10, wherein the first proxy server is further configured to The access request is proxied to a server in a server cluster in the preferred region based on a load balancing policy. 14. The proxy system according to claim 13, wherein the first proxy server is further configured to proxy the access request to the proxy server again based on a load balancing policy if the proxy server responds abnormally. other servers in the server cluster in the preferred region until the access request receives a normal response. 15. The proxy system according to claim 10, wherein the first proxy server is further configured to, after proxying the access request to a server cluster in another region and the access request is responded normally, Modify its own configuration information to configure the other region as the preferred region. 16. The proxy system according to claim 13, wherein the load balancing strategy comprises at least one of the following: round-robin balancing, weighted round-robin balancing, random balancing, response speed balancing, least number of connections balancing, processing capability Balanced, DNS response balance. 17. The proxy system of claim 13, wherein the access request comprises a header part and a body part, and the first proxy server further comprises: A parsing module, configured to parse the main body of the access request to obtain a user ID, which is used for the identification of the load balancing strategy. 18. The proxy system according to claim 17, wherein the first proxy server comprises a database in which request formats of various request types are stored, and the parsing module searches the database to search for the database according to the requested format. The request format of the access request is used to perform parsing on the body part of the access request.