Method, device and computer program product for managing web console

Abstract

This application discloses a method, apparatus, device, and computer program product for managing a web console. The method, executed by a proxy server, includes: receiving and parsing a first access request from a user to obtain the address information of a first target service node; the first access request includes the address information of the proxy server and the address information of the first target service node; forwarding the first access request to the first target service node; receiving and parsing the response data from the node to obtain the access address information of the web console; and rewriting the access address information of the web console according to the address rewriting policy corresponding to the access address information of the web console and the address information of the proxy server. This application utilizes a proxy server to implement a centralized web console access point, simplifying the complexity of accessing service nodes across big data systems, improving cluster access security, and employing a non-intrusive design to ensure ease of system maintenance and seamless integration with existing workflows.

Description

Technical Field

[0001] This application relates to the field of big data service technology, and in particular to a method, apparatus, device, and computer program product for managing a web console. Background Technology

[0002] In a large Hadoop cluster, due to its sheer size, hundreds or even thousands of machines may be deployed. Each machine typically hosts multiple Hadoop service components, such as HDFS, YARN, or HBase, and each service component usually has its own independent web console interface for monitoring and managing its running status and performance metrics. This results in a large number of web consoles across the entire cluster, making management extremely complex.

[0003] In daily operations, administrators typically access the web UI of the master node (such as NameNode or ResourceManager) to obtain overall cluster status information and manage the cluster. The master node's web console displays an overview of the cluster, such as data storage status, task scheduling information, health status, and system performance. When administrators or users need to view detailed information about a specific machine or service node, the master node's web console provides convenient links that directly jump to that node's web interface. This jump process, by directly accessing the target node through links, eliminates the need for administrators to remember the IP address and web interface port of each node, greatly simplifying the management process. However, this management method also has some drawbacks:

[0004] 1) For everyday users, in the presence of network control, the user's terminal needs to enable network policies to each big data node.

[0005] 2) Directly exposing the web console access address of each node may pose a potential security risk, as it may become a target for attackers.

[0006] 3) Big data nodes are usually accessed via hostnames, and users' terminals need to configure the mapping relationship between hostnames and IPs in the hosts file.

[0007] 4) There are security issues; access requests cannot be logged, and security auditing is not possible.

[0008] 5) There is no unified exit point. Each big data node provides a portion of the web console functionality, and multiple ports need to be opened to enable external access to all of them. Summary of the Invention

[0009] To address at least one of the aforementioned technical problems, embodiments of this application provide a method, apparatus, device, and computer program product for managing a Web console, thereby improving the convenience and security of accessing the Web console.

[0010] The embodiments of this application adopt the following technical solutions:

[0011] In a first aspect, embodiments of this application provide a method for managing a Web console, wherein the Web console is provided by a service node, the method for managing the Web console is executed by a proxy server, and the method for managing the Web console includes:

[0012] The system receives and parses the first access request from the user to obtain the address information of the first target service node. The first access request is configured to include the address information of the proxy server and the address information of the first target service node.

[0013] Based on the address information of the first target service node, the first access request is forwarded to the first target service node;

[0014] Receive and parse the response data returned by the first target service node to obtain the access address information of the Web console;

[0015] The access address information of the Web console is rewritten according to the address rewriting policy corresponding to the access address information of the Web console and the address information of the proxy server to obtain the rewritten access address information of the Web console.

[0016] Optionally, rewriting the address information in the response data using the address rewriting strategy corresponding to the parsing result of the response data includes:

[0017] Identify whether the parsing result of the response data contains absolute address information;

[0018] When absolute address information is included, the absolute address information is rewritten based on the address information of the proxy server to obtain the first rewritten address information.

[0019] Optionally, rewriting the address information in the response data using the address rewriting strategy corresponding to the parsing result of the response data includes:

[0020] Identify whether the parsing result of the response data contains redirection address information;

[0021] If the redirection address information is included, the redirection address information is rewritten based on the address information of the proxy server to obtain the second rewritten address information.

[0022] Optionally, rewriting the address information in the response data using the address rewriting strategy corresponding to the parsing result of the response data includes:

[0023] Identify whether the parsing result of the response data contains hostname information;

[0024] When hostname information is included, the IP address information corresponding to the hostname information is determined according to the mapping relationship between hostname and IP address;

[0025] The IP address information corresponding to the hostname information is rewritten based on the address information of the proxy server to obtain the third rewritten address information.

[0026] Optionally, rewriting the address information in the response data using the address rewriting strategy corresponding to the parsing result of the response data includes:

[0027] Identify whether the parsing result of the response data contains dynamically spliced ​​address information;

[0028] In the case of dynamically concatenated address information, identify the original IP address information corresponding to the dynamically concatenated address information;

