Request proxy configuration method and device, product, equipment and medium

Abstract

The invention discloses a request agent configuration method and device, a product, equipment and a medium, and the method comprises the steps: obtaining mapping relation configuration information through a graphic interaction interface, and enabling the mapping relation configuration information to comprise a mapping relation between a second-level domain name of a private cloud and a second-level domain name of a public cloud configured by a user; in response to an access request of a target private cloud secondary domain name, determining a target public cloud secondary domain name corresponding to the target private cloud secondary domain name based on the mapping relationship, the target private cloud secondary domain name being a secondary domain name of a private cloud, and the target public cloud secondary domain name being a secondary domain name of a public cloud; and forwarding the access request to a service corresponding to the target public cloud secondary domain name. In this way, it is guaranteed that the user can seamlessly access the service of the public cloud through the private cloud, and the resource access efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of request processing technology, and in particular to a request proxy configuration method, device, product, equipment and medium. Background Art

[0002] The cloud is a pool of virtual computing resources and services on the Internet, which are provided to users through the network. With the development of cloud computing technology, more and more users are using the cloud to obtain and use resources on demand in order to avoid the high cost of building and maintaining infrastructure.

[0003] Currently, many scenarios rely on hybrid cloud, which includes public cloud and private cloud. Public cloud is usually provided by third-party cloud service providers and users access and use it through the Internet. Private cloud is built and maintained by enterprises or organizations themselves and is only used by internal users. In hybrid cloud scenarios, there are problems such as complex configuration and high access latency. Summary of the invention

[0004] In view of this, the purpose of this application is to provide a request proxy configuration method, device, product, equipment and medium to ensure that users can seamlessly access public cloud services through private clouds and improve resource access efficiency. The specific solution is as follows:

[0005] In a first aspect, the present application discloses a request proxy configuration method, comprising:

[0006] Obtaining mapping relationship configuration information through a graphical interactive interface, wherein the mapping relationship configuration information includes a mapping relationship between a second-level domain name of a private cloud and a second-level domain name of a public cloud configured by a user;

[0007] In response to an access request of a target private cloud second-level domain name, determining a target public cloud second-level domain name corresponding to the target private cloud second-level domain name based on the mapping relationship, wherein the target private cloud second-level domain name is the second-level domain name of the private cloud, and the target public cloud second-level domain name is the second-level domain name of the public cloud;

[0008] The access request is forwarded to the service corresponding to the target public cloud secondary domain name.

[0009] Optionally, the mapping relationship configuration information also includes a specific port corresponding to the secondary domain name of the public cloud;

[0010] Correspondingly, forwarding the access request to the service corresponding to the target public cloud secondary domain name includes:

[0011] When the target public cloud second-level domain name has a configured specific port, the access request is forwarded to the service corresponding to the target public cloud second-level domain name based on the specific port corresponding to the target public cloud second-level domain name;

[0012] When the target public cloud second-level domain name does not have a configured specific port, the access request is forwarded to the service corresponding to the target public cloud second-level domain name based on a universal port.

[0013] Optionally, also include:

[0014] When the target public cloud second-level domain name corresponding to the target private cloud second-level domain name does not exist in the mapping relationship, the target part in the target private cloud second-level domain name is combined with the public cloud first-level domain name to obtain the target public cloud second-level domain name;

[0015] The target portion is the portion of the target private cloud secondary domain name minus the private cloud primary domain name.

[0016] Optionally, forwarding the access request to a service corresponding to the target public cloud secondary domain name includes:

[0017] Determine a target access method corresponding to the target public cloud secondary domain name based on the access method configuration information;

[0018] The access request is forwarded to the service corresponding to the target public cloud secondary domain name according to the target access mode.

[0019] Optionally, determining a target access method corresponding to the target public cloud secondary domain name based on the access method configuration information includes:

[0020] Determining a target access method corresponding to the target public cloud secondary domain name from user access method configuration information, wherein the user access method configuration information includes an access method configured by the user obtained through a graphical interactive interface;

[0021] When the target access method corresponding to the target public cloud secondary domain name is not determined from the user access method configuration information, the target access method corresponding to the target public cloud secondary domain name is determined based on the default access method configuration information.

[0022] Optionally, before determining the target public cloud second-level domain name corresponding to the target private cloud second-level domain name based on the mapping relationship, the method further includes:

[0023] Matching the access request based on a preset matching rule to determine a target cloud for the access request, wherein the target cloud is a private cloud or a public cloud;

[0024] When the target cloud targeted by the access request is a public cloud, the step of determining the target public cloud second-level domain name corresponding to the target private cloud second-level domain name based on the mapping relationship is triggered.

[0025] Optionally, also include:

[0026] Obtain reverse proxy rule configuration information through the graphical interactive interface;

[0027] When the access request is a request for a private cloud, a target server is determined based on the reverse proxy rule configuration information, and the access request is forwarded to a service running in the target server.

[0028] In a second aspect, the present application discloses a request proxy configuration device, comprising:

[0029] A mapping relationship configuration information acquisition module, used to acquire mapping relationship configuration information through a graphical interactive interface, wherein the mapping relationship configuration information includes a mapping relationship between a second-level domain name of a private cloud and a second-level domain name of a public cloud configured by a user;

[0030] A public cloud second-level domain name determination module is used to respond to an access request of a target private cloud second-level domain name, and determine a target public cloud second-level domain name corresponding to the target private cloud second-level domain name based on the mapping relationship, wherein the target private cloud second-level domain name is the second-level domain name of the private cloud, and the target public cloud second-level domain name is the second-level domain name of the public cloud;

[0031] The access request forwarding module is used to forward the access request to the service corresponding to the target public cloud secondary domain name.

[0032] In a third aspect, the present application discloses a computer program product, which implements the aforementioned request proxy configuration method when executed.

[0033] In a fourth aspect, the present application discloses an electronic device, including a memory and a processor, wherein:

[0034] The memory is used to store the computer program;

[0035] The processor is used to execute the computer program to implement the aforementioned request proxy configuration method.

[0036] In a fifth aspect, the present application discloses a computer-readable storage medium for storing a computer program, wherein the computer program implements the aforementioned request proxy configuration method when executed by a processor.

[0037] It can be seen from the above scheme that the present application provides a request proxy configuration method, including: obtaining mapping relationship configuration information through a graphical interactive interface, wherein the mapping relationship configuration information includes a mapping relationship between a private cloud second-level domain name configured by a user and a public cloud second-level domain name; in response to an access request of a target private cloud second-level domain name, determining a target public cloud second-level domain name corresponding to the target private cloud second-level domain name based on the mapping relationship, wherein the target private cloud second-level domain name is the second-level domain name of the private cloud, and the target public cloud second-level domain name is the second-level domain name of the public cloud; and forwarding the access request to the service corresponding to the target public cloud second-level domain name.

[0038] It can be seen that the beneficial effects of the present application are: obtaining mapping relationship configuration information through a graphical interactive interface, forwarding access requests for the private cloud second-level domain name to the service corresponding to the target public cloud second-level domain name based on the mapping relationship, and users can access the public cloud through the private cloud by making simple configurations through the graphical interactive interface, thereby ensuring that users can seamlessly access the public cloud services through the private cloud and improving resource access efficiency.

[0039] Correspondingly, a request proxy configuration device, product, equipment and readable storage medium provided by the present application also have the above-mentioned technical effects. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0041] Figure 1 A flow chart of a request proxy configuration method provided in an embodiment of the present application;

[0042] Figure 2 A schematic diagram of a request proxy configuration provided in an embodiment of the present application;

[0043] Figure 3 A schematic diagram of the structure of a request proxy configuration device provided in an embodiment of the present application;

[0044] Figure 4 A structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0045] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0046] See also Figure 1 As shown, the embodiment of the present application discloses a request proxy configuration method, including:

[0047] Step S11: obtaining mapping relationship configuration information through a graphical interactive interface, wherein the mapping relationship configuration information includes a mapping relationship between a second-level domain name of a private cloud and a second-level domain name of a public cloud configured by a user.

[0048] The embodiment of the present application can display a graphical interactive interface on a user terminal, and the user can configure the mapping relationship between the second-level domain name of the private cloud and the second-level domain name of the public cloud through the graphical interactive interface. The embodiment of the present application obtains the mapping relationship configuration information through the graphical interactive interface.

[0049] A second-level domain name is a domain name under the first-level domain name in the Internet DNS (Domain Name System) hierarchy. A second-level domain name is a branch under a first-level domain name (primary domain name). For example, in the URL "http: / / www.example.com.cn", "example" is a second-level domain name under the first-level domain name "com.cn". Different second-level domain names can correspond to different services. For various types of business systems, services in the business system, such as services in the charging business system, can be provided through different second-level domain names. Some services can be provided by private clouds, and some services can be provided by public clouds, and they are designed according to actual business needs. Services provided by public clouds can be mapped based on mapping relationships, so that the corresponding access requests to the private cloud second-level domain name are mapped to the public cloud second-level domain name, and then the services in the public cloud are accessed, thereby obtaining the resources managed by the service.

[0050] Step S12: In response to an access request of the target private cloud second-level domain name, determine the target public cloud second-level domain name corresponding to the target private cloud second-level domain name based on the mapping relationship, wherein the target private cloud second-level domain name is the second-level domain name of the private cloud, and the target public cloud second-level domain name is the second-level domain name of the public cloud.

[0051] In this embodiment, the target private cloud second-level domain name targeted for access can be parsed from the access request, and the target public cloud second-level domain name corresponding to the target private cloud second-level domain name can be determined based on the mapping relationship.

[0052] Step S13: forwarding the access request to the service corresponding to the target public cloud secondary domain name.

[0053] It should be pointed out that in actual business, users often need to call the corresponding services of the public cloud when accessing a specific second-level domain name of the private cloud. The embodiment of the present application allows the user to specify the second-level domain name of the private cloud corresponding to the second-level domain name of the public cloud to achieve second-level domain name mapping. It not only improves the flexibility of service calls, but also makes it more convenient for users to switch between different services. For example, when a user needs to obtain specific resources from a private cloud, the embodiment of the present application can automatically identify and forward the request to the corresponding service of the public cloud. Through this mapping relationship, users can switch seamlessly without repeated configuration, which improves operational efficiency.

[0054] In an optional implementation, the mapping relationship configuration information also includes a specific port corresponding to the second-level domain name of the public cloud; accordingly, forwarding the access request to the service corresponding to the target public cloud second-level domain name includes: when the target public cloud second-level domain name has a configured specific port, forwarding the access request to the service corresponding to the target public cloud second-level domain name based on the specific port corresponding to the target public cloud second-level domain name; when the target public cloud second-level domain name does not have a configured specific port, forwarding the access request to the service corresponding to the target public cloud second-level domain name based on a universal port.

[0055] Among them, the universal port refers to a standard port that is widely used in various services and protocols. The universal port enables the client to communicate with a specific service on the server. For example, port 80 corresponding to the HTTP protocol, port 443 corresponding to the HTTPS protocol, etc. In addition to the universal port, the embodiment of the present application can support users to configure specific ports for communicating with specific services, thereby meeting user needs.

[0056] That is, the embodiment of the present application supports the second-level domain name site port of the public cloud. In order to improve the flexibility of the business, the embodiment of the present application allows users to customize the second-level domain name and its port for accessing the public cloud. It is not only convenient for enterprises to make rapid adjustments according to changes in business scenarios, but also enables users to flexibly choose the optimal access method in different network environments. In this way, enterprises can configure different business modules on different second-level domain names, thereby achieving more refined resource management. When accessing, users only need to simply select the corresponding second-level domain name, and the system will automatically perform routing processing. This design greatly simplifies the user's operating process and reduces the possibility of misconfiguration.

[0057] In addition, in an optional implementation, when the target public cloud second-level domain name corresponding to the target private cloud second-level domain name does not exist in the mapping relationship, the target part in the target private cloud second-level domain name is combined with the public cloud first-level domain name to obtain the target public cloud second-level domain name; wherein the target part is the part of the target private cloud second-level domain name without the private cloud first-level domain name.

[0058] For example, for the private cloud second-level domain name: appview.abc.com, remove the first-level domain name .abc.com and combine it with the public cloud first-level domain name .bcd.cn to get appview.bcd.cn. That is, the application example can obtain the accessed public cloud second-level domain name based on the combination of the public cloud second-level domain name and the private cloud second-level domain name, without the need to configure the mapping relationship, further simplifying user operations.

[0059] That is, this application supports the default access configuration of the public cloud second-level domain name. In order to simplify user operations, the system automatically uses the combination of the private cloud second-level domain name and the public cloud first-level domain name for access when the user does not explicitly configure the public cloud second-level domain name routing. This default configuration ensures that users can still successfully access the required resources in the absence of clear guidance, reducing the possibility of operational errors.

[0060] In an optional implementation, forwarding the access request to the service corresponding to the target public cloud second-level domain name may include: determining the target access method corresponding to the target public cloud second-level domain name based on the access method configuration information; and forwarding the access request to the service corresponding to the target public cloud second-level domain name according to the target access method. Furthermore, determining the target access method corresponding to the target public cloud second-level domain name based on the access method configuration information may specifically include: determining the target access method corresponding to the target public cloud second-level domain name from the user access method configuration information, wherein the user access method configuration information includes the user-configured access method obtained through the graphical interactive interface; when the target access method corresponding to the target public cloud second-level domain name is not determined from the user access method configuration information, determining the target access method corresponding to the target public cloud second-level domain name based on the default access method configuration information.

[0061] The access method can be understood as the protocol used to access the public cloud secondary domain name. Users can configure the access method corresponding to the public cloud secondary domain name. If no configuration is made, access is based on the default access method.

[0062] That is, the embodiment of the present application supports access mode configuration. In a hybrid cloud environment, security is a very important issue for users. In order to meet the user's demand for secure access, the present application supports the use of HTTP or HTTPS protocols when accessing the secondary domain name site of the public cloud. Users can flexibly choose a suitable access method according to their own business needs and security policies. This flexible configuration method ensures the adaptability of enterprises in different business scenarios. For example, for services involving sensitive data, users can choose HTTPS to ensure the security of data transmission; and when sensitive information is not involved, HTTP can be used to increase access speed. This flexibility is particularly important when large-scale users access concurrently, which can effectively reduce the burden on the system and improve overall performance. In addition, public cloud global access rules (i.e., default access methods) are provided. In a multi-cloud environment, how to uniformly manage different access rules is a complex challenge. The present application provides a set of global access rule mechanisms. If the HTTP or HTTPS access method of the public cloud is not explicitly configured, the system will access according to the preset global access rules. This mechanism not only ensures the continuity and reliability of access, but also provides users with a unified operation interface and reduces learning costs.

[0063] In an optional implementation, before determining the target public cloud second-level domain name corresponding to the target private cloud second-level domain name based on the mapping relationship, it also includes: matching the access request based on a preset matching rule to determine the target cloud targeted by the access request, wherein the target cloud is a private cloud or a public cloud; when the target cloud targeted by the access request is a public cloud, triggering the step of determining the target public cloud second-level domain name corresponding to the target private cloud second-level domain name based on the mapping relationship.

[0064] That is, the embodiment of the present application can determine whether the access request is for a private cloud or a public cloud. A matching rule can be preset to match the access request. The URL of the access request can be obtained, the URI can be extracted, and the URI can be matched with the preset matching rule. The preset matching rule can carry a target cloud identifier, for example, 0 represents a private cloud, and 1 represents a public cloud. The embodiment of the present application can configure corresponding matching rules for front-end resources and back-end resources respectively.

[0065] Among them, the front-end page URL proxy routing configuration (i.e., the matching rule configuration of the front-end resources): In order to cope with high concurrent requests, this application can use regular matching rules to perform intelligent proxy configuration on the URL of the front-end page. In this way, it is possible to automatically determine whether to reverse proxy the request to the private cloud or forward proxy to the public cloud based on the user's access request. When the request is received, the URL is analyzed and the resource loading path is quickly determined according to the preset rules. This intelligent matching mechanism effectively reduces the page loading time and significantly improves the user experience. For example, when a user accesses the charging service page, the system can quickly determine the source of the request and then select the optimal resource loading method. If the content requested by the user is mainly stored in the private cloud, the system will directly obtain the required resources from the private cloud; if the resources are located in the public cloud, they will be loaded through a forward proxy. This flexibility enables enterprises to dynamically adjust resource access paths according to the needs of different users, avoiding unnecessary delays.

[0066] Backend service gateway identifier custom routing configuration (matching rule configuration belonging to backend resources): Request processing for backend services is an integral part of the entire charging business. This application can effectively distinguish access requests for different services by accurately matching the backend service gateway identifier. Whenever a user initiates a service request, the system will analyze the identification information of the request and distribute the request to the corresponding private cloud or public cloud service based on the matching result. This mechanism not only improves the response speed of the system, but also effectively reduces the complexity of request processing. For example, when a user requests battery status information, the system can quickly identify which service should handle the request and determine whether to access the public cloud or the private cloud. This improvement makes the entire service chain clearer and improves user satisfaction.

[0067] In the embodiments of the present application, the front-end configuration is related to page presentation, and access to the public cloud or private cloud is determined by the front-end resource routing rules (Url regular expression matching) and the front-end low-code page routing rules; the back-end configurations are all related to business logic, such as data preservation, data calculation, and state flow, and access to the public cloud or private cloud can be determined by the back-end gateway routing rules and the back-end low-code routing rules.

[0068] The backend gateway routing rules are configured with the corresponding relationship between the service ID and the cloud ID. The cloud ID represents the public cloud or private cloud, for example, 0 represents a private cloud and 1 represents a public cloud. The corresponding cloud ID is determined based on the service ID carried in the request, thereby determining whether the request is to access the public cloud or the private cloud.

[0069] The front-end low-code routing rule refers to whether the low-code interface UI corresponding to the relevant business function accesses the local private cloud or the public cloud, which includes the correspondence between page information and cloud identifiers. The page information carried in the parsing request is uniquely corresponding to the corresponding page and can be a page ID or page number (can be a string, such as an English string). It is matched with the front-end low-code routing rule to determine the cloud identifier corresponding to the page information, thereby determining whether the request accesses the public cloud or the private cloud.

[0070] The backend low-code routing rule refers to whether the business logic or data query used by the relevant business accesses the local private cloud or the public cloud, which contains the correspondence between the functional logic information and the cloud identifier. The functional logic information uniquely corresponds to the functional logic of the response, which can be a functional logic ID or number. The functional logic information carried in the request is parsed and matched with the backend low-code routing rule to determine the cloud identifier corresponding to the functional logic information, thereby determining whether the request accesses the public cloud or the private cloud. Functional logic can include data query or other business logic.

[0071] Low Code is a visual application development method that allows developers to quickly build and deliver applications using less code, or even without writing a lot of code. In the embodiment of the present application, low code is a set of business rapid development platforms created based on business, which can quickly develop and deploy new functions through rapid data modeling, business logic orchestration, interface component drag and drop design, business process definition, and one-click release and launch. The corresponding business functions are developed based on this platform. Among them, low code conforms to the industry's classic MVC (Model-View-Controller) architecture. Among them, a) the interface PageUI (i.e., front-end low code) corresponds to the View layer, which is responsible for the front-end interface display; b) data modeling corresponds to the Model layer, and the front-end can directly deal with it when doing data storage and data query (both are part of the back-end low code); c) business logic (part of the back-end low code) corresponds to the Controller layer, which is used for service orchestration and logic calls.

[0072] In an optional implementation, the reverse proxy rule configuration information may also be obtained through a graphical interactive interface; when the access request is a request for a private cloud, the target server is determined based on the reverse proxy rule configuration information, and the access request is forwarded to the service running in the target server.

[0073] In the embodiment of the present application, for the same type of service, service instances can be run in multiple target servers to cope with concurrent scenarios, or servers suitable for the service can be configured according to business needs. Users can configure reverse proxy rules through a graphical interactive interface so that access requests are forwarded to the services running in the corresponding target servers. Reverse proxy rules can be used to dynamically expand or shrink the corresponding services to meet different business needs.

[0074] That is, the embodiment of the present application provides a flexible routing rule configuration for the private cloud. In a high-concurrency scenario, users may need to dynamically configure multiple reverse proxy rules for different business needs. In order to meet this demand, the embodiment of the present application allows users to freely configure multiple reverse proxy rules when accessing private cloud front-end resources or back-end gateway services. This feature enables enterprises to flexibly respond to changing market demands and improve the overall performance of the system.

[0075] Furthermore, the embodiments of the present application can obtain the newly added private cloud configuration information through the graphical interactive interface, that is, the embodiments of the present application support the newly added private cloud configuration. As the enterprise develops, the business often needs to be continuously expanded and upgraded. In order to support this demand of users, the present application provides a flexible new private cloud configuration function. Users can add new private cloud configurations at any time according to actual needs. After adding a new private cloud, the system will automatically update all relevant access rules and routing configurations to ensure the availability of new resources. This mechanism enables enterprises to quickly respond to market changes and maintain business continuity and stability when managing cloud resources.

