CN110324436B - Proxy method and device for transport layer proxy - Google Patents
Proxy method and device for transport layer proxy Download PDFInfo
- Publication number
- CN110324436B CN110324436B CN201910606284.1A CN201910606284A CN110324436B CN 110324436 B CN110324436 B CN 110324436B CN 201910606284 A CN201910606284 A CN 201910606284A CN 110324436 B CN110324436 B CN 110324436B
- Authority
- CN
- China
- Prior art keywords
- proxy
- address
- domain name
- interface
- access request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/58—Caching of addresses or names
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a proxy method and a proxy device for a transport layer proxy, wherein the method comprises the following steps: after an application layer initiates an access request, acquiring an IP address in the access request; determining a domain name corresponding to the IP address in the access request; judging whether the access request meets an agent condition or not based on the domain name; and if so, sending the access request to a proxy server. The invention can filter and distribute the proxy data by utilizing the domain name matching mode, so the invention can be suitable for the access request initiated to the domain name, and the same domain name can correspond to a plurality of IP addresses, and compared with the IP address matching mode, the domain name matching mode can simplify the setting of the matching condition.
Description
Technical Field
The present invention relates to the field of transport layer proxy technologies, and in particular, to a proxy method and apparatus for a transport layer proxy.
Background
The data transmission between the client and the server can be carried out by the proxy server as a transfer station. For example, an access request sent by a client is sent to a server to be accessed through a proxy server. If the access request sent by the client side meets the proxy condition, the access request is sent to the server to be accessed by the proxy server, otherwise, the access request is directly sent to the server. If the data proxied by the TCP/UDP transmission layer proxy needs to be filtered or distributed, setting proxy conditions by using a regular matching method of an IP address and a port. In the process of proxy of the transmission layer, the transmission layer can only obtain the IP address and the port of the server to be accessed, and if only the regular matching of the IP address and the port is used, only a simple IP request can be supported, and the method can not be suitable for the domain name request.
Disclosure of Invention
In order to solve the problem in the prior art, embodiments of the present invention provide a transport layer proxy method and apparatus. The technical scheme is as follows:
in a first aspect, a proxy method for a transport layer proxy is provided, where the method is applied to a client, and the method includes:
after an application layer initiates an access request, acquiring an IP address in the access request;
determining a domain name corresponding to the IP address in the access request;
judging whether the access request meets an agent condition or not based on the domain name;
and if so, sending the access request to a proxy server.
Optionally, the method further includes:
an application layer initiates a DNS request and sends the DNS request through a proxy interface;
receiving an IP address sent by a DNS server based on the DNS request through the proxy interface;
acquiring the domain name in the DNS request and the IP address sent by the DNS server from the proxy interface;
establishing a mapping relation between a domain name and an IP address;
correspondingly, the step of determining the domain name corresponding to the IP address in the access request includes:
and determining the domain name corresponding to the IP address in the access request based on the established mapping relation between the domain name and the IP address.
Optionally, the step of sending the DNS request through a proxy interface includes:
if the operating system is an iOS system, selecting an original DNS request interface of an OC layer, taking over the original DNS request interface by a proxy interface by using an iOS Method switzling technology, and sending the DNS request through the proxy interface;
if the operating system is an Android system, selecting an original DNS request interface of a java layer, taking over the original DNS request interface by a proxy interface by using a java reflection technology, and sending the DNS request through the proxy interface;
if a user-defined DNS request is adopted, an original DNS request interface of a native layer is selected, a proxy interface takes over the original DNS request interface by utilizing a function hijacking technology, and the DNS request is sent through the proxy interface.
Optionally, after the step of establishing the mapping relationship between the domain name and the IP address, the method includes:
judging whether the established mapping relation between the domain name and the IP address is cached in a domain name and IP address relation list or not; if not, caching the established mapping relation between the domain name and the IP address into the domain name and IP address relation list;
correspondingly, the step of determining the domain name corresponding to the IP address in the access request includes:
inquiring the IP address in the access request in the relation list of the domain name and the IP address;
and if the search is successful, determining the domain name corresponding to the IP address in the access request in the relation list of the domain name and the IP address.
Optionally, the domain name and IP address relationship list is cached in a map list of the memory.
In a second aspect, a proxy apparatus of a transport layer proxy is provided, the apparatus comprising:
a sending module, configured to initiate an access request from an application layer;
an obtaining module, configured to obtain an IP address in the access request;
a determining module, configured to determine a domain name corresponding to the IP address in the access request;
the judging module is used for judging whether the access request meets the proxy condition or not based on the domain name;
the sending module is further configured to send the access request to a proxy server when the access request meets a proxy condition.
Optionally, the apparatus further includes a receiving module and a creating module;
the sending module is further used for sending the DNS request through a proxy interface when the DNS request is initiated by an application layer;
the receiving module is used for receiving an IP address sent by a DNS server based on the DNS request through the proxy interface;
the creation module is used for acquiring the domain name in the DNS request and the IP address sent by the DNS server from the proxy interface and establishing a mapping relation between the domain name and the IP address;
correspondingly, the determining module is specifically configured to determine the domain name corresponding to the IP address in the access request based on the established mapping relationship between the domain name and the IP address.
Optionally, the sending module is specifically configured to:
if the operating system is an iOS system, selecting an original DNS request interface of an OC layer, taking over the original DNS request interface by a proxy interface by using an iOS Method Swizzling technology, and sending the DNS request through the proxy interface;
if the operating system is an Android system, selecting an original DNS request interface of a java layer, taking over the original DNS request interface by a proxy interface by using a java reflection technology, and sending the DNS request through the proxy interface;
if a user-defined DNS request is adopted, an original DNS request interface of a native layer is selected, a proxy interface takes over the original DNS request interface by utilizing a function hijacking technology, and the DNS request is sent through the proxy interface.
Optionally, the creating module is specifically configured to:
judging whether the established mapping relation between the domain name and the IP address is cached in a domain name and IP address relation list or not; if not, caching the established mapping relation between the domain name and the IP address into the domain name and IP address relation list;
correspondingly, the determining module is specifically configured to:
inquiring the IP address in the access request in the relation list of the domain name and the IP address;
and if the search is successful, determining the domain name corresponding to the IP address in the access request in the relation list of the domain name and the IP address.
In a third aspect, there is provided a proxy apparatus comprising a processor and a memory, wherein the memory stores at least one instruction, at least one program, code set, or instruction set, and the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by the processor to implement the proxy method of transport layer proxy according to the first aspect.
In a fourth aspect, a computer-readable storage medium is provided, which stores a computer program, wherein the computer program is configured to implement the proxy method of the transport layer proxy according to the first aspect when executed by a processor.
The embodiment of the invention determines the domain name corresponding to the IP address after the IP address is obtained by the transport layer agent, so that the data of the agent can be filtered and distributed by utilizing a domain name matching mode, the embodiment of the invention can also be suitable for an access request initiated to the domain name, and the domain name matching mode can simplify the setting of matching conditions compared with the IP address matching mode because the same domain name can correspond to a plurality of IP addresses.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a block diagram of a network framework according to an embodiment of the present invention;
fig. 2 is a flowchart of a proxy method of a transport layer proxy according to an embodiment of the present invention;
fig. 3 is a flowchart illustrating a proxy method of a transport layer proxy according to an embodiment of the present invention;
fig. 4 is a schematic flowchart of establishing a mapping relationship between a domain name and an IP address according to an embodiment of the present invention;
fig. 5 is a block diagram of a proxy apparatus of a transport layer proxy according to an embodiment of the present invention;
fig. 6 is a block diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
The embodiment of the invention provides a proxy method of a transport layer proxy, which can be applied to a network framework shown in fig. 1. The network framework comprises a proxy device, a proxy server and a server to be accessed. Wherein the proxy device may be a client. The proxy device is embedded with a transport layer proxy SDK (Software Development Kit), and executes the proxy method provided by the implementation of the invention by calling the transport layer proxy SDK. The proxy method comprises the following steps: after initiating an access request from an application layer, a proxy device acquires an IP address in the access request, then determines a domain name corresponding to the IP address in the access request, and judges whether the access request meets proxy conditions or not based on the domain name; and if so, sending the access request to the proxy server, and sending the access request to the server to be accessed by the proxy server.
Referring to fig. 2, a flowchart of a proxy method of a transport layer proxy according to an embodiment of the present invention is provided, where the method specifically includes the following steps.
Step 201, an application layer of the proxy device sends a DNS request and sends the DNS request through a proxy interface.
In step 202, the proxy device receives, through the proxy interface, an IP address sent by the DNS server based on the DNS request.
In a specific application, the proxy device receives the port number at the same time as the IP address.
Step 203, the proxy device obtains the domain name in the DNS request and the IP address sent by the DNS server from the proxy interface.
As shown in fig. 3, the step of initiating the access request by the application layer includes: the first step is to initiate DNS request to domain name and obtain IP address, the second step is to use the IP address to initiate connection, namely to connect the server to be accessed, to send access request and to receive data. In the scenario of embedding a transport layer proxy SDK into a proxy device, a proxy interface takes over an original DNS request interface, namely, the original DNS request interface is replaced by the proxy interface, the proxy interface is connected with a DNS server, and the proxy interface is used for proxy data transceiving. Specifically, when the application layer initiates a DNS request, the proxy interface intercepts the DNS request, sends the DNS request to the DNS server, and then receives an IP address returned by the DNS server.
As shown in fig. 4, the embodiment of the present invention is applicable to agent devices of an iOS system and an Android system. If the operating system of the proxy device is an iOS system, an original DNS request interface of the OC layer is selected, and the original DNS request interface is taken over by the proxy interface using the iOS Method switzling (iOS Method conversion) technique. If the operating system of the agent device is an Android system, selecting an original DNS request interface of a java layer, and taking over the original DNS request interface by the agent interface by using a java reflection technology. If the proxy device adopts the custom DNS request, an original DNS request interface of a native layer is selected, and the original DNS request interface is taken over by the proxy interface by using a function hijack technology.
The embodiment of the invention directly obtains the domain name from the proxy interface, so that the application protocol analysis is not needed in the proxy process of the transport layer proxy, and the embodiment of the invention can be suitable for all application protocol scenes and can also reduce the code amount of the proxy.
And under the condition that the application layer initiates the access request of the domain name, the mapping relation between the domain name and the IP address can be obtained from the proxy interface and cached, so that a domain name and IP address relation list does not need to be transmitted by a newly opened interface, the development difficulty is reduced, the embedding efficiency of the proxy SDK of the transmission layer and the operation efficiency in the domain name matching process are improved, the proxy does not need to actively carry out domain name resolution on the DNS request, and the embedding operation can be simplified.
In implementation, the mapping relationship between the domain name and the IP address can be cached in a list, i.e., a domain name and IP address relationship list. The domain name and IP address relationship list may be cached in a map (associated container) list of the memory.
The process of caching the mapping relationship between the domain name and the IP address by the proxy device can be summarized as follows: after establishing the mapping relationship between the domain name and the IP address, the proxy device determines whether the established mapping relationship between the domain name and the IP address has been cached in a domain name and IP address relationship list, and specifically, whether the established mapping relationship between the domain name and the IP address has been cached in the list can be determined by IP address query; if not, caching the established mapping relation between the domain name and the IP address into the domain name and IP address relation list, if so, caching is not needed, and the next step is carried out; and returning the domain name resolution result to the original DNS request interface. After receiving a domain name resolution result, namely an IP address and a port number, sent by a DNS server by using a proxy interface, the proxy device returns the received domain name resolution result to an original DNS request interface, thereby completing a domain name resolution process.
In step 205, after initiating an access request from the application layer, the proxy device obtains an IP address in the access request.
After receiving the IP address sent by the DNS server, the proxy device may send an access request to the server of the IP address to obtain the target data.
In step 206, the proxy device determines a domain name corresponding to the IP address in the access request.
The process of determining the domain name corresponding to the IP address in the access request by the proxy device specifically includes: after the IP address in the access request is acquired, inquiring the IP address in the relation list of the domain name and the IP address; if the search is successful, determining a domain name corresponding to the IP address in the relation list of the domain name and the IP address; if the IP address is not found, the process is ended.
The proxy device can perform regular matching on the domain name by using a domain name regular expression, and if the matching is successful, the access request aiming at the domain name is in accordance with proxy conditions; if the matching is not successful, the access request is not qualified by the agent.
And step 208, if the request is consistent, sending the access request to the proxy server.
If the domain name meets the proxy condition, the request for accessing the IP address needs to be proxied, so the proxy device needs to send the request for accessing the IP address to the proxy server, and the proxy server sends the access request to the server to be visited.
In implementation, a plurality of proxy conditions, that is, a plurality of domain name regular expressions, may be set. Each proxy condition corresponds to a different functional proxy, e.g., an acceleration proxy or an encryption proxy. And the proxy device matches the domain name with each domain name regular expression, and performs corresponding proxy permission on the access request every time the matching is successful.
The embodiment of the invention determines the domain name corresponding to the IP address after the IP address is obtained by the transport layer agent, so that the data of the agent can be filtered and distributed by utilizing a domain name matching mode, the embodiment of the invention can also be suitable for an access request initiated to the domain name, and the domain name matching mode can simplify the setting of matching conditions compared with the IP address matching mode because the same domain name can correspond to a plurality of IP addresses.
Referring to fig. 5, a block diagram of a proxy apparatus for a transport layer proxy according to an embodiment of the present invention is shown, where the proxy apparatus includes:
a sending module 501, configured to initiate an access request from an application layer;
an obtaining module 502, configured to obtain an IP address in the access request;
a determining module 503, configured to determine a domain name corresponding to the IP address in the access request;
a determining module 504, configured to determine whether the access request meets a proxy condition based on the domain name;
the sending module 501 is further configured to send the access request to a proxy server when the access request meets a proxy condition.
Optionally, the apparatus further comprises a receiving module 505 and a creating module 506;
the sending module 501 is further configured to send a DNS request through a proxy interface when the application layer initiates the DNS request;
the receiving module 505 is configured to receive, through the proxy interface, an IP address sent by the DNS server based on the DNS request;
the creating module 506 is configured to obtain the domain name in the DNS request and the IP address sent by the DNS server from the proxy interface, and establish a mapping relationship between the domain name and the IP address;
correspondingly, the determining module 503 is specifically configured to determine, based on the established mapping relationship between the domain name and the IP address, the domain name corresponding to the IP address in the access request.
Optionally, the sending module 501 is specifically configured to:
if the operating system is an iOS system, selecting an original DNS request interface of an OC layer, taking over the original DNS request interface by a proxy interface by using an iOS Method switzling technology, and sending the DNS request through the proxy interface;
if the operating system is an Android system, selecting an original DNS request interface of a java layer, taking over the original DNS request interface by a proxy interface by using a java reflection technology, and sending the DNS request through the proxy interface;
if a user-defined DNS request is adopted, an original DNS request interface of a native layer is selected, a proxy interface takes over the original DNS request interface by utilizing a function hijacking technology, and the DNS request is sent through the proxy interface.
Optionally, the creating module 506 is specifically configured to:
judging whether the established mapping relation between the domain name and the IP address is cached in a domain name and IP address relation list or not; if not, caching the established mapping relation between the domain name and the IP address into the domain name and IP address relation list;
correspondingly, the determining module 503 is specifically configured to:
inquiring the IP address in the access request in the relation list of the domain name and the IP address;
and if the search is successful, determining the domain name corresponding to the IP address in the access request in the relation list of the domain name and the IP address.
The embodiment of the invention determines the domain name corresponding to the IP address after the IP address is obtained by the transport layer agent, so that the data of the agent can be filtered and distributed by utilizing a domain name matching mode, the embodiment of the invention can also be suitable for an access request initiated to the domain name, and the domain name matching mode can simplify the setting of matching conditions compared with the IP address matching mode because the same domain name can correspond to a plurality of IP addresses.
It should be noted that: the proxy device of the transport layer proxy provided in the foregoing embodiment may be implemented based on a computer program, and the device is only illustrated by dividing each functional module in the screening process, and in practical applications, the function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules, so as to complete all or part of the functions described above. In addition, the proxy device of the transport layer proxy provided in the above embodiments and the proxy method embodiment of the transport layer proxy belong to the same concept, and specific implementation processes thereof are described in detail in the method embodiments and are not described herein again.
Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present invention. The electronic device 600 may vary widely in configuration or performance and may include one or more central processors 622 (e.g., one or more processors) and memory 632, one or more storage media 630 that store applications 642 or data 644, i.e., a computer-readable storage medium (e.g., one or more mass storage devices). Memory 632 and storage medium 630 may be, among other things, transient or persistent storage. The program stored in the storage medium 630 may include one or more modules (not shown), each of which may include a sequence of instructions operating on the electronic device. Still further, the central processor 622 may be configured to communicate with the storage medium 630 to execute a series of instruction operations in the storage medium 630 on the electronic device 600.
The electronic device 600 may also include one or more power supplies 624, one or more wired or wireless network interfaces 650, one or more input-output interfaces 658, one or more keyboards 654, and/or one or more operating systems 641, such as Windows Server, mac OS XTM, unixTM, linuxTM, freeBSDTM, etc.
The electronic device 600 may include a memory having stored therein at least one instruction, at least one program, set of codes, or set of instructions that is loaded and executed by the processor to implement the proxy method of transport layer proxy as described above.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (8)
1. A proxy method of transport layer proxy, which is applied to a proxy device, wherein the proxy device embeds a transport layer proxy (SDK) and takes over an original DNS request interface by a proxy interface, and the method comprises the following steps:
an application layer initiates a DNS request and sends the DNS request through the proxy interface;
receiving an IP address sent by a DNS server based on the DNS request through the proxy interface;
acquiring the domain name in the DNS request and the IP address sent by the DNS server from the proxy interface;
establishing a mapping relation between a domain name and an IP address;
after an application layer initiates an access request, acquiring an IP address in the access request;
determining a domain name corresponding to the IP address in the access request based on the established mapping relation between the domain name and the IP address;
judging whether the access request meets an agent condition or not based on the domain name; and if so, sending the access request to the proxy server.
2. The method of claim 1, wherein the step of sending the DNS request through a proxy interface comprises:
if the operating system is an iOS system, selecting an original DNS request interface of an OC layer, taking over the original DNS request interface by a proxy interface by using an iOS Method switzling technology, and sending the DNS request through the proxy interface;
if the operating system is an Android system, selecting an original DNS request interface of a java layer, taking over the original DNS request interface by a proxy interface by using a java reflection technology, and sending the DNS request through the proxy interface;
if a user-defined DNS request is adopted, an original DNS request interface of a native layer is selected, a proxy interface takes over the original DNS request interface by utilizing a function hijacking technology, and the DNS request is sent through the proxy interface.
3. The method according to claim 1, wherein the step of establishing the mapping relationship between the domain name and the IP address comprises:
judging whether the established mapping relation between the domain name and the IP address is cached in a domain name and IP address relation list or not; if not, caching the established mapping relation between the domain name and the IP address into the domain name and IP address relation list;
correspondingly, the step of determining the domain name corresponding to the IP address in the access request includes:
inquiring the IP address in the access request in the relation list of the domain name and the IP address;
and if the search is successful, determining the domain name corresponding to the IP address in the access request in the relation list of the domain name and the IP address.
4. The method of claim 3, wherein the list of domain name to IP address relationships is cached in a map list in memory.
5. A proxy device of a transport layer proxy, wherein the proxy device embeds a transport layer proxy SDK, and takes over an original DNS request interface by a proxy interface, the device comprising:
a receiving module, configured to receive, through the proxy interface, an IP address sent by a DNS server based on the DNS request;
the creating module is used for acquiring the domain name in the DNS request and the IP address sent by the DNS server from the proxy interface and establishing a mapping relation between the domain name and the IP address;
the system comprises a sending module, a receiving module and a sending module, wherein the sending module is used for sending a DNS request through a proxy interface when the application layer initiates the DNS request, and is used for initiating an access request from the application layer;
an obtaining module, configured to obtain an IP address in the access request;
a determining module, configured to determine, based on the established mapping relationship between the domain name and the IP address, a domain name corresponding to the IP address in the access request;
the judging module is used for judging whether the access request meets the proxy condition or not based on the domain name;
the sending module is further configured to send the access request to a proxy server when the access request meets a proxy condition.
6. The apparatus according to claim 5, wherein the creation module is specifically configured to:
judging whether the established mapping relation between the domain name and the IP address is cached in a domain name and IP address relation list or not; if not, caching the established mapping relation between the domain name and the IP address into the domain name and IP address relation list;
correspondingly, the determining module is specifically configured to:
inquiring the IP address in the access request in the relation list of the domain name and the IP address;
and if the search is successful, determining the domain name corresponding to the IP address in the access request in the relation list of the domain name and the IP address.
7. An electronic device comprising a processor and a memory, the memory having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions, the at least one instruction, the at least one program, the set of codes, or the set of instructions being loaded and executed by the processor to implement the proxy method of transport layer proxy of any of claims 1 to 4.
8. A computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the proxy method of a transport layer proxy of any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910606284.1A CN110324436B (en) | 2019-07-05 | 2019-07-05 | Proxy method and device for transport layer proxy |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910606284.1A CN110324436B (en) | 2019-07-05 | 2019-07-05 | Proxy method and device for transport layer proxy |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110324436A CN110324436A (en) | 2019-10-11 |
| CN110324436B true CN110324436B (en) | 2023-04-18 |
Family
ID=68122908
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910606284.1A Active CN110324436B (en) | 2019-07-05 | 2019-07-05 | Proxy method and device for transport layer proxy |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110324436B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113364741A (en) * | 2021-05-17 | 2021-09-07 | 网宿科技股份有限公司 | Application access method and proxy server |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7792994B1 (en) * | 2005-06-15 | 2010-09-07 | Symantec Corporation | Correlating network DNS data to filter content |
| CN103294507A (en) * | 2013-05-09 | 2013-09-11 | 优视科技有限公司 | Method and device for providing information of downloading resources |
| CN109359019A (en) * | 2018-08-15 | 2019-02-19 | 中国平安人寿保险股份有限公司 | Application program capacity monitoring method, device, electronic equipment and storage medium |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102340554B (en) * | 2011-09-29 | 2014-04-02 | 奇智软件（北京）有限公司 | Optimal application server selection method and device for domain name system (DNS) |
| CN104735174B (en) * | 2015-03-30 | 2018-04-13 | 北京奇艺世纪科技有限公司 | A kind of implementation method and device of HTTP Transparent Proxies |
| US10326730B2 (en) * | 2016-06-27 | 2019-06-18 | Cisco Technology, Inc. | Verification of server name in a proxy device for connection requests made using domain names |
| CN108390955B (en) * | 2018-05-09 | 2021-06-04 | 网宿科技股份有限公司 | Domain name acquisition method, website access method and server |
-
2019
- 2019-07-05 CN CN201910606284.1A patent/CN110324436B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7792994B1 (en) * | 2005-06-15 | 2010-09-07 | Symantec Corporation | Correlating network DNS data to filter content |
| CN103294507A (en) * | 2013-05-09 | 2013-09-11 | 优视科技有限公司 | Method and device for providing information of downloading resources |
| CN109359019A (en) * | 2018-08-15 | 2019-02-19 | 中国平安人寿保险股份有限公司 | Application program capacity monitoring method, device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110324436A (en) | 2019-10-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2347561B1 (en) | Determining a network interface to access a network | |
| CN111970315A (en) | Method, device and system for pushing message | |
| CN109067936B (en) | Domain name resolution method and device | |
| CN111193773B (en) | Load balancing method, device, equipment and storage medium | |
| CN112333017B (en) | Service configuration method, device, equipment and storage medium | |
| CN113259479B (en) | Data processing method and equipment | |
| JP2020510891A (en) | Detection system, method and related device | |
| CN109104368B (en) | Connection request method, device, server and computer readable storage medium | |
| CN108595280B (en) | Interface adaptation method and device, computer equipment and storage medium | |
| CN112929463A (en) | Traffic proxy method, server and system based on DNS (Domain name System) | |
| CN110909030B (en) | Information processing method and server cluster | |
| CN110324436B (en) | Proxy method and device for transport layer proxy | |
| CN110278558B (en) | Message interaction method and WLAN system | |
| WO2019119962A1 (en) | Information processing method, system, terminal, and computer readable storage medium | |
| CN107612831B (en) | Transmission method and device for data message of access source station | |
| JP2003163681A (en) | Device and method for transferring packet and program | |
| CN111107039A (en) | Communication method, device and system based on TCP connection | |
| CN110661895A (en) | Network address mapping method and network address mapping equipment of server | |
| CN114356456A (en) | Service processing method, device, storage medium and electronic equipment | |
| CN112839071B (en) | Training system, training data access method and device, electronic equipment and medium | |
| CN115004657B (en) | Addressing method, addressing system and addressing device | |
| CN108696598B (en) | Method and device for transparently transmitting message received by stateless service through long connection under micro-service architecture | |
| CN112073494A (en) | Method, device and storage medium for establishing connection | |
| CN108848175B (en) | Method and device for establishing TCP connection | |
| CN112181933A (en) | Mounting method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |