CN109862130B - Method, device, equipment and computer medium for accessing IPv4 external link - Google Patents
Method, device, equipment and computer medium for accessing IPv4 external link Download PDFInfo
- Publication number
- CN109862130B CN109862130B CN201910120432.9A CN201910120432A CN109862130B CN 109862130 B CN109862130 B CN 109862130B CN 201910120432 A CN201910120432 A CN 201910120432A CN 109862130 B CN109862130 B CN 109862130B
- Authority
- CN
- China
- Prior art keywords
- url
- ipv4
- link
- nat64 gateway
- target
- 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
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application discloses a method, a device, equipment and a computer medium for accessing an IPv4 external link, wherein when the method is applied to an IPv6 client, the method comprises the following steps: acquiring a URL of a target IPv4 external link, wherein the URL of the target IPv4 external link consists of a NAT64 gateway diversion identifier and a URL of an initial IPv4 external link; based on the NAT64 gateway diversion identification, the URL of the target IPv4 outer chain is diverted to the NAT64 gateway; and receiving data information sent by the NAT64 gateway after accessing the URL of the initial IPv4 external link. The IPv4 out-link access method, device and equipment and the computer readable storage medium disclosed by the application have high applicability.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method, an apparatus, a device, and a computer medium for accessing an IPv4 out-link.
Background
In the transition process from IPv4 to IPv6, when an IPv6 client browser accesses a legacy Web service system (such as an IPv4 out-link website) through a Web application proxy supporting dual stack (hereinafter, such a Web application proxy using dual stack is referred to as NAT64 gateway), an IPv6 skylight problem may be encountered, which is described as follows: when an IPv6 client accesses an IPv4 host website located behind a NAT64 gateway, if a web page of an IPv4 host website carries an IPv4 out-link URL (i.e., a web page resource that does not belong to the host website and can be normally accessed only by using an IPv4 protocol, such as a picture, an audio, or a web page subframe located on another website), when the web page reaches an IPv6 client for rendering, the IPv6 client directly accesses the IPv4 out-link URL by using an IPv6 protocol, because the access of the IPv6 client to the web page resource corresponding to the IPv4 out-link URL does not pass through a NAT64 gateway under normal conditions, the IPv4 out-link URL is not reachable to the IPv6 client, and therefore, the web page content corresponding to the IPv4 out-link URL cannot be normally displayed on an IPv6 client browser, which is a so-called IPv6 skylight.
In order to solve the problem of the IPv6 skylight, the prior art scheme is: at the NAT64 gateway, when the NAT64 gateway forwards the host website web page, all IPv4 out-link URLs in the host website web page are modified so that access to the IPv4 out-link URLs must pass through the NAT64 gateway so that the IPv4 out-link URLs remain accessible to the IPv6 client. The specific IPV4 external link URL modification method of the NAT64 gateway is as follows: adding an IPv6 sub-domain name to DNS in an IPV4 external link URL, then adding a DNS-IPv6 analysis record on an authoritative DNS server, so that all analysis results aiming at the IPv6 sub-domain name are analyzed to be IPv6 addresses of a NAT64 gateway, therefore, when the IPv6 client side renders main website webpage content, the access to the IPv4 external link URL added with the IPv6 sub-domain name is guided to the NAT64 gateway, the NAT64 gateway can intercept the IPv4 external link URL access request, a real IPv4 domain name is cut out through a HOST domain in an HTTP request head (the added IPv6 sub-domain name is discarded), then carrying out IPv4DNS analysis on the IPv4 external link URL access request to obtain an IPV4 address of an external link website, the NAT64 gateway proxies an IPv6 client side, the webpage content corresponding to the IPv4 external link URL through an IPv4 protocol, and finally forwarding the obtained webpage content to the IPv6 through an IPv6 connection, thereby solving the problem of skylight 6.
However, in the existing technology for solving the IPv6 skylight problem, AAAA records need to be added for the virtual IPv6 sub-domain on the authoritative DNS server, deployment is complex, and hijacking the IPv6 sub-domain affects use of the IPv6 sub-domain, so that the applicability of the prior art is poor.
In summary, a problem to be solved urgently by those skilled in the art is how to provide an IPv6 skylight solution with simple deployment and good applicability.
Disclosure of Invention
The application aims to provide a method for accessing an IPv4 external link, which can solve the technical problem of providing a skylight solution with good applicability to a certain extent. The application also provides an IPv4 out-link access device, equipment and a computer readable storage medium.
In order to achieve the above purpose, the present application provides the following technical solutions:
a method for accessing IPv4 external links, which is applied to an IPv6 client, and comprises the following steps:
acquiring a URL of a target IPv4 external link, wherein the URL of the target IPv4 external link consists of a NAT64 gateway diversion identifier and a URL of an initial IPv4 external link;
based on the NAT64 gateway flow identification, the URL of the target IPv4 outer chain is led to a NAT64 gateway;
and receiving data information sent by the NAT64 gateway after accessing the URL of the target IPv4 external link.
Preferably, the generating of the URL of the target IPv4 external link by the NAT64 gateway, and the obtaining of the URL of the target IPv4 external link includes:
and receiving the URL of the target IPv4 external link sent by the NAT64 gateway.
Preferably, the URL of the target IPv4 foreign chain is generated by the IPv6 client, and the obtaining the URL of the target IPv4 foreign chain includes:
receiving a webpage sent by the NAT64 gateway, wherein the webpage carries the URL and the browser script of the initial IPv4 external link;
traversing out the URL of the initial IPv4 external link carried in the webpage based on the browser script;
and combining the URL of the initial IPv4 external chain and the NAT64 gateway flow guiding identifier into the URL of the target IPv4 external chain.
Preferably, the receiving the web page sent by the NAT64 gateway includes:
receiving the cached webpage sent by the NAT64 gateway;
wherein, the process that the NAT64 gateway sends the webpage includes:
caching the webpage which is sent to the IPv6 client at the last time and carries the URL and the browser script of the initial IPv4 external link;
receiving a request for requesting website data information of an IPv4 host website sent by the IPv6 client;
and judging whether the webpage is matched with the request or not, and if so, sending the webpage to the IPv6 client.
Preferably, a preset external chain identifier is added between the NAT64 gateway diversion identifier and the URL of the initial IPv4 external chain.
Preferably, the diversion of the URL of the target IPv4 out-link to the NAT64 gateway based on the NAT64 gateway diversion identifier includes:
and guiding the URL of the target IPv4 external chain to a NAT64 gateway based on the NAT64 gateway guide identification through an SSL protocol.
Preferably, the receiving the data information sent by the NAT64 gateway after accessing the URL of the initial IPv4 external link includes:
and receiving data information sent after the NAT64 gateway accesses the URL of the initial IPv4 external chain through an SSL protocol.
Preferably, the NAT64 gateway flow identifier precedes the URL of the initial IPv4 out-link.
Preferably, the NAT64 gateway flow guide identifier includes a DNS domain name of the IPv4 website.
Preferably, the NAT64 gateway flow guide identifier includes an IP address of the NAT64 gateway.
A method for accessing IPv4 external links, which is applied to a NAT64 gateway, and comprises the following steps:
receiving a request of an IPv6 client for accessing a URL of a target IPv4 outer chain, wherein the URL of the target IPv4 outer chain consists of a NAT64 gateway diversion identifier and a URL of an initial IPv4 outer chain;
and accessing the URL of the initial IPv4 external chain, and sending a result of accessing the URL of the initial IPv4 external chain to the IPv6 client.
Preferably, before the receiving the request of the IPv6 client for accessing the URL of the target IPv4 out-link, the method further includes:
and generating the URL of the target IPv4 external link, and sending the URL of the target IPv4 external link to the IPv6 client.
Preferably, the generating the URL of the target IPv4 out-link and sending the URL of the target IPv4 out-link to the IPv6 client includes:
generating a URL of the target IPv4 outer chain, and encrypting the URL of the target IPv4 outer chain;
and sending the encrypted URL of the target IPv4 external link to the IPv6 client.
Preferably, the generating the URL of the target IPv4 out-link and sending the URL of the target IPv4 out-link to the IPv6 client includes:
generating a URL of the target IPv4 outer chain;
adding a timestamp in the URL of the target IPv4 outer chain;
encrypting the URL of the initial IPv4 out-link and the timestamp;
and sending the encrypted URL of the target IPv4 external link to the IPv6 client.
Preferably, before the receiving the request of the IPv6 client for accessing the URL of the target IPv4 out-link, the method further includes:
and sending a webpage carrying a browser script and the URL of the initial IPv4 external link to the IPv6 client, so that the IPv6 client generates the URL of the target IPv4 external link.
Preferably, the receiving the request of the IPv6 client to access the URL of the target IPv4 out-link includes:
and receiving a request sent by the IPv6 client through an SSL protocol for accessing the URL of the target IPv4 external chain.
Preferably, the accessing the URL of the initial IPv4 out-link includes:
and accessing the URL of the initial IPv4 external chain based on an SSL protocol.
Preferably, the NAT64 gateway flow identifier precedes the URL of the initial IPv4 out-link.
Preferably, the NAT64 gateway flow guide identifier includes a DNS domain name of the IPv4 website.
Preferably, the NAT64 gateway flow guide identifier includes an IP address of the NAT64 gateway.
An IPv4 external link access device applied to an IPv6 client, comprising:
the first acquisition module is used for acquiring the URL of a target IPv4 external link, wherein the URL of the target IPv4 external link consists of a NAT64 gateway diversion identifier and the URL of an initial IPv4 external link;
a first diversion module, configured to divert, based on the NAT64 gateway diversion identity, the URL of the target IPv4 out-link to a NAT64 gateway;
a first receiving module, configured to receive data information sent by the NAT64 gateway after accessing the URL of the initial IPv4 external link.
An IPv4 external link access device applied to an IPv6 client comprises the following steps:
a memory for storing a computer program;
a processor for implementing the steps of any of the above described methods for accessing an IPv4 out-link when executing the computer program.
A computer readable storage medium for use in an IPv6 client, the computer readable storage medium having stored thereon a computer program which, when executed by a processor, carries out the steps of accessing an IPv4 out-link method as claimed in any preceding claim.
The method for accessing the IPv4 outer link is applied to an IPv6 client, and is used for obtaining the URL of a target IPv4 outer link, wherein the URL of the target IPv4 outer link consists of a NAT64 gateway diversion identifier and the URL of an initial IPv4 outer link; based on the NAT64 gateway flow identification, the URL of the target IPv4 outer chain is led to the NAT64 gateway; and receiving data information sent by the NAT64 gateway after accessing the URL of the initial IPv4 external link. According to the method for accessing the IPv4 outer chain, only the NAT64 gateway diversion identification is needed, the IPv6 client can divert the URL of the target IPv4 outer chain to the NAT64 gateway, the NAT64 gateway is used for obtaining the outer chain data information in the URL of the initial IPv4 outer chain, the IPv6 client does not need to directly access the URL of the initial IPv4 outer chain, and therefore the situation that the outer chain data information cannot be obtained and a skylight appears when the IPv6 client directly accesses the URL of the initial IPv4 outer chain is avoided. The device, the equipment and the computer readable storage medium for accessing the IPv4 external link also solve the corresponding technical problems.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a first flowchart of a method for accessing an IPv4 out-link according to an embodiment of the present application;
fig. 2 is a second flowchart of a method for accessing an IPv4 out-link according to an embodiment of the present application;
fig. 3 is a third flowchart of a method for accessing an IPv4 out-link according to an embodiment of the present application;
fig. 4 is a first structural diagram of an IPv4 out-link access device according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of an IPv4 out-link access device according to an embodiment of the present application;
fig. 6 is another schematic structural diagram of an apparatus for accessing an IPv4 external link according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a first flowchart of a method for accessing an IPv4 out-link according to an embodiment of the present application.
The method for accessing the IPv4 external link, which is provided by the embodiment of the application, is applied to an IPv6 client and can comprise the following steps:
step S101: and acquiring the URL of the target IPv4 external link, wherein the URL of the target IPv4 external link consists of a NAT64 gateway flow guide identifier and the URL of the initial IPv4 external link.
In practical application, the IPv6 client may obtain a URL of a target IPv4 outer chain added with the NAT64 gateway diversion identifier, where the target IPv4 outer chain refers to an outer chain composed of the NAT64 gateway diversion identifier and the URL of the initial IPv4 outer chain, the NAT64 gateway diversion identifier may be before the URL of the initial IPv4 outer chain, or may be after the URL of the initial IPv4 outer chain, and a location relationship between the NAT64 gateway diversion identifier and the URL of the target IPv4 outer chain is not specifically limited. The initial IPv4 outer chain refers to an IPv4 outer chain carried in an IPv4 host website accessed by the IPv6 client, and the IPv4 host website refers to an IPv4 website accessed by the IPv6 client for the first time. The role of the NAT64 gateway diversion identity is to cause the IPv6 client to divert the URL of the target IPv4 out-link to the NAT64 gateway.
In a specific application scenario, the NAT64 gateway diversion identifier may be a DNS domain name of an IPv4 website, for example, the DNS domain name of an IPv4 host website, a DNS domain name of an IPv4 external link website, and the like. Specifically, the DNS domain name of the IPv4 website may be added before the URL of the initial IPv4 out-link, taking the initial IPv4 out-link as:
for example, if the DNS domain name of the IPv4 website is www.abc.com, the < a href ═ http:// www.sohu.com/a. html' >, the target IPv4 outer link may be:
<a href＝“http://www.abc.com/http/www.sohu.com/a.html”>。
in a specific application scenario, the NAT64 gateway diversion identifier may also be an IP address of the NAT64 gateway, or the like.
In a specific application scenario, the URL of the target IPv4 outer link may be generated by the NAT64 gateway, and when the NAT64 gateway flow identifier is the DNS domain name of the IPv4 website or the IP address of the NAT64 gateway, the step of obtaining the URL of the target IPv4 outer link may specifically be: and receiving the URL of the target IPv4 external link sent by the NAT64 gateway. The process of the NAT64 gateway generating the URL of the target IPv4 out-link may be: the NAT64 gateway combines the obtained URL of the initial IPv4 out-link and the NAT64 gateway diversion identity into the URL of the target IPv4 out-link, and the NAT64 gateway diversion identity may precede the URL of the initial IPv4 out-link.
Specifically, because the NAT64 gateway is used as a jumper for the IPv6 client to access the initial IPv4 outer chain, the initial IPv4 outer chain is easily attacked by the outside, and in order to ensure the security of the initial IPv4 outer chain, the URL of the initial IPv4 outer chain may be encrypted, and when the NAT64 gateway flows the DNS domain name identified as the IPv4 website, the process of receiving the URL of the target IPv4 outer chain sent by the NAT64 gateway may specifically be: and receiving the encrypted URL of the target IPv4 external link sent by the NAT64 gateway. The process of the NAT64 gateway encrypting the URL of the target IPv4 out-link may be: and the NAT64 gateway encrypts the URL of the initial IPv4 out-link in the target IPv4 out-link URL based on the generated encryption key to obtain the encrypted target IPv4 out-link URL. Specifically, the encryption key may be an encryption key randomly generated by the NAT64 gateway, for example, each time the NAT64 gateway starts, the NAT64 gateway automatically generates an encryption key, and the like.
Specifically, in order to further ensure the security of the target IPv4 outer link, the NAT64 gateway may add a timestamp to the URL of the target IPv4 outer link, then encrypt the URL of the target IPv4 outer link to which the timestamp is added, for example, encrypt the timestamp and the URL of the initial IPv4 outer link based on the generated encryption key, to obtain an encrypted URL of the target IPv4 outer link, and then the NAT64 gateway sends the encrypted URL of the target IPv4 outer link to the IPv6 client. Specifically, the timestamp may be added after the URL of the initial IPv4 out-link in the URL of the target IPv4 out-link, for example, the target IPv4 out-link is:
https:// www.abc.com/https/www.def.com/a. html, the target IPv4 outer chain with the timestamp added can be:
https:// www.abc.com/https/www.sohu.com/a. html #20181031123506, the result of encrypting the target IPv4 outer chain added with the timestamp can be:
https://www.abc.com/aebeedeb85de9be97fb85b7d7b6e9v7ev。
in a specific application scenario, if the NAT64 gateway generates the target IPv4 external link, the service pressure of the NAT64 gateway will be increased, and some URLs of the initial IPv4 out-links may be contained in the browser script, the NAT64 gateway may not be able to find the URL of the initial IPv4 out-link in the browser script by means of static rule matching, the number of target IPv4 external chains generated by the NAT64 gateway is not thorough, and in order to reduce the service pressure of the NAT64 gateway, and ensures that each target IPv4 foreign link can be traversed, the NAT64 gateway can rewrite the browser script, and sends the browser script to the IPv6 client, so that the IPv6 client traverses all target IPv4 outer chains based on the browser script, then when the NAT64 gateway diverts the DNS domain name identified as the IPv4 website or the IP address of the NAT64 gateway, the URL of the target IPv4 external link may be generated by the IPv6 client, and the process of obtaining the URL of the target IPv4 external link may specifically be: receiving a webpage sent by a NAT64 gateway, wherein the webpage carries a URL (uniform resource locator) and a browser script of an initial IPv4 external link; traversing the URL of the initial IPv4 external link carried in the webpage based on the browser script; and combining the URL of the initial IPv4 external chain and the NAT64 gateway flow guiding identification into the URL of the target IPv4 external chain. In practical application, the browser script may be javascript, VBscript, or the like.
Specifically, in an actual application scenario, there is a case that the IPv6 client accesses the initial IPv4 outer link for multiple times in a short time, in this case, if the IPv6 client re-acquires the target IPv4 outer link every time the IPv4 outer link is accessed, the process is tedious and meaningless, to avoid this, a cache technology may be used to store the target IPv4 outer link, and when the NAT64 gateway diversion identifier is the DNS domain name of the IPv4 website, the process of receiving the web page sent by the NAT64 gateway may specifically be: receiving a cached webpage sent by the NAT64 gateway; the process of sending the webpage by the NAT64 gateway comprises the following steps: caching a webpage which is sent to an IPv6 client at the last time and carries the URL and the browser script of an initial IPv4 external link; receiving a request for requesting website data information of an IPv4 host website sent by an IPv6 client; and judging whether the webpage is matched with the request, if so, sending the webpage to the IPv6 client. That is, when the target IPv4 external link accessed by the IPv6 client for multiple times is not changed, the IPv6 client may directly receive the URL of the target IPv4 external link cached by the NAT64 gateway. In addition, when the conditions allow, the NAT64 gateway may also cache the out-link data information obtained from the URL of the initial IPv4 out-link, and when the URL of the target IPv4 out-link that the IPv6 client has navigated to the NAT64 gateway is not changed, the NAT64 gateway directly sends the cached out-link data information to the IPv6 client, and the like.
Specifically, in order to avoid external cracking of the browser script sent by the NAT64 gateway to the IPv6 client, ensure the security of the IPv6 client and the NAT64 gateway, and receive the web page sent by the NAT64 gateway, the process in which the web page carries the URL of the initial IPv4 external link and the browser script may specifically be: and receiving a webpage sent by the NAT64 webpage, wherein the webpage carries the URL of the initial IPv4 out-link and a code-obfuscated browser script.
In a specific application scenario, in order to facilitate the NAT64 gateway to distinguish the IPv4 host website from the target IPv4 outer chain, and improve the efficiency of the NAT64 gateway in distinguishing the IPv4 host website from the target IPv4 outer chain, an outer chain identifier may be added to the target IPv4 outer chain to inform that the IPv4 address containing the outer chain identifier is the target IPv4 outer chain, and when the NAT64 gateway diversion identifier is the DNS domain name of the IPv4 website or the IP address of the NAT64 gateway, a preset outer chain identifier may be added between the NAT64 gateway diversion identifier and the URL of the initial IPv4 outer chain. Specifically, the external link identifier may be added between the URL of the NAT64 gateway diversion identifier in the target IPv4 external link and the initial IPv4 external link, for example, the NAT64 gateway diversion identifier is a DNS domain name of the IPv4 website, and the initial IPv4 external link is:
if the < a href ═ http:// www.sohu.com/a. html' >, the DNS domain name of the IPv4 website is www.abc.com, and the out-link identifier is SPECIALSTR, then the target IPv4 out-link may be:
<a href＝“http://www.abc.com/SPECIALSTR/http/www.sohu.com/a.html”>。
in a specific application scenario, when an IPv6 client accesses an initial IPv4 outer chain, the IPv4 host website may be accessed first, and in the specific application scenario, before acquiring a URL of a target IPv4 outer chain, the IPv6 client may also send a request for resolving a DNS domain name of the IPv4 host website to a DNS of the IPv6 client, receive an address of a NAT64 gateway returned by a DNS of the IPv6 client, establish a communication connection with a NAT64 gateway, such as an HTTP connection, and send a request for accessing the IPv4 host website to a NAT64 gateway; correspondingly, the NAT64 gateway establishes communication connection with the IPv4 main website, acquires data information on the IPv4 main website and returns the data information to the IPv6 client. The NAT64 gateway may be a Web gateway, a WAF, an AD (Application Delivery), or the like.
Step S102: and guiding the URL of the target IPv4 external chain to the NAT64 gateway based on the NAT64 gateway flow identification.
In practical application, after the IPv6 client acquires the URL of the target IPv4 outer chain, when acquiring the outer chain data information of the URL of the initial IPv4 outer chain, due to the existence of the NAT64 gateway diversion identifier, the IPv6 client diverts the URL of the target IPv4 outer chain to the NAT64 gateway. In the process, if the IPv6 client has established a connection with the NAT64 gateway, the URL of the target IPv4 outer chain may be directly guided to the NAT64 gateway, and if the IPv6 client does not establish a connection with the NAT64 gateway, the IPv6 client may initiate, for the outer chain is located on the host website, an IPv6 address resolution for the DNS of the host website first, so as to obtain the IPv6 address of the NAT64 gateway, and implement guiding the traffic of the URL accessing the target IPv4 outer chain to the NAT64 gateway.
Step S103: and receiving data information sent by the NAT64 gateway after accessing the URL of the initial IPv4 external link.
In practical application, the IPv6 client guides the URL of the target IPv4 external link to the NAT64 gateway; after receiving the URL of the target IPv4 outer chain, the NAT64 gateway can analyze the URL of the initial IPv4 outer chain from the URL of the target IPv4 outer chain, access the URL of the initial IPv4 outer chain and acquire data information in the URL of the initial IPv4 outer chain, and then the NAT64 gateway transmits the acquired data information to the IPv6 client; accordingly, the IPv6 client receives the data message sent by the NAT64 gateway.
In a specific application scenario, in order to ensure the communication security between the IPv6 client and the NAT64 gateway, when the NAT64 gateway supports SSL (Secure Sockets Layer) offload, the communication connection between the IPv6 client and the NAT64 gateway may be protected by SSL, and a process of guiding a URL of a target IPv4 outer link to the NAT64 gateway based on the NAT64 gateway guide identifier may specifically be: the URL of the target IPv4 external chain is guided to the NAT64 gateway based on the NAT64 gateway guide identification through the SSL protocol; correspondingly, the process of receiving the out-link data information sent by the NAT64 gateway after accessing the URL of the initial IPv4 out-link may specifically be: and receiving the external link data information sent by the NAT64 gateway after accessing the URL of the initial IPv4 external link through the SSL protocol. Specifically, in order to ensure the security of the communication connection between the NAT64 gateway and the initial IPv4 foreign link, the communication connection between the NAT64 gateway and the initial IPv4 foreign link may also be protected by using the SSL protocol, and the process of receiving the data information sent by the NAT64 gateway after accessing the URL of the initial IPv4 foreign link may specifically be: and receiving data information sent by the NAT64 gateway after accessing the URL of the initial IPv4 external chain through the SSL protocol.
The method for accessing the IPv4 outer chain is applied to an IPv6 client, and is used for obtaining the URL of a target IPv4 outer chain, wherein the URL of the target IPv4 outer chain consists of a NAT64 gateway diversion identifier and the URL of an initial IPv4 outer chain; based on the NAT64 gateway diversion identification, the URL of the target IPv4 outer chain is diverted to the NAT64 gateway; and receiving data information sent by the NAT64 gateway after accessing the URL of the initial IPv4 external link. According to the method for accessing the IPv4 outer chain, only the NAT64 gateway diversion identification is needed, the IPv6 client can divert the URL of the target IPv4 outer chain to the NAT64 gateway, the NAT64 gateway is used for obtaining the outer chain data information in the URL of the initial IPv4 outer chain, the IPv6 client does not need to directly access the URL of the initial IPv4 outer chain, and therefore the situation that the outer chain data information cannot be obtained and a skylight appears when the IPv6 client directly accesses the URL of the initial IPv4 outer chain is avoided.
Referring to fig. 2, fig. 2 is a second flowchart of a method for accessing an IPv4 out-link according to an embodiment of the present application.
The method for accessing the IPv4 external link, provided by the embodiment of the application, is applied to the NAT64 gateway, and comprises the following steps:
step S201: and receiving a request of the IPv6 client for accessing the URL of the target IPv4 external chain, wherein the URL of the target IPv4 external chain consists of the NAT64 gateway diversion identifier and the URL of the initial IPv4 external chain.
Step S202: and accessing the URL of the initial IPv4 external chain, and sending a result of accessing the URL of the initial IPv4 external chain to the IPv6 client.
For the related description in this embodiment, reference may be made to the corresponding description in the above embodiments, which is not repeated herein.
In the embodiment shown in fig. 2, when the NAT64 gateway flow is identified as the DNS domain name of the IPv4 website or the IP address of the NAT64 gateway, before the NAT64 gateway receives a request from the IPv6 client to access the URL of the target IPv4 outer chain, the URL of the target IPv4 outer chain may also be generated, and the URL of the target IPv4 outer chain is sent to the IPv6 client. That is, the URL of the target IPv4 external link is generated by the NAT64 gateway, and accordingly, the IPv6 client receives the URL of the target IPv4 external link sent by the NAT64 gateway.
In the embodiment shown in fig. 2, when the NAT64 gateway flow is identified as the DNS domain name of the IPv4 website, the process of the NAT64 gateway generating the URL of the target IPv4 external link and sending the URL of the target IPv4 external link to the IPv6 client may specifically be: generating a URL of a target IPv4 external link, and encrypting the URL of the target IPv4 external link; and sending the encrypted URL of the target IPv4 external link to the IPv6 client.
In the embodiment shown in fig. 2, when the NAT64 gateway flow is identified as the DNS domain name of the IPv4 website, the process of the NAT64 gateway generating the URL of the target IPv4 external link and sending the URL of the target IPv4 external link to the IPv6 client may specifically be: generating a URL of a target IPv4 outer chain; adding a time stamp to the URL of the target IPv4 outer chain; encrypting the URL and timestamp of the initial IPv4 outer chain; and sending the encrypted URL of the target IPv4 external link to the IPv6 client.
In the embodiment shown in fig. 2, when the NAT64 gateway flow is identified as the DNS domain name of the IPv4 website or the IP address of the NAT64 gateway, the NAT64 gateway may further send a web page carrying a browser script and the URL of the initial IPv4 out-link to the IPv6 client before receiving a request for the IPv6 client to access the URL of the target IPv4 out-link, so that the IPv6 client generates the URL of the target IPv4 out-link.
In the embodiment shown in fig. 2, when the NAT64 gateway diversion is identified as the DNS domain name of the IPv4 website or the IP address of the NAT64 gateway, the process of the NAT64 gateway receiving the request of the IPv6 client to access the URL of the target IPv4 outer chain may specifically be: and receiving a request sent by the IPv6 client through the SSL protocol for accessing the URL of the target IPv4 external chain.
In the embodiment shown in fig. 2, when the NAT64 gateway flow is identified as the DNS domain name of the IPv4 website or the IP address of the NAT64 gateway, the process of the NAT64 gateway accessing the URL of the initial IPv4 external link may specifically be: the URL of the initial IPv4 out-link is accessed based on the SSL protocol.
In the embodiment shown in fig. 2, when the NAT64 gateway diversion is identified as the DNS domain name of the IPv4 website or the IP address of the NAT64 gateway, the NAT64 gateway diversion identification may precede the URL of the initial IPv4 out-link.
Referring to fig. 3, fig. 3 is a third flowchart of a method for accessing an IPv4 out-link according to an embodiment of the present application.
In practical applications, the method for accessing an IPv4 external link provided in the embodiment of the present application may include the following steps:
step S301: the IPv6 client sends a request to the DNS of the IPv6 client to resolve the DNS domain name of the IPv4 host website.
Step S302: the DNS of the IPv6 client returns the address of the NAT64 gateway to the IPv6 client.
Step S303: the IPv6 client establishes a communication connection with the NAT64 gateway and sends a request for accessing the IPv4 host website to the NAT64 gateway.
Step S304: the NAT64 gateway establishes a communication connection with the IPv4 host network station.
Step S305: the NAT64 gateway accesses the IPv4 host website to obtain the URL of the initial IPv4 external chain carried in the IPv4 host website.
Step S306: the NAT64 gateway adds the DNS domain name of the IPv4 website before the URL of the initial IPv4 external chain, obtains the URL of the target IPv4 external chain, and returns the URL of the target IPv4 external chain to the IPv6 client.
Step S307: the IPv6 client renders IPv4 main website webpage content and acquires data information of a target IPv4 external link.
Step S308: the IPv6 client sends a request to the NAT64 gateway to access the URL of the target IPv4 out-link.
Step S309: the NAT64 gateway judges the target IPv4 external link to be an external link website based on the DNS domain name of the IPv4 website, and analyzes the URL of the initial IPv4 external link in the URL of the target IPv4 external link.
Step S310: the NAT64 gateway analyzes the DNS of the IPv4 main website to obtain the DNS domain name of the initial IPv4 external chain, and data information is obtained based on the DNS domain name of the initial IPv4 external chain.
Step S311: the NAT64 gateway returns data information to the IPv6 client.
Step S312: the IPv6 client combines the web page content and data information of the IPv4 host website to display the final web page.
The application also provides an IPv4 external link accessing device which has the corresponding effect of the IPv4 external link accessing method provided by the embodiment of the application. Referring to fig. 4, fig. 4 is a first structural diagram of an IPv4 external link access device according to an embodiment of the present application.
The IPv4 external link access device provided in the embodiment of the present application, which is applied to an IPv6 client, may include:
the first obtaining module 101 is configured to obtain a URL of a target IPv4 outer chain, where the URL of the target IPv4 outer chain is composed of a NAT64 gateway diversion identifier and a URL of an initial IPv4 outer chain;
the first diversion module 102 is configured to divert a URL of the target IPv4 out-link to a NAT64 gateway based on the NAT64 gateway diversion identifier;
the first receiving module 103 is configured to receive data information sent by the NAT64 gateway after accessing the URL of the initial IPv4 external link.
The IPv4 external link accessing device provided in the embodiment of the present application is applied to an IPv6 client, where a URL of a target IPv4 external link is generated by a NAT64 gateway, and the first obtaining module may include:
the first receiving unit is used for receiving the URL of the target IPv4 external link sent by the NAT64 gateway.
The IPv4 external link accessing device provided in the embodiment of the present application is applied to an IPv6 client, where a URL of a target IPv4 external link is generated by an IPv6 client, and the first obtaining module may include:
the second receiving unit is used for receiving a webpage sent by the NAT64 gateway, wherein the webpage carries the URL of the initial IPv4 external link and a browser script;
the first traversal unit is used for traversing the URL of the initial IPv4 external link carried in the webpage based on the browser script;
and the first combination unit is used for combining the URL of the initial IPv4 external chain and the NAT64 gateway flow guiding identifier into the URL of the target IPv4 external chain.
The IPv4 external link accessing device provided in the embodiment of the present application is applied to an IPv6 client, where the second receiving unit may include:
the first receiving subunit is configured to receive the cached web page sent by the NAT64 gateway;
the process of sending the webpage by the NAT64 gateway comprises the following steps:
caching a webpage which is sent to an IPv6 client at the last time and carries the URL and the browser script of an initial IPv4 external link;
receiving a request for requesting website data information of an IPv4 host website sent by an IPv6 client;
and judging whether the webpage is matched with the request, if so, sending the webpage to the IPv6 client.
The IPv4 external link access device provided by the embodiment of the application is applied to an IPv6 client, and a preset external link identifier is added between a NAT64 gateway diversion identifier and a URL (uniform resource locator) of an initial IPv4 external link.
The IPv4 external link access device provided in the embodiment of the present application is applied to an IPv6 client, where the first diversion module may include:
and the first diversion unit is used for diverting the URL of the target IPv4 external chain to the NAT64 gateway based on the NAT64 gateway diversion identification through the SSL protocol.
The device for accessing the IPv4 external link, provided by the embodiment of the present application, is applied to an IPv6 client, where the first receiving module may include:
and the third receiving unit is used for receiving the data information sent by the NAT64 gateway after accessing the URL of the initial IPv4 external link through the SSL protocol.
The device for accessing the IPv4 external link, provided by the embodiment of the application, is applied to an IPv6 client, and the NAT64 gateway flow identifier is in front of the URL of the initial IPv4 external link.
The IPv4 external link access device provided by the embodiment of the application is applied to an IPv6 client, and the NAT64 gateway flow guide identifier comprises a DNS domain name of an IPv4 website.
The IPv4 external link access device provided by the embodiment of the application is applied to an IPv6 client, and the NAT64 gateway flow guide identifier comprises an IP address of the NAT64 gateway.
The IPv4 external link access device provided in the embodiment of the present application, which is applied to a NAT64 gateway, may include:
the second receiving module is used for receiving a request of the IPv6 client for accessing the URL of the target IPv4 external chain, wherein the URL of the target IPv4 external chain consists of a NAT64 gateway diversion identifier and the URL of the initial IPv4 external chain;
and the first access module is used for accessing the URL of the initial IPv4 external chain and sending a result of accessing the URL of the initial IPv4 external chain to the IPv6 client.
The IPv4 external link access device provided in the embodiment of the present application is applied to a NAT64 gateway, and may further include:
and the first generating module is used for generating the URL of the target IPv4 external chain before the second receiving module receives the request of the IPv6 client for accessing the URL of the target IPv4 external chain, and sending the URL of the target IPv4 external chain to the IPv6 client.
The IPv4 external link access device provided in the embodiment of the present application is applied to a NAT64 gateway, and the first generation module may include:
a first generating unit, configured to generate a URL of the target IPv4 outer link and encrypt the URL of the target IPv4 outer link;
and the first sending unit is used for sending the encrypted URL of the target IPv4 out-link to the IPv6 client.
The IPv4 external link access device provided in the embodiment of the present application is applied to a NAT64 gateway, and the first generation module may include:
a second generation unit, configured to generate a URL of the target IPv4 out-link;
a first adding unit, which is used for adding a time stamp in the URL of the target IPv4 external chain;
a first encryption unit, configured to encrypt the URL and the timestamp of the initial IPv4 out-link;
and the second sending unit is used for sending the encrypted URL of the target IPv4 out-link to the IPv6 client.
The IPv4 external link access device provided in the embodiment of the present application is applied to a NAT64 gateway, and may further include:
the first sending module is used for sending the webpage carrying the browser script and the initial IPv4 outer chain URL to the IPv6 client before the second receiving module receives the request that the IPv6 client accesses the target IPv4 outer chain URL, so that the IPv6 client generates the target IPv4 outer chain URL.
The IPv4 external link access device provided in the embodiment of the present application is applied to a NAT64 gateway, and the second receiving module may include:
and the fourth receiving unit is used for receiving a request for accessing the URL of the target IPv4 external chain sent by the IPv6 client through the SSL protocol.
The IPv4 external link access device provided in the embodiment of the present application is applied to a NAT64 gateway, where the first access module may include:
and the first access unit is used for accessing the URL of the initial IPv4 external chain based on the SSL protocol.
The device for accessing the IPv4 external link, provided by the embodiment of the application, is applied to the NAT64 gateway, and the NAT64 gateway diversion identifier can be before the URL of the initial IPv4 external link.
The device for accessing the IPv4 external link, provided by the embodiment of the application, is applied to the NAT64 gateway, and the NAT64 gateway diversion identifier can include a DNS domain name of an IPv4 website.
The IPv4 external link access device provided in the embodiment of the present application is applied to a NAT64 gateway, and the NAT64 gateway diversion identifier may include an IP address of a NAT64 gateway.
The application also provides an IPv4 external link access device and a computer readable storage medium, which have the corresponding effects of the IPv4 external link access method applied to the IPv6 client. Referring to fig. 5, fig. 5 is a schematic structural diagram of an IPv4 external link access device according to an embodiment of the present application.
The IPv4 external link access device provided in the embodiment of the present application, which is applied to an IPv6 client, may include:
a memory 201 for storing a computer program;
a processor 202 for implementing the steps of the method for accessing an IPv4 out-link, as applied to an IPv6 client, as described in any one of the above embodiments, when executing the computer program.
Referring to fig. 6, another device for accessing an IPv4 external link according to the embodiment of the present application may further include: an input port 203 connected to the processor 202, for transmitting externally input commands to the processor 202; a display unit 204 connected to the processor 202, for displaying the processing result of the processor 202 to the outside; and the communication module 205 is connected with the processor 202 and is used for realizing communication between the IPv4 external link access device and the outside world. The display unit 204 may be a display panel, a laser scanning display, or the like; the communication method adopted by the communication module 205 includes, but is not limited to, mobile high definition link technology (HML), Universal Serial Bus (USB), High Definition Multimedia Interface (HDMI), and wireless connection: wireless fidelity technology (WiFi), bluetooth communication technology, bluetooth low energy communication technology, ieee802.11s based communication technology.
The computer-readable storage medium provided by the embodiment of the present application is applied to an IPV6 client, and a computer program is stored in the computer-readable storage medium, and when being executed by a processor, the computer program implements the steps of the IPV4 out-link method applied to an IPV6 client, as described in any of the above embodiments.
The computer-readable storage media to which this application relates include Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage media known in the art.
For a description of relevant parts in an IPv4 external link accessing device, equipment, and a computer-readable storage medium provided in the embodiment of the present application, refer to a detailed description of corresponding parts in an IPv4 external link accessing method provided in the embodiment of the present application, and are not described herein again. In addition, parts of the above technical solutions provided in the embodiments of the present application, which are consistent with the implementation principles of corresponding technical solutions in the prior art, are not described in detail so as to avoid redundant description.
It is further noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in the process, method, article, or apparatus that comprises the element.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (20)
1. A method for accessing IPv4 external links, which is applied to an IPv6 client, and comprises the following steps:
acquiring a URL of a target IPv4 external link, wherein the URL of the target IPv4 external link consists of a NAT64 gateway diversion identifier and a URL of an initial IPv4 external link;
based on the NAT64 gateway diversion identification, diverting the URL of the target IPv4 outer chain to a NAT64 gateway;
receiving data information sent by the NAT64 gateway after accessing the URL of the initial IPv4 external link;
wherein the diverting the URL of the target IPv4 outer chain to a NAT64 gateway based on the NAT64 gateway diversion identifier comprises:
if the IPv6 client side is not connected with the NAT64 gateway, initiating IPv6 address resolution aiming at a main website DNS to obtain an IPv6 address of the NAT64 gateway, and guiding flow of the URL accessing the target IPv4 external link to the NAT64 gateway;
the NAT64 gateway diversion identifier comprises a DNS domain name of an IPv4 website or an IP address of the NAT64 gateway.
2. The method of claim 1, wherein the channeling the target IPv4 out-link URL to a NAT64 gateway based on the NAT64 gateway channeling identification comprises:
and if the IPv6 client establishes connection with the NAT64 gateway, directly guiding the URL of the target IPv4 external link to the NAT64 gateway.
3. The method of claim 2, wherein the target IPv4 out-link URL is generated by the NAT64 gateway, and wherein the obtaining the target IPv4 out-link URL comprises:
and receiving the URL of the target IPv4 external link sent by the NAT64 gateway.
4. The method of claim 2, wherein the target IPv4 out-link URL is generated by the IPv6 client, and wherein the obtaining the target IPv4 out-link URL comprises:
receiving a webpage sent by the NAT64 gateway, wherein the webpage carries the URL and the browser script of the initial IPv4 external link;
traversing out the URL of the initial IPv4 external link carried in the webpage based on the browser script;
and combining the URL of the initial IPv4 external chain and the NAT64 gateway flow guiding identifier into the URL of the target IPv4 external chain.
5. The method of claim 4, wherein the receiving the web page sent by the NAT64 gateway includes:
receiving the cached webpage sent by the NAT64 gateway;
wherein, the process that the NAT64 gateway sends the webpage includes:
caching the webpage which is sent to the IPv6 client at the last time and carries the URL and the browser script of the initial IPv4 external link;
receiving a request for requesting website data information of an IPv4 host website sent by the IPv6 client;
and judging whether the webpage is matched with the request or not, and if so, sending the webpage to the IPv6 client.
6. The method of claim 2, wherein a preset out-chain identifier is added between the NAT64 gateway flow identifier and the URL of the initial IPv4 out-chain.
7. The method of claim 6, wherein the channeling the target IPv4 out-link URL to a NAT64 gateway based on the NAT64 gateway steering identification comprises:
and guiding the URL of the target IPv4 outer chain to a NAT64 gateway based on the NAT64 gateway guide identification through an SSL protocol.
8. The method as claimed in claim 7, wherein the receiving the data information sent by the NAT64 gateway after accessing the URL of the initial IPv4 out-link comprises:
and receiving data information sent after the NAT64 gateway accesses the URL of the initial IPv4 external link through the SSL protocol.
9. The method of any of claims 1 to 8, wherein the NAT64 gateway flow identifies a URL preceding the initial IPv4 out-link.
10. A method for accessing an IPv4 external link is applied to a NAT64 gateway and comprises the following steps:
receiving a request of an IPv6 client for accessing a URL of a target IPv4 outer chain, wherein the URL of the target IPv4 outer chain consists of a NAT64 gateway diversion identifier and a URL of an initial IPv4 outer chain;
accessing the URL of the initial IPv4 external chain, and sending a result of accessing the URL of the initial IPv4 external chain to the IPv6 client;
wherein the IPv6 client, based on the NAT64 gateway diversion identifier, diverts the URL of the target IPv4 outer chain to the NAT64 gateway, including: if the IPv6 client side is not connected with the NAT64 gateway, initiating IPv6 address resolution aiming at a main website DNS to obtain an IPv6 address of the NAT64 gateway, and guiding flow of the URL accessing the target IPv4 external link to the NAT64 gateway;
the NAT64 gateway diversion identifier comprises a DNS domain name of an IPv4 website or an IP address of the NAT64 gateway.
11. The method of claim 10, wherein prior to receiving the request for the IPv6 client to access the URL of the target IPv4 out-link, further comprising:
and generating the URL of the target IPv4 external link, and sending the URL of the target IPv4 external link to the IPv6 client.
12. The method of claim 11, wherein the generating the target IPv4 out-link URL and sending the target IPv4 out-link URL to the IPv6 client comprises:
generating a URL of the target IPv4 outer chain, and encrypting the URL of the target IPv4 outer chain;
and sending the encrypted URL of the target IPv4 external link to the IPv6 client.
13. The method of claim 11, wherein the generating the target IPv4 out-link URL and sending the target IPv4 out-link URL to the IPv6 client comprises:
generating a URL of the target IPv4 outer chain;
adding a timestamp in the URL of the target IPv4 outer chain;
encrypting the URL of the initial IPv4 out-link and the timestamp;
and sending the encrypted URL of the target IPv4 external link to the IPv6 client.
14. The method of claim 10, prior to receiving the request for the IPv6 client to access the URL of the target IPv4 out-link, further comprising:
and sending a webpage carrying a browser script and the URL of the initial IPv4 external link to the IPv6 client, so that the IPv6 client generates the URL of the target IPv4 external link.
15. The method of claim 10, wherein the receiving the request for the IPv6 client to access the URL of the target IPv4 out-link comprises:
and receiving a request sent by the IPv6 client through an SSL protocol for accessing the URL of the target IPv4 external chain.
16. The method of claim 10, wherein said accessing the URL of the initial IPv4 out-link comprises:
and accessing the URL of the initial IPv4 external chain based on an SSL protocol.
17. The method as claimed in any one of claims 10 to 16, wherein the NAT64 gateway flow identifier precedes the URL of the initial IPv4 out-link.
18. An IPv4 out-link access device applied to an IPv6 client comprises the following steps:
the first acquisition module is used for acquiring the URL of a target IPv4 external link, wherein the URL of the target IPv4 external link consists of a NAT64 gateway diversion identifier and the URL of an initial IPv4 external link;
a first diversion module, configured to divert, based on the NAT64 gateway diversion identity, the URL of the target IPv4 out-link to a NAT64 gateway;
a first receiving module, configured to receive data information sent by the NAT64 gateway after accessing the URL of the initial IPv4 external link;
the first diversion module is specifically configured to: if the IPv6 client side is not connected with the NAT64 gateway, initiating IPv6 address resolution aiming at a main website DNS to obtain an IPv6 address of the NAT64 gateway, and guiding flow of the URL accessing the target IPv4 external link to the NAT64 gateway;
the NAT64 gateway diversion identifier comprises a DNS domain name of an IPv4 website or an IP address of the NAT64 gateway.
19. An IPv4 external link access device applied to an IPv6 client comprises the following steps:
a memory for storing a computer program;
a processor for implementing the steps of the method of accessing an IPv4 out-link as claimed in any one of claims 1 to 9 when executing the computer program.
20. A computer-readable storage medium for use in an IPv6 client, the computer-readable storage medium having stored thereon a computer program which, when executed by a processor, carries out the steps of the method of accessing an IPv4 out-link as claimed in any one of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910120432.9A CN109862130B (en) | 2019-02-18 | 2019-02-18 | Method, device, equipment and computer medium for accessing IPv4 external link |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910120432.9A CN109862130B (en) | 2019-02-18 | 2019-02-18 | Method, device, equipment and computer medium for accessing IPv4 external link |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109862130A CN109862130A (en) | 2019-06-07 |
| CN109862130B true CN109862130B (en) | 2022-08-09 |
Family
ID=66898146
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910120432.9A Active CN109862130B (en) | 2019-02-18 | 2019-02-18 | Method, device, equipment and computer medium for accessing IPv4 external link |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109862130B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110417932B (en) * | 2019-07-30 | 2020-08-04 | 睿哲科技股份有限公司 | IPv 6-based out-link resource upgrading device, electronic equipment and computer readable medium |
| CN110392130B (en) * | 2019-08-23 | 2022-09-23 | 北京天融信网络安全技术有限公司 | Information processing method based on network, electronic equipment and network system |
| CN111200643A (en) * | 2019-12-26 | 2020-05-26 | 山石网科通信技术股份有限公司 | Method, device and system for detecting website address |
| CN111064823A (en) * | 2019-12-27 | 2020-04-24 | 深信服科技股份有限公司 | Data processing method, terminal, device and storage medium |
| CN111680233B (en) * | 2020-06-08 | 2023-08-29 | 北京明略昭辉科技有限公司 | Method and device for generating landing page website, storage medium and electronic equipment |
| CN114070818B (en) * | 2021-11-17 | 2024-04-02 | 山石网科通信技术股份有限公司 | Website access system, method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102546850A (en) * | 2010-12-08 | 2012-07-04 | 中国电信股份有限公司 | Method, device and server used for providing internet protocol (IP) v4 content and supporting IPv6 |
| CN102694754A (en) * | 2012-06-07 | 2012-09-26 | 广州睿哲网络科技有限公司 | Application gateway technology and system for realizing content interchange of Internet protocol version 4/Internet protocol version 6 (IPv4/IPv6) websites |
| CN106790503A (en) * | 2016-12-16 | 2017-05-31 | 广东睿哲科技股份有限公司 | It is a kind of to realize the IPv4 websites without skylight using the device upgraded to IPv6 based on HTTP reverse proxys |
| CN106790098A (en) * | 2016-12-26 | 2017-05-31 | 广东睿哲科技股份有限公司 | A kind of IPv4/IPv6 intercommunicating systems based on HTTP ALG Yu NAT64 technologies |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110040886A1 (en) * | 2008-05-01 | 2011-02-17 | Nortel Networks Limited | Method and System for Identification of Packet Gateways Supporting Different Service Types |
-
2019
- 2019-02-18 CN CN201910120432.9A patent/CN109862130B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102546850A (en) * | 2010-12-08 | 2012-07-04 | 中国电信股份有限公司 | Method, device and server used for providing internet protocol (IP) v4 content and supporting IPv6 |
| CN102694754A (en) * | 2012-06-07 | 2012-09-26 | 广州睿哲网络科技有限公司 | Application gateway technology and system for realizing content interchange of Internet protocol version 4/Internet protocol version 6 (IPv4/IPv6) websites |
| CN106790503A (en) * | 2016-12-16 | 2017-05-31 | 广东睿哲科技股份有限公司 | It is a kind of to realize the IPv4 websites without skylight using the device upgraded to IPv6 based on HTTP reverse proxys |
| CN106790098A (en) * | 2016-12-26 | 2017-05-31 | 广东睿哲科技股份有限公司 | A kind of IPv4/IPv6 intercommunicating systems based on HTTP ALG Yu NAT64 technologies |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109862130A (en) | 2019-06-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109862130B (en) | Method, device, equipment and computer medium for accessing IPv4 external link | |
| US10419398B2 (en) | Method and apparatus for resource locator identifier rewrite | |
| US9769126B2 (en) | Secure personal server system and method | |
| US10904227B2 (en) | Web form protection | |
| CN105791451B (en) | Message response method and device | |
| CN105635073B (en) | Access control method and device and network access equipment | |
| CN108632221B (en) | Method, equipment and system for positioning controlled host in intranet | |
| CN111917900B (en) | Domain name agent request processing method and device | |
| WO2020019477A1 (en) | Communication data encryption method and apparatus | |
| US10033830B2 (en) | Requesting web pages and content rating information | |
| CN110691149B (en) | Method and apparatus for operating content delivery network and method for operating origin server | |
| CN102547553B (en) | Method, system and device for accessing service based on wireless application protocol (WAP) | |
| CN102065573A (en) | WAP gateway agent service data processing method and server | |
| CN101378407B (en) | Method, system and equipment for pushing information | |
| CN111049832B (en) | Reverse proxy method and related device | |
| CN106031097A (en) | Service processing method and device | |
| CN101945053B (en) | Method and device for transmitting message | |
| CN106411978B (en) | Resource caching method and device | |
| CN106453399B (en) | A kind of domain name resolution service method and system of user oriented secret protection | |
| CA3027340A1 (en) | Secure personal server system and method | |
| WO2014166078A1 (en) | Data sending and processing method and router | |
| JP2019522416A (en) | System and method for DNS request suppression | |
| US8150875B1 (en) | Method and an apparatus to store information regarding web pages | |
| CN108418906A (en) | A kind of domain name analytic method and system | |
| US7769766B1 (en) | Method and an apparatus to store content rating information |
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 |