[0029] The original IP address information corresponding to the dynamically concatenated address information is rewritten based on the address information of the proxy server to obtain the fourth rewritten address information.

[0030] Optionally, after rewriting the access address information of the Web console according to the address rewriting policy corresponding to the access address information of the Web console and the address information of the proxy server to obtain the rewritten access address information of the Web console, the Web console management method further includes:

[0031] Receive a user's first redirect request, which is configured to include access address information of the rewritten Web console, wherein the access address information of the rewritten Web console includes the address information of the proxy server and the address information of the second target service node.

[0032] The user is redirected to the web console of the second target service node based on the first redirect request.

[0033] Optionally, the first target service node is divided into a main service node and sub-service nodes, and the management method of the Web console further includes:

[0034] Receive a second access request from the user, the access request being configured to include the address information of the proxy server;

[0035] The proxy server provides the user with the access address information of the main service node according to the second access request, so that the user can access the web console of the main service node through the proxy server.

[0036] Receive a second redirect request from the user terminal on the Web console of the main service node, the second redirect request being configured to include the address information of the proxy server and the address information of the sub-service node;

[0037] The second redirect request will redirect you to the web console of the sub-service node.

[0038] Secondly, embodiments of this application also provide a management and control device for a web console, wherein the web console is provided by a service node, the management and control device for the web console is applied to a proxy server, and the management and control device for the web console includes:

[0039] The first receiving unit is used to receive and parse the first access request from the user terminal to obtain the address information of the first target service node. The first access request is configured to include the address information of the proxy server and the address information of the first target service node.

[0040] The forwarding unit is used to forward the first access request to the first target service node according to the address information of the first target service node;

[0041] The second receiving unit is used to receive and parse the response data returned by the first target service node to obtain the access address information of the Web console.

[0042] The rewriting unit is used to rewrite the access address information of the Web console according to the address rewriting strategy corresponding to the access address information of the Web console and the address information of the proxy server, so as to obtain the rewritten access address information of the Web console.

[0043] Thirdly, embodiments of this application also provide an apparatus, comprising:

[0044] A processor; and a memory arranged to store computer-executable instructions, which, when executed, cause the processor to perform any of the aforementioned Web console control methods.

[0045] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program / instructions thereon, which, when executed by a processor, implements any of the aforementioned Web console control methods.

[0046] Fifthly, embodiments of this application also provide a computer program product, including a computer program / instruction, which, when executed by a processor, implements any of the aforementioned Web console control methods.

[0047] The at least one technical solution adopted in this application embodiment can achieve the following beneficial effects: The Web console management method in this application embodiment is executed by a proxy server. First, it receives and parses a first access request from the user to obtain the address information of the first target service node. The first access request is configured to include the address information of the proxy server and the address information of the first target service node. Then, based on the address information of the first target service node, the first access request is forwarded to the first target service node. Next, it receives and parses the response data returned by the first target service node to obtain the access address information of the Web console. Finally, based on the address rewriting strategy corresponding to the access address information of the Web console and the address information of the proxy server, the access address information of the Web console is rewritten to obtain the rewritten access address information of the Web console. The Web console management method in this application embodiment uses the proxy server as a unified relay node between the user and the Web console provided by the service node, realizing a centralized Web console access entry point, simplifying the complexity of accessing service nodes across big data systems, and using the proxy server as an effective isolation layer between the Web console and the user, thus improving the security of cluster access. Furthermore, the non-intrusive design requires no modifications to the service nodes themselves, maintaining their original operational status, ensuring ease of system maintenance and seamless integration with existing workflows, and providing system administrators with a low-risk, easy-to-operate solution. Attached Figure Description

[0048] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0049] Figure 1 This is a flowchart illustrating a web console control method according to an embodiment of this application;

[0050] Figure 2 This is a flowchart illustrating a web console control method according to an embodiment of this application;

[0051] Figure 3 This is a schematic diagram of the structure of a control device for a web console according to an embodiment of this application;

[0052] Figure 4 This is a schematic diagram of the structure of a device according to an embodiment of this application. Detailed Implementation

[0053] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0054] The technical solutions provided by the various embodiments of this application are described in detail below with reference to the accompanying drawings.

[0055] Key technical terms used in this application:

[0056] 1) Big Data Service Nodes: Big data service nodes typically refer to servers or computers that perform specific functions within a big data processing architecture. Hadoop, Spark, Flink, and HBase are common frameworks or systems used in big data processing; they run on big data service nodes and each performs different functions.