[0076] It can be seen that the embodiment of the present application obtains mapping relationship configuration information through a graphical interactive interface, and forwards the access request for the private cloud second-level domain name to the service corresponding to the target public cloud second-level domain name based on the mapping relationship. The user can access the public cloud through the private cloud by performing simple configuration through the graphical interactive interface, thereby ensuring that the user can seamlessly access the public cloud services through the private cloud and improving resource access efficiency.

[0077] For further information, see Figure 2 As shown, Figure 2A request proxy configuration diagram provided for an embodiment of the present application. The private cloud Nginx proxy can be configured, including the aforementioned mapping relationship configuration information, user access mode configuration information, reverse proxy rule configuration information, etc., which can specifically include front-end resource routing rules (i.e., the aforementioned front-end page URL proxy routing configuration), back-end gateway routing rules (i.e., the aforementioned back-end service gateway identifier custom routing configuration), front-end low-code routing rules, back-end low-code routing rules, private cloud Web site routing rules (i.e., reverse proxy rules for private cloud Web sites), secondary domain name mapping rules (i.e., mapping relationships), http / https protocol rules (i.e., user access mode configuration information) and global routing rules (i.e., default access mode configuration information), reverse proxy to private cloud, or forward proxy to public cloud, access private cloud resources or public cloud resources. In public and private clouds, front-end resources may include but are not limited to html, js, css, pictures, low-code pages, etc., and back-end resources may include but are not limited to service gateways, WebApi, low-code actions, etc. The embodiment of the present application can set efficient routing rules for different types of resources.

[0078] In the process of building a private cloud, several business application Web sites will be involved. These business sites can be deployed on one server to reduce operation and maintenance costs, or on multiple servers to reduce access pressure and ensure high availability of the system. In order to ensure system security, these sites are not directly exposed to the public network for everyone to access, but through Nginx reverse proxy. The user actually accesses the second-level domain name bound to Nginx, which is then reverse-proxied to the relevant site by Nginx. The private cloud Web site routing rules describe this elastic deployment address, that is, which private web sites of the backend server are reverse-proxied to different second-level domain names, generally including two information: the host intranet IP and port number. The system supports load balancing for multiple sites.

[0079] The embodiments of the present application can be applied to various business scenarios, such as charging business scenarios. With the rapid development of electric vehicles and charging infrastructure, the demand for charging services is growing, especially in high-concurrency scenarios, which require effective management and configuration of charging services. Current charging services often rely on a hybrid cloud environment, in which private clouds provide secure storage and management functions, while public clouds provide flexible resources for business expansion. Customers hope to be able to seamlessly access public cloud services after logging in with a private cloud account. Through the request proxy configuration method provided by this application, the public cloud services can be seamlessly accessed based on the private cloud, simplifying user operations, improving resource access efficiency, and solving the problems of complex configuration, high access latency, and insufficient resource integration in the existing system. By establishing an efficient request proxy configuration mechanism, better technical support is provided for enterprises. Significantly improve the service quality of charging services in a hybrid cloud environment. Through a flexible and intelligent configuration mechanism, users can not only quickly access the required resources, but also enjoy an efficient and secure service experience. In addition, the scalability of this technology provides strong support for the future development of enterprises.

[0080] See also Figure 3 As shown, the embodiment of the present application discloses a request proxy configuration device, including:

[0081] A mapping relationship configuration information acquisition module 11 is used to acquire mapping relationship configuration information through a graphical interactive interface, wherein the mapping relationship configuration information includes a mapping relationship between a second-level domain name of a private cloud and a second-level domain name of a public cloud configured by a user;

[0082] The public cloud second-level domain name determination module 12 is used to respond to the access request of the target private cloud second-level domain name, and determine the target public cloud second-level domain name corresponding to the target private cloud second-level domain name based on the mapping relationship, wherein the target private cloud second-level domain name is the second-level domain name of the private cloud, and the target public cloud second-level domain name is the second-level domain name of the public cloud;

[0083] The access request forwarding module 13 is used to forward the access request to the service corresponding to the target public cloud secondary domain name.

[0084] In an optional implementation, the mapping relationship configuration information also includes a specific port corresponding to the second-level domain name of the public cloud; accordingly, the access request forwarding module 13 is specifically used to: when the target public cloud second-level domain name has a configured specific port, forward the access request to the service corresponding to the target public cloud second-level domain name based on the specific port corresponding to the target public cloud second-level domain name; when the target public cloud second-level domain name does not have a configured specific port, forward the access request to the service corresponding to the target public cloud second-level domain name based on a universal port.

