CN110602269B - Method for converting domain name - Google Patents
Method for converting domain name Download PDFInfo
- Publication number
- CN110602269B CN110602269B CN201911005736.7A CN201911005736A CN110602269B CN 110602269 B CN110602269 B CN 110602269B CN 201911005736 A CN201911005736 A CN 201911005736A CN 110602269 B CN110602269 B CN 110602269B
- Authority
- CN
- China
- Prior art keywords
- domain name
- information
- response
- segment
- uri
- 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/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
-
- 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
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the invention provides a method for converting a domain name, which comprises the steps of receiving a request message initiated by a user browser; analyzing the domain name information of the request message; sending the analyzed domain name information to a WEB server; obtaining response information based on the response of the WEB server to the analyzed domain name information, and performing domain name replacement on the response information; and sending the response information after the domain name replacement to a user browser so that the user can normally access the browser. The method for converting the domain name provided by the invention realizes the domain name conversion of the hyperlink content of the request message flowing through the SSL VPN proxy server, only converts the domain name, does not relate to the modification of URI and other information, and has concise rule matching, so that the request efficiency, the response efficiency and the accuracy can be improved. The scheme has the advantages that the replacement target is single, and the replacement work can be completed more quickly and accurately.
Description
Technical Field
The invention belongs to the technical field of network security, and particularly relates to a method for converting a domain name.
Background
SSL VPN is a VPN technology that establishes a remote secure access channel based on secure socket layer protocol. The network access method has a plurality of functions such as network access, online application program and application program access, wherein the network access is the most important and marked function of the SSL VPN. In network access, links are required to be processed many times, otherwise, only the links of the non-absolute path of the page can be accessed, and access exception can be caused when the links of the absolute path are accessed.
In the prior art, a WEB reverse proxy method is generally used to realize network access. Specifically, after a user inputs a WEB reverse proxy processing request under a bookmark column or an interface input box of a browser, the method comprises the following steps: a client sends an HTTP/HTTPS request, and the URL of the request comprises the address of an SSL VPN (secure socket layer virtual private network) of a reverse proxy server, the address of an accessed background server and a resource path of the accessed background server; after the reverse proxy server SSL VPN intercepts the request, the address and the resource path of the accessed background server are extracted, and the request is forwarded normally. After a user accesses a page at the rear end of the WEB reverse proxy, clicking the page through an HTML (hypertext markup language) page in a browser to send a request; assigning a uniform resource locator type attribute in a tag or label of HTML in the request as a relative path or an absolute path; in the existing scheme, a TAG of HTML needs to be distinguished, an attribute of a URI type is assigned to be a relative path or an absolute path, the absolute path processing process is divided into different modes such as GET and POST, even redirection processing is needed in a request, and the processing process is complex and time-consuming.
Disclosure of Invention
The invention provides a method for converting domain names. The method for converting the domain name provided by the invention realizes the domain name conversion of the hyperlink content of the request message flowing through the SSL VPN proxy server, only converts the domain name, does not relate to the modification of URI and other information, and has concise rule matching, so that the request efficiency, the response efficiency and the accuracy can be improved.
In order to solve the above technical problem, the embodiment of the present invention provides the following technical solutions:
the present invention provides a method of converting a domain name, the method comprising,
receiving a request message initiated by a user browser;
analyzing the domain name information of the request message;
sending the resolved domain name information to a WEB server;
obtaining response information based on the response of the WEB server to the analyzed domain name information, and performing domain name replacement on the response information;
and sending the response information after the domain name replacement to a user browser so that the user can normally access the browser.
Preferably, the analyzing the domain name information of the request packet includes,
acquiring domain name information in the request message;
and analyzing the domain name information.
Preferably, the analyzing the domain name information includes,
removing the tail part of the domain name information;
acquiring port information;
acquiring protocol information;
acquiring a target domain name;
and obtaining the resolved domain name information.
Preferably, the obtaining of the target domain name includes,
acquiring an initial domain name;
and converting the initial domain name to obtain the target domain name.
Preferably, the resolved domain name information includes,
and combining the port information, the protocol information and the target domain name to obtain the analyzed domain name information.
Preferably, the performing domain name replacement on the response information includes,
carrying out segmentation processing on the response information to obtain different response information segments;
and respectively processing the different response information segments to finish the domain name replacement of the response information.
Preferably, the response information segment includes, in response to the response information segment,
a protocol information segment, a domain name information segment, a port information segment, and a URI information segment.
Preferably, the processing the different response information segments separately includes,
processing the protocol information segment and the domain name information segment;
processing the port information segment;
adding domain name identification information;
and obtaining the response information after the domain name replacement.
Preferably, the adding of the domain name identification information includes adding new request protocol information and domain name tail identification information.
Preferably, the response information after the domain name replacement is obtained includes,
and combining the processed protocol information segment and the domain name information segment, the processed port information segment, the domain name identification information and the URI information segment to obtain response information after domain name replacement.
Based on the disclosure of the above embodiments, it can be known that the embodiments of the present invention have the following beneficial effects:
the method for converting the domain name provided by the invention realizes the domain name conversion of the hyperlink content of the request message flowing through the SSL VPN proxy server, only converts the domain name, does not relate to the modification of URI and other information, and has concise rule matching and refining, so that the request efficiency, the response efficiency and the accuracy can be improved. The scheme has the advantages that the replacement target is single, and the replacement work can be completed more quickly and accurately. Therefore, the invention overcomes the problems of multi-step branching, request redirection, request inclusion storage and the like when the URI is converted during absolute path URL processing in the prior art. In addition, the regular expression is adopted in the rule configuration, and the matching performance, the portability and the expansibility of the regular expression have better advantages.
Drawings
Fig. 1 is a schematic flowchart of a method for converting a domain name according to an embodiment of the present invention.
Detailed Description
The following detailed description of specific embodiments of the present invention is provided in connection with the accompanying drawings, which are not intended to limit the invention.
It will be understood that various modifications may be made to the embodiments disclosed herein. Accordingly, the foregoing description should not be considered as limiting, but merely as exemplifications of embodiments. Other modifications will occur to those skilled in the art within the scope and spirit of the disclosure.
The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the disclosure and, together with a general description of the disclosure given above, and the detailed description of the embodiments given below, serve to explain the principles of the disclosure.
These and other characteristics of the invention will become apparent from the following description of a preferred form of embodiment, given as a non-limiting example, with reference to the accompanying drawings.
It should also be understood that, although the invention has been described with reference to some specific examples, a person of skill in the art shall certainly be able to achieve many other equivalent forms of the invention, having the characteristics as set forth in the claims and hence all coming within the field of protection defined thereby.
The above and other aspects, features and advantages of the present disclosure will become more apparent in view of the following detailed description when taken in conjunction with the accompanying drawings.
Specific embodiments of the present disclosure are described hereinafter with reference to the drawings; however, it is to be understood that the disclosed embodiments are merely examples of the disclosure that may be embodied in various forms. Well-known and/or repeated functions and structures have not been described in detail so as not to obscure the present disclosure with unnecessary or unnecessary detail. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present disclosure in virtually any appropriately detailed structure.
The specification may use the phrases "in one embodiment," "in another embodiment," "in yet another embodiment," or "in other embodiments," which may each refer to one or more of the same or different embodiments in accordance with the disclosure.
The embodiments of the present invention will be described in detail below with reference to the accompanying drawings,
as shown in fig. 1, an embodiment of the present invention provides a method for converting a domain name, where the method includes receiving a request packet initiated by a user browser;
analyzing the domain name information of the request message;
sending the resolved domain name information to a WEB server;
obtaining response information based on the response of the WEB server to the analyzed domain name information, and performing domain name replacement on the response information;
and sending the response information after the domain name replacement to a user browser so that the user can normally access the browser.
In this embodiment, to perform domain name conversion, first, a request message initiated by a user browser is received, for example, the request message may be received by an SSL VPN server, and the request message may be https:// svsvvhttp-test-web-com-p 8000. VPN-com/uri _ test, for example. The SSL VPN server parses the domain name information of the request packet, and for example, for the request packet, the domain name information in the request packet is svvhttp-test-web-com-p 8000.VPN. And then, sending the analyzed domain name information to a WEB server. Obtaining response information based on the response of the WEB server to the analyzed domain name information, and performing domain name replacement on the response information; in an embodiment, the WEB server needs to respond to the parsed domain name information, that is, the WEB server needs to process the parsed domain name information, and obtain response information after the processing, for example, the obtained response information may include http: while link contents of/h 1.Test. WEB. Com:8000/uri _ test1 and https:// test. WEB2.Com:8888/uri _ test2, etc. are merely exemplary in the above embodiments provided by the present invention, response information may be http:// h1.Test. WEB. Com:8000/uri _ test1 and https:// test. WEB2.Com:8888/uri _ test2, and in fact, the present invention has no limitation on the number of said response information, which may be 1, 2 or 3, or a plurality of different response information corresponding to different resource information, such as http:// h1.Test. WEB. 8000/uri _ test1, which represents a resource, and http:// test.b 2.Com:8888/uri _ test2, which represents a movie resource, and so on, the present invention does not specifically limit news resources. And finally, sending the response information after the domain name replacement to a user browser so that the user can normally access. <xnotran> , , , , , http:// h1.test.web.com:8000/uri _ test1 https:// test.web2.com:8888/uri _ test2 https:// svsvhttp-h1-test-web-com- -p8000.vpn.com/uri _ test1 https:// svsvhttps-test-web2-com- -p8888.vpn.com/uri _ test2, https:// svsvhttp-h1-test-web-com- -p8000.vpn.com/uri _ test1 https:// svsvhttps-test-web2-com- -p8888.vpn.com/uri _ test2 , https:// svsvhttp-h1-test-web-com- -p8000.vpn.com/uri _ test1 https:// svsvhttps-test-web2-com- -p8888.vpn.com/uri _ test2 . </xnotran>
In another embodiment provided by the present invention, the parsing the domain name information of the request packet includes,
acquiring domain name information in the request message;
and analyzing the domain name information.
In this embodiment, if the domain name information of the request packet needs to be analyzed, the domain name information in the request packet is first acquired, and then the domain name information is analyzed. In a specific embodiment, when the request message is https:// svsvvhhttp-test-web-com-p 8000.Vpn. Com/uri _ test, the domain name information in the request message is svsvvhhttp-test-web-com-p 8000.Vpn. Com, and after the domain name information is obtained, the domain name information is analyzed.
In other embodiments provided by the present invention, the resolving the domain name information includes,
removing the tail part of the domain name information;
acquiring port information;
acquiring protocol information;
acquiring a target domain name;
and obtaining the resolved domain name information.
In this embodiment, when the domain name information is svsvvhttp-test-web-com-p 8000.Vpn.com, analyzing the domain name information specifically includes removing a domain name tail of the domain name information, that is, removing. Vpn.com; port information is obtained, i.e., 8000. In other embodiments, if p is not followed by a number, default port information is obtained, such as 80 or 443, etc. Then acquiring protocol information, and acquiring http as the protocol information in the embodiment; then, the target domain name is obtained, for example, in the above embodiment, test-web-com is obtained, and after "-" is changed to ". Is taken as the target domain name, that is, test.
In one embodiment of the present invention, the obtaining the target domain name includes,
acquiring an initial domain name;
and converting the initial domain name to obtain the target domain name.
In the embodiment provided by the invention, if the target domain name is to be acquired, the initial domain name is acquired first, and then the initial domain name is converted to obtain the target domain name. Specifically, when the domain name information is svsvvhttp-test-web-com-p 8000.Vpn. Com, the obtained initial domain name is test-web-com, and then the initial domain name is converted, so that the target domain name can be obtained. For example, the conversion made to the initial domain name may be: changing the "-" in the initial domain name into ". The result is that test.
In an embodiment provided by the present invention, the obtained resolved domain name information includes,
and combining the port information, the protocol information and the target domain name to obtain the analyzed domain name information.
In this embodiment, the port information, the protocol information, and the target domain name are combined to obtain the resolved domain name information. In a specific embodiment, when the domain name information is svsvvhttp-test-web-com-p 8000.Vpn.com, the port information is 8000, the protocol information is http, the target domain name is test.web.com, the port information, the protocol information and the target domain name are combined together with the uri _ test field to obtain the resolved domain name information of http:// test.web.com:8000/uri _ test.
In one embodiment provided by the present invention, the performing domain name replacement on the response message includes,
carrying out segmentation processing on the response information to obtain different response information segments;
and respectively processing the different response information segments to finish the domain name replacement of the response information.
In this embodiment, after obtaining the resolved domain name information, sending the resolved domain name information to a WEB server, where the WEB server responds to the resolved domain name information to obtain response information, and for example, when the resolved domain name information is http:// test.web.com:8000/uri _ test, the response information obtained by the WEB server responding to the resolved domain name information may be http:// h1.test.web.com:8000/uri _ test1 and https:// test.web2.com:8888/uri _ test2. The domain name replacement needs to be performed on the response information, for example, the specific steps of performing domain name replacement on http:// h1.Test.web. Com:8000/uri _ test1 are as follows: firstly, segmenting http:// h1.Test.web.com:8000/uri _ test1, for example, dividing into four different response information sections of http, h1.Test.web.com, 8000 and uri _ test1, then respectively processing the four different response information sections, and finishing domain name replacement of the response information, for example, after domain name replacement is carried out on the response information, obtaining https:// svvhttp-h 1-test-web-com-p-8000. Vpn.com/uri _ test1.
The specific steps for carrying out domain name replacement on https:// test.web2.com:8888/uri _ test2 are as follows: firstly, https:// test.web2.Com:8888/uri _ test2 is processed in a segmented manner, for example, the https, test.web2.Com, 8888 and uri _ test2 can be divided into four different response information segments, and then the four different response information segments are processed respectively, so that domain name replacement of the response information can be completed, for example, after domain name replacement is performed on the response information, https:// svhttps-test-web 2-com-p-8888. Vpn.com/uri _ test2 is obtained.
In one embodiment of the present invention, the response information segment includes,
a protocol information segment, a domain name information segment, a port information segment, and a URI information segment.
In this embodiment, when the response information is http:// h1.Test.web.com:8000/URI _ test1, the response information is segmented, and the obtained http is a protocol information segment, h1.Test.web.com is a domain name information segment, 8000 is a port information segment, and URI _ test1 is a URI information segment.
When the response information is https:// test.web2.Com:8888/URI _ test2, the response information is segmented, the obtained https is a protocol information segment, the obtained test.web2.Com is a domain name information segment, the obtained 8888 is a port information segment, and the obtained URI _ test2 is a URI information segment.
In another embodiment provided by the present invention, said processing said different response information segments separately includes,
processing the protocol information segment and the domain name information segment;
processing the port information segment;
adding domain name identification information;
and obtaining the response information after the domain name replacement.
In this embodiment, when the response information is http:// h1.Test.web.com:8000/uri _ test1, the different pieces of response information are processed respectively, that is, four different pieces of response information, http, h1.Test.web.com, 8000 and uri _ test1, are processed respectively. Processing a protocol information segment http and a domain name information segment h1.test.web.com to obtain svsvvhttp-h 1-test-web-com, processing an interface information segment to obtain-p 8000, not processing uri _ test1, combining the processed different information segments, adding domain name identification information, and obtaining response information after domain name replacement. For example, the obtained response information after domain name replacement is https:// svsvvhttp-h 1-test-web-com-8000. Vpn. Com/uri _ test1.
When the response information is https:// test.web2.Com:8888/uri _ test2, the different response information sections are processed respectively, namely, four different response information sections of https, test.web2.Com, 8888 and uri _ test2 are processed respectively. Processing the protocol information section https and the domain name information section test.web2.Com to obtain svsvshttps-test-web 2-com, processing the port information section to obtain-p 8888, not processing uri _ test2, combining the processed different information sections, adding domain name identification information, and obtaining response information after domain name replacement. For example, the obtained response information after domain name replacement is https:// svsvshhttps-test-web 2-com-p 8888.Vpn. Com/uri _ test2.
In an embodiment provided by the present invention, the adding of the domain name identification information includes adding new request protocol information and domain name tail identification information.
In this embodiment, when the response information is http:// h1.Test.web.com:8000/uri _ test1, domain name replacement is performed on the response information to obtain https:// svsvsvsvvhttp-h 1-test-web-com- -p8000.Vpn.com/uri _ test1, https is new request protocol information added, and. Vpn.com is domain name tail identification information added.
When the response information is https:// test.web2.Com:8888/uri _ test2, performing domain name replacement on the response information to obtain https:// svsvsvshttps-test-web 2-com-p 8888.Vpn.com/uri _ test2, if https is added new request protocol information, and. Vpn.com is added domain name tail identification information.
In other embodiments provided by the present invention, the response information after the domain name replacement is obtained includes,
and combining the processed protocol information segment and the domain name information segment, the processed port information segment, the domain name identification information and the URI information segment to obtain response information after domain name replacement.
In this embodiment, if the response information after the domain name replacement is to be obtained, the processed protocol information segment and the domain name information segment, the processed port information segment, the domain name identification information, and the URI information segment need to be combined.
When the response information is http:// h1.Test.web.com:8000/URI _ test1, processing the protocol information segment and the domain name information segment to obtain svsvvhttp-h 1-test-web-com, processing the port information segment to obtain-p 8000, the domain name identification information is https and vpn.com, the URI information segment is URI _ test1, combining the processed protocol information segment and the domain name information segment, the processed port information segment, the domain name identification information and the URI information segment, namely combining svvhttp-h 1-test-web-com, - -p8000, https, vvpt.com and URI _ test1 to obtain the response information after domain name replacement, namely obtaining https:// svvhttp-h 1-test-web-p 8000.8000/URI _ test1.
When the response information is https:// test.web2.Com:8888/URI _ test2, processing the protocol information section and the domain name information section to obtain svsvvhttps-test-web 2-com, processing the port information section to obtain-p 8888, and combining the processed protocol information section, the domain name information section, the processed port information section, the domain name identification information and the URI information section, namely combining svvhttps-test-web 2-com, - -p8888, https, vvcom and URI _ test2 to obtain the response information after domain name replacement, namely obtaining https:// svhtttttttttst-test-web 2-p-com-p 8888-pvtest.88.
The above embodiments are only exemplary embodiments of the present invention, and are not intended to limit the present invention, and the scope of the present invention is defined by the claims. Various modifications and equivalents of the invention may be made by those skilled in the art within the spirit and scope of the invention, and such modifications and equivalents should also be considered as falling within the scope of the invention.
Claims (7)
1. A method of converting a domain name, the method comprising,
receiving a request message initiated by a user browser;
analyzing the domain name information of the request message;
sending the resolved domain name information to a WEB server;
obtaining response information based on the response of the WEB server to the analyzed domain name information, and performing domain name replacement on the response information, wherein the number of the response information is one or more;
sending the response information after domain name replacement to a user browser so that a user can normally access the browser;
the performing domain name replacement on the response information comprises,
carrying out segmentation processing on the response information to obtain different response information segments; the response information segment comprises a protocol information segment, a domain name information segment, a port information segment and a URI information segment;
processing the different response information segments respectively to finish domain name replacement of the response information;
the processing the different response information segments respectively comprises,
processing the protocol information segment and the domain name information segment;
processing the port information segment;
adding domain name identification information;
maintaining the URI information segment;
and obtaining response information after domain name replacement.
2. The method of claim 1, wherein the parsing the domain name information of the request packet comprises,
acquiring domain name information in the request message;
and analyzing the domain name information.
3. The method according to claim 2, wherein the resolving the domain name information comprises,
removing the tail part of the domain name information;
acquiring port information;
acquiring protocol information;
acquiring a target domain name;
and obtaining the resolved domain name information.
4. The method according to claim 3, wherein obtaining the target domain name comprises,
acquiring an initial domain name;
and converting the initial domain name to obtain the target domain name.
5. The method of claim 3, wherein the obtaining the resolved domain name information comprises,
and combining the port information, the protocol information and the target domain name to obtain the analyzed domain name information.
6. The method according to claim 1, wherein the adding the domain name identification information comprises adding new request protocol information and domain name tail identification information.
7. The method of claim 1, wherein obtaining the response information after the domain name replacement comprises,
and combining the processed protocol information segment and the domain name information segment, the processed port information segment, the domain name identification information and the URI information segment to obtain the response information after domain name replacement.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911005736.7A CN110602269B (en) | 2019-10-22 | 2019-10-22 | Method for converting domain name |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911005736.7A CN110602269B (en) | 2019-10-22 | 2019-10-22 | Method for converting domain name |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110602269A CN110602269A (en) | 2019-12-20 |
| CN110602269B true CN110602269B (en) | 2022-10-21 |
Family
ID=68851307
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911005736.7A Active CN110602269B (en) | 2019-10-22 | 2019-10-22 | Method for converting domain name |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110602269B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111901218A (en) * | 2020-06-23 | 2020-11-06 | 北京天融信网络安全技术有限公司 | Message transmission method, SSLVPN proxy server, electronic device and storage medium |
| CN112054994B (en) * | 2020-08-04 | 2022-11-11 | 上海人云科技有限公司 | Robot access address encryption method, robot access method and device |
| CN112272158A (en) * | 2020-09-16 | 2021-01-26 | 厦门网宿有限公司 | Data proxy method, system and proxy server |
| CN112260991B (en) * | 2020-09-16 | 2023-08-22 | 厦门网宿有限公司 | Authentication management method and device |
| CN114205652B (en) * | 2020-09-18 | 2024-05-31 | 腾讯科技（深圳）有限公司 | Media information processing method and device and computer equipment |
| CN112769835B (en) * | 2021-01-13 | 2023-04-18 | 网宿科技股份有限公司 | Method for initiating access request and terminal equipment |
| CN113194099B (en) * | 2021-04-30 | 2023-04-18 | 网宿科技股份有限公司 | Data proxy method and proxy server |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103067417A (en) * | 2011-10-19 | 2013-04-24 | 华耀(中国)科技有限公司 | Web service mapping method and system of security agent in virtual private network (VPN) |
| CN110266661A (en) * | 2019-06-04 | 2019-09-20 | 东软集团股份有限公司 | A kind of authorization method, device and equipment |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101981887B (en) * | 2008-01-26 | 2016-02-10 | 思杰系统有限公司 | For configuring the system and method driving WEB content to detect and rewrite with fine-grained policy |
| US20180191856A1 (en) * | 2016-12-29 | 2018-07-05 | Synology Inc. | Cross-domain communication methods and proxy servers using the same |
| US10812448B2 (en) * | 2018-01-26 | 2020-10-20 | Citrix Systems, Inc. | Split-tunneling for clientless SSL-VPN sessions with zero-configuration |
-
2019
- 2019-10-22 CN CN201911005736.7A patent/CN110602269B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103067417A (en) * | 2011-10-19 | 2013-04-24 | 华耀(中国)科技有限公司 | Web service mapping method and system of security agent in virtual private network (VPN) |
| CN110266661A (en) * | 2019-06-04 | 2019-09-20 | 东软集团股份有限公司 | A kind of authorization method, device and equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110602269A (en) | 2019-12-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110602269B (en) | Method for converting domain name | |
| US7739354B2 (en) | Adding data to text pages by means of an intermediary proxy | |
| US6892231B2 (en) | Method and apparatus for verifying the contents of a global configuration file | |
| US8321503B2 (en) | Context-specific network resource addressing model for distributed services | |
| US10164961B2 (en) | Dynamic web services server | |
| CN110392130B (en) | Information processing method based on network, electronic equipment and network system | |
| EP2482517B1 (en) | Method, apparatus and system for protocol identification | |
| WO2013143403A1 (en) | Method and system for accessing website | |
| CN104102577B (en) | Multi version web page access method of testing | |
| CN103338236B (en) | A kind of concurrent data acquisition methods and system | |
| CN104021154B (en) | A kind of method and apparatus scanned in a browser | |
| CN109905288A (en) | A kind of application service classification method and device | |
| CN108595468A (en) | A kind of acquisition methods of web data, device, server, terminal and system | |
| CN109756584B (en) | Domain name resolution method, domain name resolution device and computer readable storage medium | |
| CN110855766A (en) | Method and device for accessing Web resources and proxy server | |
| CN105635064A (en) | CSRF attack detection method and device | |
| US20210406217A1 (en) | Method for processing resource description file, page resource acquisition method, and intermediate server | |
| CN111901218A (en) | Message transmission method, SSLVPN proxy server, electronic device and storage medium | |
| US9785721B2 (en) | System and method for programmatically creating resource locators | |
| CN103825772A (en) | Method for identifying user click behavior and gateway equipment | |
| CN104023046A (en) | Mobile terminal recognition method and device | |
| NL2006294C2 (en) | Website translator, system, and method. | |
| CN113055420B (en) | HTTPS service identification method and device and computing equipment | |
| US9866614B2 (en) | Methods for website version control using bucket cookies | |
| CN105635225A (en) | Method and system of using mobile terminal to access mobile internet-based server and mobile terminal |
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 |