[0057] 2) Web Console: The web console for big data service nodes is a web interface provided by the big data service framework (such as Hadoop, Spark, etc.) for monitoring, managing, and configuring the cluster. Through the web console, users can intuitively view cluster status, resource usage, task execution status, and perform node management and configuration adjustments. For Hadoop clusters, the web console typically includes the NameNode web interface and the ResourceManager web interface. The NameNode web interface provides detailed information about HDFS (Distributed File System), such as file browsing, block information, and data node status. The ResourceManager web interface provides information about YARN (Resource Manager), including application queues, application status, and resource usage. To access these web consoles, users usually need to enter a specific URL in their browser, which is typically the IP address of a node in the cluster plus a default port number. For example, for a Hadoop cluster, the default port number for the NameNode web interface is usually 50070.

[0058] 3) Reverse Proxy Server: A reverse proxy server sits between the client and the target server. From the client's perspective, the reverse proxy server is equivalent to the target server. The client can directly access the target server's resources by accessing the reverse proxy server without needing to know the target server's real address. The working principle of a reverse proxy is as follows: the proxy server receives network access connection requests from the client, then forwards the requests to the actual business servers (i.e., backend servers) in the network according to predefined rules and load balancing strategies, and returns the results processed by the business servers to the client that initiated the connection request.

[0059] This application provides a method for managing a web console, such as... Figure 1 The diagram illustrates a flowchart of a web console management method according to an embodiment of this application. The web console is provided by a service node, and the web console management method is executed by a proxy server. The web console management method includes at least the following steps S110 to S140:

[0060] Step S110: Receive and parse the first access request from the user terminal to obtain the address information of the first target service node. The first access request is configured to include the address information of the proxy server and the address information of the first target service node.

[0061] Combination Figure 2 This document provides a flowchart illustrating a web console management method according to an embodiment of this application. The web console management method in this embodiment is executed by a proxy server, specifically a reverse proxy server. The reverse proxy server is deployed between the user client and the service nodes of the big data cluster, serving as a unified relay station between the user client and the web console provided by the service nodes.

[0062] When a user needs to access the web console of a service node in a big data cluster, they must first send a standardized access request to the proxy server. This standardized access request is configured to include the proxy server's address information and the address information of the target service node that the user wants to access. The proxy server's address information may include its IP address and port number, while the target service node's address information may include the target server's IP address and port number. Therefore, the standardized access request can be represented, for example, as follows:

[0063] "http: / / proxy server IP:proxy server port / [target server IP]:[target server port](the actual node to be accessed) / [specific request path]".

[0064] In this way, after a user initiates an access request in the above-mentioned unified format, the proxy server will first receive the user's access request, then parse the access request to extract the address information of the target service node contained therein.

[0065] Step S120: Based on the address information of the first target service node, forward the first access request to the first target service node.

[0066] After obtaining the address information of the target service node, the user's access request needs to be accurately forwarded to the target service node based on the IP address and port number of the target service node, so that the target service node can respond to and process the user's access request.

[0067] Step S130: Receive and parse the response data returned by the first target service node to obtain the access address information of the Web console.

[0068] After the target service node completes its processing, it sends the processed response data back to the proxy server. This response data may include the target service node's web console page and links to other service nodes' web console pages. The proxy server then needs to further parse this response data to extract access address information for other service nodes' web consoles.

[0069] Step S140: Rewrite the access address information of the Web console according to the address rewriting policy corresponding to the access address information of the Web console and the address information of the proxy server to obtain the rewritten access address information of the Web console.

[0070] To achieve a non-intrusive design, this application embodiment does not require any modification to the service nodes in the big data cluster. The target service node can still return response data such as the access address of the Web console page containing other service nodes according to the original user access process. It is only necessary for the proxy server to rewrite the access address of the Web console page of other nodes returned by the target service node in combination with the proxy server's own address information. The purpose of rewriting is to ensure that all accesses to the Web console pages of the big data cluster nodes by the user client will be forwarded through the proxy server, so as to realize unified relay, control and recording functions.

[0071] The specific rewriting address strategy depends on the type of access address parsed from the Web console. Different address rewriting strategies need to be adopted for different types of access addresses, and the rewriting should be uniformly rewritten into the access request format given in step S110 above, so as to cover various types of interactions between the user terminal and the big data cluster nodes.

[0072] The Web console management method in this application uses a proxy server as a unified relay node between the user client and the Web console provided by the service node, realizing a centralized Web console access point. This simplifies the complexity of accessing service nodes across big data systems and uses the proxy server as an effective isolation layer between the Web console and the user, improving cluster access security. Furthermore, the non-intrusive design requires no modification to the service nodes themselves, maintaining their original operational state and ensuring ease of system maintenance and seamless integration with existing workflows. This provides system administrators with a low-risk, easy-to-operate solution.

[0073] In some embodiments of this application, rewriting the address information in the response data using the address rewriting strategy corresponding to the parsing result of the response data includes: identifying whether the parsing result of the response data contains absolute address information; if it contains absolute address information, rewriting the absolute address information according to the address information of the proxy server to obtain first rewritten address information.