[0085] In an optional implementation, the public cloud second-level domain name determination module 12 is specifically used to combine the target part in the target private cloud second-level domain name with the public cloud first-level domain name to obtain the target public cloud second-level domain name when the target public cloud second-level domain name corresponding to the target private cloud second-level domain name does not exist in the mapping relationship; wherein the target part is the part of the target private cloud second-level domain name without the private cloud first-level domain name.

[0086] In an optional implementation manner, the access request forwarding module 13 is specifically configured to:

[0087] A target access mode determination submodule, used to determine a target access mode corresponding to the target public cloud secondary domain name based on the access mode configuration information;

[0088] The access request forwarding module submodule is used to forward the access request to the service corresponding to the target public cloud secondary domain name according to the target access mode.

[0089] Among them, the target access method determination submodule is specifically used to determine the target access method corresponding to the target public cloud second-level domain name from the user access method configuration information, wherein the user access method configuration information includes the user configured access method obtained through the graphical interactive interface; when the target access method corresponding to the target public cloud second-level domain name is not determined from the user access method configuration information, the target access method corresponding to the target public cloud second-level domain name is determined based on the default access method configuration information.

[0090] The device also includes a target cloud determination module, which is used to match the access request based on a preset matching rule to determine the target cloud targeted by the access request, wherein the target cloud is a private cloud or a public cloud; when the target cloud targeted by the access request is a public cloud, the step of determining the target public cloud second-level domain name corresponding to the target private cloud second-level domain name based on the mapping relationship is triggered.

[0091] In an optional implementation, it also includes:

[0092] The reverse proxy rule acquisition module is used to obtain the reverse proxy rule configuration information through a graphical interactive interface; correspondingly, the access request forwarding module 13 is specifically used to determine the target server based on the reverse proxy rule configuration information when the access request is a request for a private cloud, and forward the access request to the service running on the target server.

[0093] It can be seen that the embodiment of the present application obtains mapping relationship configuration information through a graphical interactive interface, and forwards the access request for the private cloud second-level domain name to the service corresponding to the target public cloud second-level domain name based on the mapping relationship. The user can access the public cloud through the private cloud by performing simple configuration through the graphical interactive interface, thereby ensuring that the user can seamlessly access the public cloud services through the private cloud and improving resource access efficiency.

[0094] Furthermore, an embodiment of the present application discloses a computer program product, which implements the aforementioned request proxy configuration method when executed.

[0095] For the specific process of the above-mentioned request proxy configuration method, reference may be made to the corresponding content disclosed in the aforementioned embodiment, which will not be repeated here.

[0096] See also Figure 4 As shown, an embodiment of the present application discloses an electronic device 20, including a processor 21 and a memory 22; wherein the memory 22 is used to store a computer program; the processor 21 is used to execute the computer program, the request proxy configuration method disclosed in the above embodiment.

[0097] For the specific process of the above-mentioned request proxy configuration method, reference may be made to the corresponding content disclosed in the aforementioned embodiment, which will not be repeated here.

[0098] Furthermore, the memory 22 as a carrier for storing resources may be a read-only memory, a random access memory, a magnetic disk or an optical disk, etc., and the storage method may be temporary storage or permanent storage.

[0099] In addition, the electronic device 20 also includes a power supply 23, a communication interface 24, an input / output interface 25 and a communication bus 26; wherein the power supply 23 is used to provide working voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and an external device, and the communication protocol it follows is any communication protocol that can be applied to the technical solution of the present application, and is not specifically limited here; the input / output interface 25 is used to obtain external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0100] Furthermore, an embodiment of the present application also discloses a computer-readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the request proxy configuration method disclosed in the aforementioned embodiment.

[0101] For the specific process of the above-mentioned request proxy configuration method, reference may be made to the corresponding content disclosed in the aforementioned embodiment, which will not be repeated here.

[0102] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

