Web application proxy method and device based on gateway
By intercepting DNS resolution requests and assigning proxy IP to web applications, the security proxy for web applications is realized, solving the problem of modifying network architecture and low security in the existing technology, and is suitable for various enterprise intranet architectures.
Patent Information
- Application Number
- CN202411078120.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-07
- Publication Date
- 2024-12-03
AI Technical Summary
The prior art requires modification of the original network architecture when performing web application proxying or has low security problems.
By obtaining the DNS resolution request of the browser when accessing the intranet application, we determine whether the target object is a web application, and assign it a proxy IP to it, construct the DNS response result, and return the response result to the client, and the client sends the access request with the proxy IP. , the gateway receives the request and forwards it to the service server to realize the proxy of the web application and avoid direct exposure to the public network.
There is no need to modify the original network architecture, which improves the security of web applications, adapts to different enterprise intranet architectures, and proxies intranet web applications through tunnels to avoid direct exposure to the public network.
Smart Images

Figure CN119071028A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of network security, and in particular relates to a gateway-based Web application proxy method and device. Background Art
[0002] With the rapid development of network technology, network security has attracted great attention from the whole society. Firewalls, load balancing and other equipment have been deployed in large quantities in actual network environments. Application proxy is one of the main functions provided by firewalls, data leakage prevention, load balancing and other equipment.
[0003] Currently, the following methods are mainly used to access web applications within the enterprise from the external network:
[0004] 1. Map internal applications directly to the public Internet on the enterprise intranet firewall and access them directly on the public Internet.
[0005] 2. Deploy a web application gateway in the isolated network area (DMZ network area) of the enterprise to proxy the web applications in the intranet area. Open an entrance on the enterprise boundary firewall to allow external traffic to access the web application gateway.
[0006] 3. Deploy a VPN in the enterprise intranet, and access the company's intranet applications after launching the VPN client in the public network outside the enterprise.
[0007] However, the above solutions all have certain defects. In solution 1, there are certain security risks in opening ports on the boundary firewall of the enterprise intranet, which directly exposes the intranet application to the public network. The application is at risk of being attacked by weak passwords, DDoS, SQL injection and other means. In addition, it is necessary to detect and intercept the port, or deploy a security system such as a WAF firewall in front of the web application. In solution 2, a web application gateway is deployed in the enterprise's isolation zone network, and the gateway is used to converge the intranet web application exports and uniformly expose them to the external network. This operation can reduce the attack surface, but this operation has a large adjustment to the architecture of the enterprise intranet. It may be necessary to modify the public network IP pointing to point to the web application gateway. Or adjust the internal routing policy to direct the traffic to the web application gateway. In solution 3, the solution of using VPN can avoid the problems in the above two solutions. However, if the web application in the enterprise does not have a public domain name, it is only resolved on the DNS server of the intranet. After starting the VPN, when accessing the web application in the enterprise intranet, the DNS resolution fails, and the traffic cannot be directed to the client through the routing policy. At this time, additional modifications are also required to access it. Summary of the invention
[0008] In order to overcome the deficiencies of the prior art, the present invention provides a gateway-based Web application proxy method and device to solve the problem in the prior art that the original network architecture needs to be modified or the security is low when performing Web application proxy.
[0009] One embodiment of the present invention provides a gateway-based Web application proxy method, comprising the following steps:
[0010] Obtaining a DNS resolution request from a browser when accessing an intranet application, and determining whether the target object of the DNS resolution request is a Web application;
[0011] When the target object is a Web application, a corresponding proxy IP is allocated to the Web application, and a DNS response result is constructed based on the proxy IP;
[0012] Send the DNS response result back to the client, and based on the DNS response result, send an access request to the proxy IP through the client;
[0013] After receiving the access request, the gateway determines the corresponding Web application based on the proxy IP, forwards the access request to the business server and returns a response result.
[0014] In one embodiment, obtaining a DNS resolution request when a browser accesses an intranet application, and determining whether a target object of the DNS resolution request is a Web application, includes:
[0015] When the browser accesses the intranet application, the DNS resolution request is triggered, and the DNS resolution request is intercepted by the client;
[0016] In the client, it is determined whether the target object of the DNS resolution request is a Web application.
[0017] In one embodiment, when the target object is a Web application, a corresponding proxy IP is allocated to the Web application, and a DNS response result is constructed based on the proxy IP, including:
[0018] When the target object is a Web application, the DNS resolution request is hijacked by the client and sent to the gateway;
[0019] A proxy IP is allocated to the Web application in the FakeIP segment through the gateway, the real address of the Web application is saved, and a DNS response result is constructed based on the proxy IP.
[0020] In one embodiment, the DNS response result is sent back to the client, and based on the DNS response result, an access request is sent to the proxy IP through the client, including:
[0021] The Fake DNS resolution result is responded to the client, and after the client receives the Fake DNS resolution result, the Fake DNS result is responded to the browser;
[0022] Obtain the proxy IP in the Fake DNS result through the browser, and send an access request to the proxy IP;
[0023] The access request is forwarded to the gateway based on the client and through the tunnel.
[0024] In one embodiment, after the gateway receives the access request, it determines the corresponding Web application based on the proxy IP and forwards the request traffic and response, including:
[0025] After the gateway receives the access request, it obtains the Web application corresponding to the proxy IP and the real address of the Web application;
[0026] The access request and the real address are forwarded to the business server through the gateway, and after the business server receives the access request and the real address, a response result is returned to the browser to enable the browser to access the Web application.
[0027] In one embodiment, obtaining a DNS resolution request when a browser accesses an intranet application and determining whether a target object of the DNS resolution request is a Web application includes:
[0028] Enable the local DNS resolution request interception function on the client.
[0029] In one embodiment, the method further comprises:
[0030] When the target object is not a Web application, a response result is returned to the browser through a public DNS server.
[0031] One embodiment of the present invention further provides a gateway-based Web application proxy device, comprising:
[0032] A judgment module is used to obtain a DNS resolution request when the browser accesses an intranet application, and to judge whether the target object of the DNS resolution request is a Web application;
[0033] An allocation module, for allocating a corresponding proxy IP to the Web application when the target object is a Web application, and constructing a DNS response result based on the proxy IP;
[0034] A first response module, used for responding the DNS response result back to the client, and sending an access request to the proxy IP through the client based on the DNS response result;
[0035] The second response module is used to determine the corresponding Web application based on the proxy IP after the gateway receives the access request, forward the access request to the business server and return a response result.
[0036] One embodiment of the present invention further provides a readable storage medium, in which a computer program is stored. The computer program includes program instructions. When the program instructions are executed by a processor of an electronic device, the processor executes the steps of any one of the gateway-based Web application proxy methods described above.
[0037] One embodiment of the present invention further provides an electronic device, comprising: a processor and a memory, the memory being used to store computer program code, the computer program code comprising computer instructions, and when the processor executes the computer instructions, the electronic device executes the steps of any one of the gateway-based Web application proxy methods described above.
[0038] By applying the above technical solution, a gateway-based Web application proxy method is proposed, including obtaining the DNS resolution request of the browser when accessing the intranet application, and judging whether the target object of the DNS resolution request is a Web application; when the target object is a Web application, assigning a corresponding proxy IP to the Web application, and constructing a DNS response result based on the proxy IP; responding the DNS response result back to the client, and sending an access request to the proxy IP through the client based on the DNS response result; after the gateway receives the access request, it determines the corresponding Web application based on the proxy IP, forwards the access request to the business server and returns the response result. By intercepting the DNS resolution request and setting the proxy IP for the Web application, the security of the Web application is guaranteed, and the original network architecture does not need to be modified to adapt to different enterprise intranet architectures. BRIEF DESCRIPTION OF THE DRAWINGS
[0039] In order to more clearly illustrate the embodiments of the present invention 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 some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the structures shown in these drawings without paying creative work.
[0040] Figure 1 It is a schematic flow diagram of the method of the present invention;
[0041] Figure 2 It is a schematic diagram of the structure of the device of the present invention;
[0042] Figure 3 It is a structural schematic diagram of the electronic device of the present invention. DETAILED DESCRIPTION
[0043] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0044] It should be noted that if the embodiments of the present invention involve directional indications (such as up, down, left, right, front, back, etc.), the directional indications are only used to explain the relative position relationship, movement status, etc. between the components in a certain specific posture. If the specific posture changes, the directional indication will also change accordingly.
[0045] In addition, if there are descriptions involving "first", "second", etc. in the embodiments of the present invention, the descriptions of "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of technical features indicated. Therefore, the features limited to "first" and "second" may explicitly or implicitly include at least one of the features. In addition, if "and / or" or "and / or" appears in the full text, its meaning includes three parallel solutions. Taking "A and / or B" as an example, it includes solution A, solution B, or solutions that satisfy both A and B. In addition, the technical solutions between the various embodiments can be combined with each other, but it must be based on the ability of ordinary technicians in this field to implement. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such combination of technical solutions does not exist and is not within the scope of protection required by the present invention.
[0046] like Figure 1 One embodiment of the present invention provides a gateway-based Web application proxy method, comprising the following steps:
[0047] S100: Obtain a DNS resolution request when a browser accesses an intranet application, and determine whether a target object of the DNS resolution request is a Web application.
[0048] Specifically, browser access to intranet applications actually refers to the browser accessing the domain name of the intranet application. During the access, a DNS resolution request is triggered, and the DNS resolution request is intercepted and used to determine whether the browser is accessing a Web application.
[0049] Specifically, the DNS resolution request process involves multiple steps, including the client making a request, querying the local domain name server, querying the root domain name server, and returning the final result. Client makes a request: When a user accesses a website through a browser, the client makes a domain name resolution request and sends the request to the local domain name server. The local domain name server performs a query and returns a response result. This process ensures that users can access resources on the Internet through domain names. Even if the actual IP addresses of these resources may change frequently, users do not need to directly remember or use IP addresses to access them. DNS resolution is one of the key parts for the normal operation of the Internet.
[0050] S200: When the target object is a Web application, a corresponding proxy IP is allocated to the Web application, and a DNS response result is constructed based on the proxy IP.
[0051] Specifically, when the target object is a Web application, a Web application proxy process is required. At this time, a proxy IP is assigned to the Web application, and the real IP of the Web application is responded through the proxy IP to ensure the security of the Web application, and the DNS response result is built through the proxy IP. This step is performed by the gateway, which is further a zero-trust gateway. The application of a zero-trust gateway can further improve the security of the Web application proxy process.
[0052] S300: Send the DNS response result back to the client, and based on the DNS response result, send an access request to the proxy IP through the client.
[0053] Specifically, after the DNS response result is constructed, the DNS response result is returned to the client, the client receives the DNS response result, identifies the proxy IP in the DNS response result, and further sends an access request to the proxy IP.
[0054] S400: After receiving the access request, the gateway determines the corresponding Web application based on the proxy IP, forwards the access request to the business server and returns a response result.
[0055] Specifically, after the gateway receives the proxy IP, it determines the Web application corresponding to the proxy IP and its corresponding real IP, forwards the access request traffic to the business server, and forwards the response result returned by the business server to the client and browser, thus completing the proxy process of the Web application.
[0056] In one embodiment, obtaining a DNS resolution request when a browser accesses an intranet application, and determining whether a target object of the DNS resolution request is a Web application, includes:
[0057] When the browser accesses the intranet application, the DNS resolution request is triggered, and the DNS resolution request is intercepted by the client;
[0058] In the client, it is determined whether the target object of the DNS resolution request is a Web application.
[0059] Specifically, this step is implemented by the browser and the client. When the browser accesses the intranet application, it will trigger a DNS resolution request. The client intercepts the DNS resolution request in real time and determines whether the target object that the browser needs to access is a Web application through the DNS resolution request.
[0060] In one embodiment, when the target object is a Web application, a corresponding proxy IP is allocated to the Web application, and a DNS response result is constructed based on the proxy IP, including:
[0061] When the target object is a Web application, the DNS resolution request is hijacked by the client and sent to the gateway;
[0062] A proxy IP is allocated to the Web application in the FakeIP segment through the gateway, the real address of the Web application is saved, and a DNS response result is constructed based on the proxy IP.
[0063] Specifically, FakeIP is an IP segment from which a DNS resolution address is assigned to a web application. It should be noted that those skilled in the art can flexibly change IP segments according to different actual application scenarios. Therefore, even if an IP segment different from FakeIP is used, it should be within the scope of protection of this application.
[0064] When the target object is a Web application, the proxy process of the Web application is required. At this time, the DNS resolution request is sent to the zero-trust gateway. The zero-trust gateway assigns a proxy IP to the Web application from the FakeIP segment. Different Web applications have different proxy IPs, and there will not be two Web applications with the same proxy IP. The real address of the Web application is saved. In essence, the correspondence between the proxy IP, Web application and its corresponding real address is established here, and the proxy IP is written to the DNS response result to ensure that the DNS response result carries the proxy IP.
[0065] In some embodiments, the DNS response result is sent back to the client, and based on the DNS response result, an access request is sent to the proxy IP through the client, including:
[0066] The Fake DNS resolution result is responded to the client, and after the client receives the Fake DNS resolution result, the Fake DNS result is responded to the browser;
[0067] Obtain the proxy IP in the Fake DNS result through the browser, and send an access request to the proxy IP;
[0068] The access request is forwarded to the gateway based on the client and through the tunnel.
[0069] Specifically, the DNS response result process of the zero-trust gateway here includes two steps. The first step is to respond the Fake DNS resolution result back to the client. The client responds to the Fake DNS resolution result and responds the Fake DNS result back to the browser. The browser obtains the proxy IP carried in the response result and sends an access request to the proxy IP.
[0070] Specifically, a tunnel refers to an information channel established between the zero-trust gateway and the client, through which access requests are sent to the zero-trust gateway.
[0071] In some embodiments, after the gateway receives the access request, it determines the corresponding Web application based on the proxy IP and forwards the request traffic and response, including:
[0072] After the gateway receives the access request, it obtains the Web application corresponding to the proxy IP and the real address of the Web application;
[0073] The access request and the real address are forwarded to the business server through the gateway, and after the business server receives the access request and the real address, a response result is returned to the browser to enable the browser to access the Web application.
[0074] In this embodiment, when the gateway receives an access request, it determines the Web application that the browser actually wants to access and its real address based on the correspondence between the proxy IP and the real address in the above steps, and forwards the Web application and its real address to the business server. The business server builds a business response result based on the real address, and forwards the business response result to the browser through the zero-trust gateway and the client in turn. Through the above steps, only the proxy IP is needed to implement the proxy process when the browser accesses the intranet application, thereby ensuring the security of the intranet and there is no need to modify the network architecture of the intranet.
[0075] In some embodiments, obtaining a DNS resolution request of a browser when accessing an intranet application and determining whether a target object of the DNS resolution request is a Web application includes:
[0076] Enable the local DNS resolution request interception function on the client.
[0077] Specifically, before obtaining the DNS resolution request of the browser when accessing the intranet application and determining whether the target object of the DNS resolution request is a Web application, it is necessary to enable the local DNS resolution request interception function on the client to ensure that the DNS resolution request can be intercepted in real time on the local machine.
[0078] In some embodiments, the method further comprises:
[0079] When the target object is not a Web application, a response result is returned to the browser through a public DNS server.
[0080] Specifically, when the client recognizes that the target object is not a Web application, it directly requests the public network server to respond to the browser without performing a proxy process.
[0081] Applying the above technical solution, a gateway-based Web application proxy method and device are proposed, including obtaining the DNS resolution request of the browser when accessing the intranet application, and judging whether the target object of the DNS resolution request is a Web application; when the target object is a Web application, assigning a corresponding proxy IP to the Web application, and constructing a DNS response result based on the proxy IP; responding the DNS response result back to the client, and sending an access request to the proxy IP through the client based on the DNS response result; after the gateway receives the access request, determining the corresponding Web application based on the proxy IP, forwarding the access request to the business server and returning the response result. By intercepting the DNS resolution request and setting a proxy IP for the Web application, the security of the Web application is guaranteed, and the original network architecture does not need to be modified to adapt to different enterprise intranet architectures.
[0082] One embodiment of the present invention also provides a gateway-based Web application proxy device, such as Figure 2 ,include:
[0083] The judgment module 100 is used to obtain a DNS resolution request when the browser accesses an intranet application, and to judge whether the target object of the DNS resolution request is a Web application;
[0084] The allocation module 200 is used to allocate a corresponding proxy IP to the Web application when the target object is a Web application, and to construct a DNS response result based on the proxy IP;
[0085] The first response module 300 is used to respond the DNS response result back to the client, and based on the DNS response result, send an access request to the proxy IP through the client;
[0086] The second response module 400 is used to determine the corresponding Web application based on the proxy IP after the gateway receives the access request, forward the access request to the business server and return a response result.
[0087] The advantages of the present invention are as follows:
[0088] (1) No modification to the enterprise’s internal network architecture.
[0089] (2) No intrusion into the enterprise's internal web applications.
[0090] (3) There are no special requirements for the internal network environment of the deployed enterprise, and it is adaptable to various complex enterprise intranet architectures.
[0091] (4) Simple deployment, only one intranet server is required.
[0092] (5) Ensure the security of enterprise intranet web applications. By proxying enterprise intranet web applications through tunnels, there is no need to expose intranet applications directly to the public Internet.
[0093] (6) Since there are no requirements for the deployment network environment, no modifications are required when the internal network architecture of the enterprise changes.
[0094] In summary, the present invention hijacks the DNS traffic on the client through the zero-trust client, intercepts the DNS resolution request for accessing the intranet web application, and forwards the request to the zero-trust gateway. The gateway modifies the DNS request, allocates an IP from the FakeIP segment to the accessed web application, and responds to the DNS request to the client.
[0095] After receiving the response request, the client will send a request to FakeIP. At this time, the requested FakeIP will be intercepted by the client and sent to the gateway. After receiving the request, the gateway will find the corresponding intranet application according to FakeIP and forward the request and response to complete the access to the intranet web application.
[0096] In summary, the above solution does not require changes to the network architecture of the enterprise intranet, nor does it require changes to the web applications on the enterprise intranet. You only need to deploy a zero-trust gateway and client, and configure the intranet web application on the gateway to achieve secure access to the enterprise intranet web application from the external network.
[0097] One embodiment of the present invention further provides a readable storage medium, in which a computer program is stored. The computer program includes program instructions. When the program instructions are executed by a processor of an electronic device, the processor executes the steps of any one of the gateway-based Web application proxy methods described above.
[0098] One embodiment of the present invention further provides an electronic device, comprising: a processor and a memory, the memory being used to store computer program code, the computer program code comprising computer instructions, and when the processor executes the computer instructions, the electronic device executes the steps of any one of the gateway-based Web application proxy methods described above.
[0099] See also Figure 3 , Figure 3 A schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present invention.
[0100] The electronic device 2 includes a processor 21, a memory 22, an input device 23, and an output device 24. The processor 21, the memory 22, the input device 23, and the output device 24 are coupled via a connector, and the connector includes various interfaces, transmission lines, or buses, etc., which are not limited in the embodiments of the present invention. It should be understood that in various embodiments of the present invention, coupling refers to mutual connection in a specific manner, including direct connection or indirect connection through other devices, for example, through various interfaces, transmission lines, buses, etc.
[0101] The processor 21 may be one or more central processing units (CPUs). When the processor 21 is a CPU, the CPU may be a single-core CPU or a multi-core CPU. Optionally, the processor 21 may be a processor group consisting of multiple CPUs, and the multiple processors are coupled to each other through one or more buses. Optionally, the processor may also be other types of processors, etc., which are not limited in the embodiments of the present invention.
[0102] The memory 22 can be used to store computer program instructions and various computer program codes including program codes for executing the scheme of the present invention. Optionally, the memory includes but is not limited to random access memory (RAM), read-only memory (ROM), erasable programmable read only memory (EPROM), or portable read only memory (CD-ROM), which is used for related instructions and data.
[0103] The input device 23 is used to input data and / or signals, and the output device 24 is used to output data and / or signals. The output device 23 and the input device 24 can be independent devices or an integrated device.
[0104] It is understandable that in the embodiment of the present invention, the memory 22 is not only used to store related instructions, and the embodiment of the present invention does not limit the specific data stored in the memory.
[0105] Understandably, Figure 3 Only a simplified design of an electronic device is shown. In practical applications, the electronic device may also include other necessary components, including but not limited to any number of input / output devices, processors, memories, etc., and all video analysis devices that can implement the embodiments of the present invention are within the protection scope of the present invention.
[0106] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.
[0107] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. Those skilled in the art can also clearly understand that the descriptions of the various embodiments of the present invention have different focuses. For the convenience and brevity of description, the same or similar parts may not be repeated in different embodiments. Therefore, for parts not described or not described in detail in a certain embodiment, refer to the records of other embodiments.
[0108] In the several embodiments provided by the present invention, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0109] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0110] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0111] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program to be sealed. The computer program to be sealed includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present invention is generated in whole or in part. 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 transmitted through the computer-readable storage medium. The computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that contains one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).
[0112] A person skilled in the art can understand that to implement all or part of the processes in the above-mentioned embodiments, the processes can be completed by a computer program to instruct the relevant hardware, and the program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the above-mentioned method embodiments. The aforementioned storage medium includes: a read-only memory (ROM) or a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes.
[0113] The above description is only a preferred embodiment of the present invention, and does not limit the patent scope of the present invention. All equivalent structural changes made by using the contents of the present invention specification and drawings under the inventive concept of the present invention, or directly / indirectly applied in other related technical fields are included in the patent protection scope of the present invention.
Claims
1. A gateway-based Web application proxy method, It is characterized in that The following steps are involved: Obtaining a DNS resolution request from a browser when accessing an intranet application, and determining whether the target object of the DNS resolution request is a Web application; When the target object is a Web application, a corresponding proxy IP is allocated to the Web application, and a DNS response result is constructed based on the proxy IP; Send the DNS response result back to the client, and based on the DNS response result, send an access request to the proxy IP through the client; After receiving the access request, the gateway determines the corresponding Web application based on the proxy IP, forwards the access request to the business server and returns a response result.
2. The gateway-based Web application proxy method according to claim 1, It is characterized in that Obtaining a DNS resolution request when a browser accesses an intranet application, and determining whether a target object of the DNS resolution request is a Web application, including: When the browser accesses the intranet application, the DNS resolution request is triggered, and the DNS resolution request is intercepted by the client; In the client, it is determined whether the target object of the DNS resolution request is a Web application.
3. The gateway-based Web application proxy method according to claim 2, It is characterized in that When the target object is a Web application, a corresponding proxy IP is allocated to the Web application, and a DNS response result is constructed based on the proxy IP, including: When the target object is a Web application, the DNS resolution request is hijacked by the client and sent to the gateway; A proxy IP is allocated to the Web application in the FakeIP segment through the gateway, the real address of the Web application is saved, and a DNS response result is constructed based on the proxy IP.
4. The gateway-based Web application proxy method according to claim 3, It is characterized in that The method further comprises: sending the DNS response result back to the client, and sending an access request to the proxy IP through the client based on the DNS response result, including: The Fake DNS resolution result is responded to the client, and after the client receives the Fake DNS resolution result, the Fake DNS result is responded to the browser; Obtain the proxy IP in the Fake DNS result through the browser, and send an access request to the proxy IP; The access request is forwarded to the gateway based on the client and through the tunnel.
5. The gateway-based Web application proxy method according to claim 4, It is characterized in that After the gateway receives the access request, it determines the corresponding Web application based on the proxy IP and forwards the request traffic and response, including: After the gateway receives the access request, it obtains the Web application corresponding to the proxy IP and the real address of the Web application; The access request and the real address are forwarded to the business server through the gateway, and after the business server receives the access request and the real address, a response result is returned to the browser to enable the browser to access the Web application.
6. The gateway-based Web application proxy method according to claim 1, It is characterized in that Obtaining a DNS resolution request when a browser accesses an intranet application and determining whether a target object of the DNS resolution request is a Web application includes: Enable the local DNS resolution request interception function on the client.
7. The gateway-based Web application proxy method according to claim 1, It is characterized in that The method further comprises: When the target object is not a Web application, a response result is returned to the browser through a public DNS server.
8. A gateway-based Web application proxy device, It is characterized in that include: A judgment module is used to obtain a DNS resolution request when the browser accesses an intranet application, and to judge whether the target object of the DNS resolution request is a Web application; An allocation module, for allocating a corresponding proxy IP to the Web application when the target object is a Web application, and constructing a DNS response result based on the proxy IP; A first response module, used for responding the DNS response result back to the client, and sending an access request to the proxy IP through the client based on the DNS response result; The second response module is used to determine the corresponding Web application based on the proxy IP after the gateway receives the access request, forward the access request to the business server and return a response result.
9. An electronic device, include: A processor and a memory, characterized in that the memory is used to store computer program code, the computer program code includes computer instructions, and when the processor executes the computer instructions, the electronic device executes the steps of the gateway-based Web application proxy method as described in any one of claims 1-7.
10. A readable storage medium having a computer program stored therein, It is characterized in that The computer program includes program instructions, and when the program instructions are executed by a processor of an electronic device, the processor executes the steps of the gateway-based Web application proxy method as described in any one of claims 1-7.
Citation Information
Patent Citations
Proxy access method, user equipment, storage medium, device and system
CN110808897A
Data proxy method and system, and proxy server
CN112272158A
Webpage access method, webpage access device, storage medium and electronic equipment
CN114430409A
Access control method, device, system and equipment and storage medium
CN116938486A
Cited By
Intranet application access method and device based on connector
CN120811641A