[0074] Continue to refer to Figure 2 The address rewriting strategy in this application embodiment may include an absolute address rewriting strategy. An absolute address refers to a URL that includes the complete protocol (such as HTTP or HTTPS), domain name or IP address, port number (if any), and resource path. Compared with relative addresses, absolute addresses do not depend on the current page location and can be directly accessed by browsers or other user terminals.

[0075] Based on the parsing results of the response data, it is determined whether the parsed address information contains an absolute path URL. If it contains a standard format absolute path URL, the absolute path URL can be directly extracted by parsing the HTML DOM structure. Then, the absolute path URL is rewritten according to the address information of the proxy server. When the user clicks on the absolute path URL on the response page returned by the proxy server, the address of the absolute path URL will be changed to the new address via the proxy server, thereby realizing that the communication between the user terminal and the big data service node is managed by the proxy server.

[0076] For example, if the parsed result contains an absolute path URL such as "http: / / xx.xx.xx.xx:port / path", it needs to be rewritten as "http: / / proxy server IP:proxy server port / xx.xx.xx.xx:port / path" based on the proxy server's address information.

[0077] In some embodiments of this application, rewriting the address information in the response data using the address rewriting strategy corresponding to the parsing result of the response data includes: identifying whether the parsing result of the response data contains redirection address information; if it contains redirection address information, rewriting the redirection address information according to the address information of the proxy server to obtain second rewritten address information.

[0078] Continue to refer to Figure 2 The address rewriting strategy in this application embodiment may also include a rewriting strategy for redirect address information. A redirect address refers to a command in the response message sent by the server to the user during HTTP communication that instructs the user to perform a redirect (i.e., relocate to another URL). This is used to tell the user that the requested resource has been temporarily or permanently moved to a new location, and the user will use the new URL to access the resource.

[0079] During the parsing of response data, the proxy server pays attention to responses that contain redirection commands. In the HTTP protocol, redirection is typically indicated by status codes (such as 301, 302, 307, etc.) and a Location header field. The proxy server checks whether such a Location header field exists in the response data, and whether that field contains redirection address information.

[0080] If the target server's response contains redirection commands, such as an HTTP redirection response with a "Location:" header, the proxy server will also replace these addresses accordingly. For example, "Location:http: / / xx.xx.xx.xx:port / path" will be rewritten as "Location:http: / / proxy server IP:proxy server port / xx.xx.xx.xx:port / path". This new address will retain the resource path of the original redirection address. By rewriting the redirection address information, the proxy server can ensure that even if the target server returns a redirection command, the user can still access the final target resource through the proxy server.

[0081] In some embodiments of this application, rewriting the address information in the response data using the address rewriting strategy corresponding to the parsing result of the response data includes: identifying whether the parsing result of the response data contains hostname information; if it contains hostname information, determining the IP address information corresponding to the hostname information according to the mapping relationship between hostname and IP address; and rewriting the IP address information corresponding to the hostname information according to the address information of the proxy server to obtain the third rewritten address information.

[0082] Continue to refer to Figure 2 The address rewriting strategy in this application embodiment may also include an address rewriting strategy containing hostname information. A hostname refers to the name used to identify a device or service in a network, such as "http: / / www.example.com". In this application embodiment, it mainly refers to the names of various service nodes in a big data cluster. In a URL, the hostname is usually located between the protocol (such as http or https) and the resource path, separated by a colon and the port number (if any).

[0083] If the response data returned by the target server contains URLs represented by hostnames, such as "http: / / hostname:port / path", the proxy server also needs to perform replacement processing to ensure that all links containing hostnames can still be forwarded through the proxy server. For example, "http: / / hostname:port / path" can be rewritten as "http: / / proxy server IP:proxy server port / xx.xx.xx.xx:port / path".

[0084] It's important to note that in the rewritten address above, "xx.xx.xx.xx" refers to the IP address corresponding to the hostname of a service node. The proxy server needs to maintain the mapping relationship between the master node and IP address of all service nodes. Based on this mapping relationship, it replaces the hostname information in the response data returned by the target server with the corresponding IP address of the service node. Furthermore, to facilitate subsequent expansion by adding hosts, the proxy server can also provide an interface for dynamically adding hostname and IP address mapping relationships, ensuring that adding or expanding hosts does not affect the proxy server's request redirection.

[0085] In some embodiments of this application, rewriting the address information in the response data using the address rewriting strategy corresponding to the parsing result of the response data includes: identifying whether the parsing result of the response data contains dynamically concatenated address information; if it contains dynamically concatenated address information, identifying the original IP address information corresponding to the dynamically concatenated address information; and rewriting the original IP address information corresponding to the dynamically concatenated address information according to the address information of the proxy server to obtain the fourth rewritten address information.