[0103] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0104] The above is a detailed introduction to a request proxy configuration method, device, product, equipment and medium provided by the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for general technical personnel in this field, according to the idea of ​​the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A request proxy configuration method, characterized in that: include: Obtaining mapping relationship configuration information through a graphical interactive interface, wherein the mapping relationship configuration information includes a mapping relationship between a second-level domain name of a private cloud and a second-level domain name of a public cloud configured by a user; In response to an access request of a target private cloud second-level domain name, determining a target public cloud second-level domain name corresponding to the target private cloud second-level domain name based on the mapping relationship, wherein the target private cloud second-level domain name is the second-level domain name of the private cloud, and the target public cloud second-level domain name is the second-level domain name of the public cloud; The access request is forwarded to the service corresponding to the target public cloud secondary domain name.

2. The request proxy configuration method according to claim 1, characterized in that: The mapping relationship configuration information also includes a specific port corresponding to the secondary domain name of the public cloud; Correspondingly, forwarding the access request to the service corresponding to the target public cloud secondary domain name includes: When the target public cloud second-level domain name has a configured specific port, the access request is forwarded to the service corresponding to the target public cloud second-level domain name based on the specific port corresponding to the target public cloud second-level domain name; When the target public cloud second-level domain name does not have a configured specific port, the access request is forwarded to the service corresponding to the target public cloud second-level domain name based on a universal port.

3. The request proxy configuration method according to claim 1, characterized in that: Also includes: When the target public cloud second-level domain name corresponding to the target private cloud second-level domain name does not exist in the mapping relationship, the target part in the target private cloud second-level domain name is combined with the public cloud first-level domain name to obtain the target public cloud second-level domain name; The target portion is the portion of the target private cloud secondary domain name minus the private cloud primary domain name.

4. The request proxy configuration method according to claim 1, characterized in that: The step of forwarding the access request to a service corresponding to the target public cloud secondary domain name includes: Determine a target access method corresponding to the target public cloud secondary domain name based on the access method configuration information; The access request is forwarded to the service corresponding to the target public cloud secondary domain name according to the target access mode.

5. The request proxy configuration method according to claim 4, characterized in that: Determining a target access method corresponding to the target public cloud secondary domain name based on the access method configuration information includes: Determining a target access method corresponding to the target public cloud secondary domain name from user access method configuration information, wherein the user access method configuration information includes an access method configured by the user obtained through a graphical interactive interface; When the target access method corresponding to the target public cloud secondary domain name is not determined from the user access method configuration information, the target access method corresponding to the target public cloud secondary domain name is determined based on the default access method configuration information.

6. The request proxy configuration method according to any one of claims 1 to 5, characterized in that: Before determining the target public cloud secondary domain name corresponding to the target private cloud secondary domain name based on the mapping relationship, the method further includes: Matching the access request based on a preset matching rule to determine a target cloud for the access request, wherein the target cloud is a private cloud or a public cloud; When the target cloud targeted by the access request is a public cloud, the step of determining the target public cloud second-level domain name corresponding to the target private cloud second-level domain name based on the mapping relationship is triggered.

7. The request proxy configuration method according to claim 6, characterized in that: Also includes: Obtain reverse proxy rule configuration information through the graphical interactive interface; When the access request is a request for a private cloud, a target server is determined based on the reverse proxy rule configuration information, and the access request is forwarded to a service running in the target server.

8. A request proxy configuration device, characterized in that: include: A mapping relationship configuration information acquisition module, used to acquire mapping relationship configuration information through a graphical interactive interface, wherein the mapping relationship configuration information includes a mapping relationship between a second-level domain name of a private cloud and a second-level domain name of a public cloud configured by a user; A public cloud second-level domain name determination module is used to respond to an access request of a target private cloud second-level domain name, and determine a target public cloud second-level domain name corresponding to the target private cloud second-level domain name based on the mapping relationship, wherein the target private cloud second-level domain name is the second-level domain name of the private cloud, and the target public cloud second-level domain name is the second-level domain name of the public cloud; The access request forwarding module is used to forward the access request to the service corresponding to the target public cloud secondary domain name.

9. A computer program product, characterized in that When the computer program product is executed, the request proxy configuration method according to any one of claims 1 to 7 is implemented.

10. An electronic device, characterized in that: comprising a memory and a processor, wherein: The memory is used to store the computer program; The processor is used to execute the computer program to implement the request proxy configuration method according to any one of claims 1 to 7.

11. A computer-readable storage medium, characterized in that: Used to store a computer program, wherein when the computer program is executed by a processor, the request proxy configuration method according to any one of claims 1 to 7 is implemented.

Images