[0086] Continue to refer to Figure 2 The address rewriting strategy in this application embodiment may also include a dynamic address concatenation strategy. In JavaScript, address concatenation typically refers to combining multiple string values ​​together to form a complete URL or path. This operation is very common in web development, especially when it is necessary to dynamically generate links based on user input, variable values, or program logic.

[0087] Based on the parsing results of the response data, it is necessary to identify such special links. For example, packet capture analysis can be used to determine which page and which JS file contains such special links. Custom rules can then be written for this JS file to replace them, thereby enabling the identification and replacement of different types of dynamically concatenated addresses.

[0088] For example, if the response data returned by the target server contains a page request initiated by an address dynamically constructed by JavaScript, such as "var a = "datanode"; var b = "8080"; var c = "http: / / " + a + b", it is necessary to identify the original IP address information in this address. This can be done by parsing the variables and logic in the JavaScript code to determine which parts constitute the target server's real IP address or are related to the real IP address (such as hostname information). Then, based on the proxy server's address information, the corresponding JavaScript code can be replaced, rewriting the constructed address into the form "http: / / proxy server IP:proxy server port / xx.xx.xx.xx:port / path".

[0089] In some embodiments of this application, after rewriting the access address information of the Web console according to the address rewriting policy corresponding to the access address information of the Web console and the address information of the proxy server to obtain the rewritten access address information of the Web console, the Web console management method further includes: receiving a first redirect request from a user, the first redirect request being configured to include a request containing the rewritten access address information of the Web console, the rewritten access address information of the Web console including the address information of the proxy server and the address information of the second target service node; and redirecting to the Web console of the second target service node according to the first redirect request.

[0090] As mentioned earlier, the rewritten address information includes the address information of the proxy server and the address information of the target service node. In this way, when a user accesses the Web console, the request will first be directed to the proxy server, and then forwarded by the proxy server to the target service node.

[0091] After the address rewriting strategy based on the foregoing embodiments completes the address rewriting, when a user clicks any redirect link on the page returned by the proxy server, i.e., requests a redirect to the web console of another target service node, the address of these links will be changed to the new address via the proxy server, such as "http: / / proxy server IP:proxy server port / [target server IP]:[target server port] / [specific request path]". This ensures that all outbound requests and data flows are processed through a centralized proxy server, enhancing security and simplifying the user's operation process.

[0092] In some embodiments of this application, the first target service node is divided into a main service node and a sub-service node. The management method of the Web console further includes: receiving a second access request from a user terminal, the access request being configured to include the address information of a proxy server; providing the user terminal with the access address information of the main service node according to the second access request, so that the user terminal can access the Web console of the main service node through the proxy server; receiving a second redirect request from the user terminal on the Web console of the main service node, the second redirect request being configured to include the address information of the proxy server and the address information of the sub-service node; and redirecting to the Web console of the sub-service node according to the second redirect request.

[0093] As mentioned earlier, in a big data cluster architecture, big data service nodes can be divided into primary service nodes and secondary service nodes. The web console of the primary service node is mainly used to display an overview of the cluster, such as data storage status, task scheduling information, health status, and system performance. When administrators or users need to view detailed information about a specific machine or service node, the web console of the primary service node provides convenient links that can directly jump to the web interface of that node. This jump process directly accesses the target node through links, eliminating the need for administrators or users to remember the IP address and web interface port of each node, thus simplifying the management process.

[0094] Based on this, this application provides another redirection method using a proxy server, building upon the functionality implemented by the main service node. Specifically, when a user initiates an access request, they can simply request access to the proxy server; that is, the request only needs to include the proxy server's address information. After receiving the user's access request, the proxy server can provide the user with a redirection link page containing the main service node. After clicking the redirection link page of the main service node, the user can access the main service node's web console page through the proxy server. The main service node's web console page provides links to other sub-service nodes, and the user can click to redirect to the web console page of any sub-service node according to their needs.

[0095] The above-mentioned redirection process is uniformly forwarded and managed by the proxy server, which eliminates the need for the user to remember the IP address and port information of each service node, thus simplifying the management process.

[0096] In summary, the key points of the Web console control method in this application mainly include:

[0097] 1) Reverse Proxy: This application introduces reverse proxy technology into the management and control of the web console of the big data cluster, and optimizes the access and management of the web console of each service node in the big data environment through highly automated and configurable proxy strategies.

[0098] 2) Rewriting Strategy: This application implements a URL rewriting strategy to ensure that all requests originating from a single entry point are properly mapped and forwarded to the correct service node. Essentially, this encompasses intelligent routing capabilities; when a user enters a uniform URL address, the proxy server parses the request and routes it to the correct node in the cluster.

[0099] 3) Security: This application creates a centralized web console access point and makes the reverse proxy server an effective isolation layer between the web console and the user. This design enables the reverse proxy service to effectively act as a security barrier, integrating multiple advanced security policies. For example, strict access control is ensured through the use of Access Control Lists (ACLs) and Role-Based Access Control (RBAC); simultaneously, data is encrypted during transmission using SSL / TLS protocols, and IP whitelist policies can be deployed to further restrict access to service nodes, ensuring that only requests from trusted sources are processed. These advanced security features provide robust protection for big data systems against external threats, ensuring data security while enhancing system stability and greatly reducing the possibility of data leakage and unauthorized access.

[0100] 4) Non-intrusiveness: While enhancing system security, this application also focuses on maintaining the original architecture and performance stability of the big data system. The non-intrusive design means it can be fully integrated into the existing big data environment without requiring any modifications to the service nodes themselves, maintaining their original operational state. This enhanced transparency ensures ease of system maintenance and seamless integration with existing workflows, providing system administrators with a low-risk, easy-to-operate solution.

[0101] The web console control method of this application has achieved at least the following technical effects:

[0102] 1) Simplified access: Through a unified reverse proxy, users only need to access a single address to access the web consoles of all nodes in the Hadoop cluster. This greatly simplifies the user access process and improves the user experience.

[0103] 2) Enhanced security: The reverse proxy server acts as a security barrier for the web console. It can be configured with various security policies, such as access control and encrypted transmission, to ensure that only authorized users can access the web console, thereby enhancing system security.

[0104] 3) Easy to manage and maintain: The unified reverse proxy allows administrators to centrally manage the web consoles of all nodes without having to configure and maintain each node separately. This reduces management costs and improves management efficiency.

[0105] 5) Hiding the backend architecture: By using a reverse proxy, the specific architecture and configuration details of the Hadoop cluster backend can be hidden, exposing only a unified interface to the outside world. This helps protect the cluster's security and prevent potential security risks.

[0106] This application embodiment also provides a web console control device 300, such as... Figure 3 The diagram shows a structural schematic of a web console management device according to an embodiment of this application. The web console is provided by a service node, and the web console management device 300 is applied to a proxy server. The web console management device 300 includes: a first receiving unit 310, a forwarding unit 320, a second receiving unit 330, and a rewriting unit 340, wherein:

[0107] The first receiving unit 310 is used to receive and parse the first access request from the user terminal to obtain the address information of the first target service node. The first access request is configured to include the address information of the proxy server and the address information of the first target service node.

[0108] The forwarding unit 320 is used to forward the first access request to the first target service node according to the address information of the first target service node;

[0109] The second receiving unit 330 is used to receive and parse the response data returned by the first target service node to obtain the access address information of the Web console.

[0110] The rewriting unit 340 is used to rewrite the access address information of the Web console according to the address rewriting strategy corresponding to the access address information of the Web console and the address information of the proxy server, so as to obtain the rewritten access address information of the Web console.

[0111] In some embodiments of this application, the rewriting unit 340 is specifically used to: identify whether the parsing result of the response data contains absolute address information; if it contains absolute address information, rewrite the absolute address information according to the address information of the proxy server to obtain first rewritten address information.

[0112] In some embodiments of this application, the rewriting unit 340 is specifically used to: identify whether the parsing result of the response data contains redirection address information; if it contains redirection address information, rewrite the redirection address information according to the address information of the proxy server to obtain second rewritten address information.

[0113] In some embodiments of this application, the rewriting unit 340 is specifically used to: identify whether the parsing result of the response data contains hostname information; if hostname information is included, determine the IP address information corresponding to the hostname information according to the mapping relationship between hostname and IP address; and rewrite the IP address information corresponding to the hostname information according to the address information of the proxy server to obtain third rewritten address information.

[0114] In some embodiments of this application, the rewriting unit 340 is specifically used to: identify whether the parsing result of the response data contains dynamically concatenated address information; if it contains dynamically concatenated address information, identify the original IP address information corresponding to the dynamically concatenated address information; and rewrite the original IP address information corresponding to the dynamically concatenated address information according to the address information of the proxy server to obtain fourth rewritten address information.

[0115] In some embodiments of this application, the Web console management device 300 further includes: a third receiving unit, configured to receive a first redirect request from a user after rewriting the access address information of the Web console according to the address rewriting policy corresponding to the access address information of the Web console and the address information of the proxy server to obtain the rewritten access address information of the Web console, wherein the first redirect request is configured to include the rewritten access address information of the Web console, the rewritten access address information of the Web console including the address information of the proxy server and the address information of the second target service node; and a first redirect unit, configured to redirect to the Web console of the second target service node according to the first redirect request.

[0116] In some embodiments of this application, the first target service node is divided into a main service node and a sub-service node. The control device 300 of the Web console further includes: a fourth receiving unit, configured to receive a second access request from a user terminal, the access request being configured to include the address information of a proxy server; a providing unit, configured to provide the user terminal with the access address information of the main service node according to the second access request, so that the user terminal can access the Web console of the main service node through the proxy server; a fifth receiving unit, configured to receive a second redirect request from the user terminal on the Web console of the main service node, the second redirect request being configured to include the address information of the proxy server and the address information of the sub-service node; and a second redirect unit, configured to redirect to the Web console of the sub-service node according to the second redirect request.

[0117] It is understood that the aforementioned Web console management device can implement each step of the Web console management method provided in the foregoing embodiments. The relevant explanations of the Web console management method are applicable to the Web console management device, and will not be repeated here.

[0118] Figure 4 This is a schematic diagram of the structure of a device according to an embodiment of this application. For example... Figure 4 As shown, the device includes one or more processors (or processing units), and may also include one or more memories coupled to the processors, and may also include a communication module coupled to the processors.

[0119] A communication module can be used to communicate with other devices or apparatuses, such as sending or receiving data and / or signals. A communication module may have at least one communication module for communication. A communication module may include any interface necessary for communicating with other devices. Exemplarily, a communication module may be a transceiver, circuit, bus, module, or other type of communication module.

[0120] The processor may include, but is not limited to, one or more of the following: a general-purpose computer, a special-purpose computer, a microcontroller, a digital signal processor (DSP), or a controller-based multi-core controller architecture. The device may have multiple processors, such as application-specific integrated circuit (ASIC) chips, which are time-dependent on a clock synchronized with the main processor.

[0121] The memory may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, at least one of the following: read-only memory (ROM), electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disc (CD), digital video disk (DVD), or other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, at least one of the following: random access memory (RAM), or other volatile memories that do not persist during the duration of a power outage.

[0122] A computer program consists of computer-executable instructions that are executed by an associated processor. Programs can be stored in ROM. A processor can perform any appropriate action and processing by loading the program into RAM.

[0123] Possible implementations of this application can be achieved through a program, enabling the device to perform any of the processes discussed in the foregoing embodiments. Possible implementations of this application can also be achieved through hardware or a combination of software and hardware.

[0124] In some implementations, the program may be tangibly contained in a computer-readable storage medium, which may include in a device (such as in memory) or other storage device accessible by the device. The program may be loaded from the computer-readable storage medium into RAM for execution. The computer-readable storage medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc.

[0125] This application also provides a computer-readable storage medium storing computer instructions or program code thereon, which, when executed by a processor, causes the processor to perform the methods and functions involved in any of the above embodiments. A computer-readable medium can be any tangible medium that contains or stores a program for or relating to an instruction execution system, apparatus, or device. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. More detailed examples of computer-readable storage media include electrical connections with one or more wires, magnetic media (e.g., disks, floppy disks, hard disks, magnetic tapes, magnetic storage devices), optical media (e.g., optical storage devices, DVDs), semiconductor media (e.g., solid-state drives), random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), or any suitable combination thereof.

[0126] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. Embodiments of this application also provide at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. This computer program product includes one or more computer-executable instructions, such as instructions included in a program module, which execute in a device on a target's real or virtual processor to perform the processes, methods, and functions involved in any of the above embodiments. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means.

[0127] This application also proposes a computer program product, including a computer program or instructions that, when run on a computer, cause the computer to perform the processes, methods, and functions described in the above embodiments. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of program modules can be combined or divided as needed. The machine-executable instructions for the program modules can be executed locally or in a distributed device. In a distributed device, the program modules can reside in both local and remote storage media.

[0128] Generally, the various embodiments of this application can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software, which can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are shown and described as block diagrams, flowcharts, or represented using some other illustration, it should be understood that the blocks, apparatuses, systems, techniques, or methods described herein can be implemented as, as non-limiting examples, in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0129] It should be noted that although embodiments of this application have been described above with reference to the accompanying drawings, these embodiments are not independent of each other, and they can be combined to obtain other embodiments. The methods, situations, categories, and classifications of embodiments in this application are only for the convenience of description and should not constitute a special limitation. Various methods, categories, situations, and features in embodiments can be combined with each other if logically consistent. The various embodiments of this application can be arbitrarily combined to achieve different technical effects. The embodiments of this application will not list various combinations.

[0130] Furthermore, although the operation of the methods of this disclosure is described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all of the operations shown must be performed to achieve the desired result. Rather, the steps depicted in the flowcharts may be performed in a different order. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps. It should also be noted that the features and functions of two or more devices according to this disclosure may be embodied in one device. Conversely, the features and functions of one device described above may be further divided and embodied by multiple devices.

[0131] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0132] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for managing a web console, characterized in that, The web console is provided by the service node, and its management methods are executed by the proxy server. These management methods include: The system receives and parses the first access request from the user to obtain the address information of the first target service node. The first access request is configured to include the address information of the proxy server and the address information of the first target service node. Based on the address information of the first target service node, the first access request is forwarded to the first target service node; Receive and parse the response data returned by the first target service node to obtain the access address information of the Web console; The access address information of the Web console is rewritten according to the address rewriting policy corresponding to the access address information of the Web console and the address information of the proxy server to obtain the rewritten access address information of the Web console. The response data returned by the first target service node includes the web console page of the first target service node and links from the web console page of the first target service node to the web console pages of other service nodes; The rewritten access address information for the Web console is used to ensure that all user access to the Web console pages is forwarded through the proxy server.

2. The control method for the Web console according to claim 1, characterized in that, Rewriting the address information in the response data using the address rewriting strategy corresponding to the parsing result of the response data includes: Identify whether the parsing result of the response data contains absolute address information; When absolute address information is included, the absolute address information is rewritten based on the address information of the proxy server to obtain the first rewritten address information.

3. The control method for the Web console according to claim 1, characterized in that, Rewriting the address information in the response data using the address rewriting strategy corresponding to the parsing result of the response data includes: Identify whether the parsing result of the response data contains redirection address information; If the redirection address information is included, the redirection address information is rewritten according to the address information of the proxy server to obtain the second rewritten address information.

4. The control method for the Web console according to claim 1, characterized in that, Rewriting the address information in the response data using the address rewriting strategy corresponding to the parsing result of the response data includes: Identify whether the parsing result of the response data contains hostname information; When hostname information is included, the IP address information corresponding to the hostname information is determined according to the mapping relationship between hostname and IP address; The IP address information corresponding to the hostname information is rewritten based on the address information of the proxy server to obtain the third rewritten address information.

5. The control method for the Web console according to claim 1, characterized in that, Rewriting the address information in the response data using the address rewriting strategy corresponding to the parsing result of the response data includes: Identify whether the parsing result of the response data contains dynamically spliced ​​address information; In the case of dynamically concatenated address information, identify the original IP address information corresponding to the dynamically concatenated address information; The original IP address information corresponding to the dynamically concatenated address information is rewritten based on the address information of the proxy server to obtain the fourth rewritten address information.

6. The control method for the Web console according to claim 1, characterized in that, After rewriting the access address information of the Web console according to the address rewriting policy corresponding to the access address information of the Web console and the address information of the proxy server to obtain the rewritten access address information of the Web console, the Web console management method further includes: Receive a user's first redirect request, which is configured to include access address information of the rewritten Web console, wherein the access address information of the rewritten Web console includes the address information of the proxy server and the address information of the second target service node. The user is redirected to the web console of the second target service node based on the first redirect request.

7. The control method for the Web console according to claim 1, characterized in that, The first target service node is divided into a main service node and sub-service nodes, and the management method of the Web console further includes: Receive a second access request from the user, the access request being configured to include the address information of the proxy server; The proxy server provides the user with the access address information of the main service node according to the second access request, so that the user can access the web console of the main service node through the proxy server. Receive a second redirect request from the user terminal on the Web console of the main service node, the second redirect request being configured to include the address information of the proxy server and the address information of the sub-service node; The second redirect request will redirect you to the web console of the sub-service node.

8. A control device for a web console, characterized in that, The web console is provided by the service node, and the management device for the web console is applied to the proxy server. The management device for the web console includes: The first receiving unit is used to receive and parse the first access request from the user terminal to obtain the address information of the first target service node. The first access request is configured to include the address information of the proxy server and the address information of the first target service node. The forwarding unit is used to forward the first access request to the first target service node according to the address information of the first target service node; The second receiving unit is used to receive and parse the response data returned by the first target service node to obtain the access address information of the Web console. The rewriting unit is used to rewrite the access address information of the Web console according to the address rewriting strategy corresponding to the access address information of the Web console and the address information of the proxy server, so as to obtain the rewritten access address information of the Web console. The response data returned by the first target service node includes the web console page of the first target service node and links from the web console page of the first target service node to the web console pages of other service nodes; The rewritten access address information for the Web console is used to ensure that all user access to the Web console pages is forwarded through the proxy server.

9. An apparatus comprising: processor; And a memory configured to store computer-executable instructions, which, when executed, cause the processor to perform the control method of the Web console according to any one of claims 1 to 7.

10. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instruction is executed by the processor, it implements the control method of the Web console according to any one of claims 1 to 7.

Images