CN111416862B - CDN platform access method and system based on IPV6IPV4 - Google Patents
CDN platform access method and system based on IPV6IPV4 Download PDFInfo
- Publication number
- CN111416862B CN111416862B CN202010202495.1A CN202010202495A CN111416862B CN 111416862 B CN111416862 B CN 111416862B CN 202010202495 A CN202010202495 A CN 202010202495A CN 111416862 B CN111416862 B CN 111416862B
- Authority
- CN
- China
- Prior art keywords
- user
- response content
- ipv6
- user terminal
- skylight
- 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
- 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]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
-
- 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
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/60—Types of network addresses
- H04L2101/686—Types of network addresses using dual-stack hosts, e.g. in Internet protocol version 4 [IPv4]/Internet protocol version 6 [IPv6] networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention belongs to the technical field of source station IPV6 transformation, and particularly relates to a CDN platform access method and system based on IPV6IPV4, which comprises the following steps: the user terminal sends a request to the DNS server, and the DNS server feeds a DNS response back to the user according to the request; the user terminal sends a request to the CDN edge node server according to the DNS response, and the CDN edge node server sends the obtained response content to the skylight transformation device; and the skylight reconstruction device judges whether the user is an IPV6 user or not according to the response content, judges whether the response content has an external link or not if the response content has the external link, and feeds back the response content to the user terminal after the external link is rewritten if the response content has the external link. The present invention supports IPV6 without modification of the source station; the IPV6 and the IPV4 users share cache resources, so that the CDN acceleration effect is ensured; the website outer chain is rewritten through the skylight reconstruction device, and the skylight problem that a user accesses the outer chain under the IPV6 environment is solved.
Description
Technical Field
The invention belongs to the technical field of source station IPV6 transformation, and particularly relates to a CDN platform access method and system based on IPV6IPV 4.
Background
The shortage of IPV4 address space has hindered and limited the development of the internet, and therefore, the substitution of IPV6 for IPV4 has been a necessary trend. Most current solutions for source station IPV6 upgrade are: the conversion equipment from IPV6 to IPV4 is deployed at the front end of the source station, so that the source station supports IPV6 and also supports third-party off-link rewriting of the website to solve the skylight problem. In the existing internet environment, along with the improvement of the network performance requirements of users, most websites need to use the CDN to improve the access speed, and improve the user experience.
The existing source station IPV6 modification technology has the following two disadvantages:
1. the IPV6 transformation equipment is deployed at the front end of the source station, and the network deployment of the source station needs to be changed, which is troublesome.
2. If a CDN is used, a user supporting IPV6 cannot be resolved back to a source station supporting IPV6, and a user compatible with IPV6 and IPV4 accesses an IPV4 environment, and a user supporting IPV6 cannot access the environment.
Disclosure of Invention
Aiming at the defects in the prior art, the invention provides a CDN platform deployment method and system based on IPV6 and IPV4, which support IPV6 without any change of a source station; users of the IPV6 and the IPV4 can share cache resources, and the CDN acceleration effect of the IPV6 is ensured; through the deployed skylight reconstruction device, the outer chain of the website is rewritten, and the skylight problem existing when a user accesses the outer chain under the pure IPV6 environment is solved.
In a first aspect, the present invention provides an IPV 6-IPV 4-based CDN platform access method, including the following steps:
the user terminal sends a DNS request to a DNS server, and the DNS server feeds a DNS response back to the user according to the DNS request;
the user terminal initiates an HTTP request to the CDN edge node server according to the IPV6 address or the IPV4 address obtained by DNS response, the CDN edge node server obtains response content according to the HTTP request and sends the response content to the skylight improvement device;
the skylight reconstruction device judges whether the user is an IPV6 user or not according to the response content, judges whether the response content has an external link or not if the user is the IPV6 user, and carries out external link rewriting on the response content and feeds back the rewritten response content to the user terminal if the response content has the external link.
Preferably, the user terminal sends a DNS request to a DNS server, and the DNS server feeds back a DNS response to the user according to the DNS request, specifically:
the user terminal initiates a DNS request of IPV4 or IPV6 of the website domain name according to the local network environment;
the DNS server obtains a regional operator to which the user belongs according to the user IP in the DNS request, and inquires an IPV4 address and an IPV6 address of a CDN edge node server served by the regional operator;
and judging whether the response IPV4 address or the IPV6 address is judged according to the DNS request, if the response IPV4 address or the IPV6 address is the DNS request AAAA record, feeding back the IPV6 address of the CDN edge node server to the user terminal, and if the response IPV 35AA record is the DNS request A record, feeding back the IPV4 address of the CDN edge node server to the user terminal.
Preferably, the user terminal initiates an HTTP request to the CDN edge node server according to the IPV6 address or the IPV4 address obtained by the DNS response, and the CDN edge node server obtains response content according to the HTTP request and sends the response content to the sunroof modification device, specifically:
the user terminal initiates an HTTP request to a corresponding CDN edge node server according to the IPV6 address or the IPV4 address, the CDN edge node server performs local query according to the HTTP request and judges whether a local cache exists or not, if the local cache exists, response content is read and sent to the skylight reconstruction device, if the local cache does not exist, a request is initiated to a source station or a CDN father node, response content fed back by the source station or the CDN father node is obtained, and the response content is sent to the skylight reconstruction device.
Preferably, the sunroof reconstruction device determines whether the user is an IPV6 user or not according to the response content, determines whether the response content has an external link if the user is an IPV6 user, and rewrites the external link of the response content and feeds the rewritten response content back to the user terminal if the response content has the external link, specifically:
the skylight reconstruction device judges whether the user is an IPV6 user or not according to the user IP in the response content; if the user is an IPV6 user, further judging whether the response content has an external link, if so, rewriting the external link of the response content and feeding back the rewritten response content to the user terminal, and if not, directly feeding back the response content to the user terminal; if the user is not an IPV6 user, the response content is directly fed back to the user terminal.
Preferably, the step of feeding back the response content after the outer link rewriting is performed to the user terminal specifically includes:
extracting the outer-link domain name in the response content, and obtaining a corresponding outer-link new domain name supporting IPV6 according to a rewriting rule; and rewriting the outer chain domain name into an outer chain new domain name, and feeding back the response content after the outer chain is rewritten to the user terminal.
Preferably, the out-link new domain name supporting IPV6 is a domain name supporting IPV6 domain name resolution and resolvable to the present system.
Preferably, the method further comprises the following steps:
when the user terminal performs external link access, the skylight improvement device performs security validity verification and original URL restoration, acquires response content according to the original URL, and feeds back the response content to the user terminal.
Preferably, when the user terminal is used for performing the external link access, the skylight reconstruction device performs security validity verification and original URL reduction, acquires response content according to the original URL, and feeds back the response content to the user terminal, specifically:
and the user terminal accesses the rewritten outer chain, the skylight reconstruction device verifies the safety and the legality of the rewritten outer chain, if the verification is rewritten by the system, the original URL is restored according to the new domain name of the outer chain, response content is obtained through the original URL, and if the verification is not rewritten by the system, the user terminal responds 403 to refuse service or disconnect connection and does not respond.
In a second aspect, the present invention provides a CDN platform system based on IPV6 and IPV4, which is suitable for the CDN platform access method based on IPV6 and IPV4 in the first aspect, and includes: the system comprises a DNS server, a CDN edge node server and a skylight transformation device;
the user terminal sends a DNS request to a DNS server, and the DNS server feeds a DNS response back to the user according to the DNS request;
the user terminal initiates an HTTP request to the CDN edge node server according to the IPV6 address or the IPV4 address obtained by DNS response, the CDN edge node server obtains response content according to the HTTP request and sends the response content to the skylight improvement device;
the skylight reconstruction device judges whether the user is an IPV6 user or not according to the response content, judges whether the response content has an external link or not if the user is the IPV6 user, and carries out external link rewriting on the response content and feeds back the rewritten response content to the user terminal if the response content has the external link.
Preferably, the skylight modifying device is deployed in a CDN edge node server, or the skylight modifying device is deployed in a separate server.
The technical scheme of the invention supports the IPV6 without any change of the source station; users of the IPV6 and the IPV4 can share cache resources, and the CDN acceleration effect of the IPV6 is ensured; through the deployed skylight reconstruction device, the outer chain of the website is rewritten, and the skylight problem existing when a user accesses the outer chain under the pure IPV6 environment is solved.
Drawings
In order to more clearly illustrate the detailed description of the invention or the technical solutions in the prior art, the drawings that are needed in the detailed description of the invention or the prior art will be briefly described below. Throughout the drawings, like elements or portions are generally identified by like reference numerals. In the drawings, elements or portions are not necessarily drawn to scale.
Fig. 1 is a flowchart of a CDN platform access method based on IPV6IPV4 in this embodiment;
fig. 2 is a structural diagram of the CDN platform system based on IPV6IPV4 in this embodiment.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. 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 invention.
It will be understood that the terms "comprises" and "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the specification of the present invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted "as" when used in a language such as "or" upon "or" in response to a determination or "in response to a detection," depending on the context. Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted, depending on the context, to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
The first embodiment is as follows:
the embodiment provides a CDN platform access method based on IPV6IPV4, as shown in fig. 1, including the following steps:
s1, the user terminal sends a DNS request to the DNS server, and the DNS server feeds back a DNS response to the user according to the DNS request;
s2, the user terminal initiates an HTTP request to the CDN edge node server according to the IPV6 address or the IPV4 address obtained by DNS response, the CDN edge node server obtains response content according to the HTTP request, and sends the response content to the skylight improvement device;
s3, the skylight reconstruction device judges whether the user is an IPV6 user or not according to the response content, judges whether the response content has an external link or not if the user is an IPV6 user, and feeds back the response content to the user terminal after the external link is rewritten if the response content has the external link;
and S4, when the user terminal accesses the external link, the skylight improvement device carries out security validity verification and original URL restoration, acquires response content according to the original URL and feeds back the response content to the user terminal.
Step S1 of this embodiment specifically includes:
the user terminal initiates a DNS request of IPV4 or IPV6 of the website domain name according to the local network environment;
the DNS server obtains a regional operator to which the user belongs according to the user IP in the DNS request, and inquires an IPV4 address and an IPV6 address of a CDN edge node server served by the regional operator;
and judging whether the response IPV4 address or the IPV6 address is judged according to the DNS request, if the response IPV4 address or the IPV6 address is the DNS request AAAA record, feeding back the IPV6 address of the CDN edge node server to the user terminal, and if the response IPV 35AA record is the DNS request A record, feeding back the IPV4 address of the CDN edge node server to the user terminal.
In this embodiment, after a user initiates a query request to a DNS server, the DNS server feeds back a corresponding CDN edge node server IP address to the user according to the DNS request. And when the DNS requests the record A, the IPV4 address of the CDN edge node server is fed back to the user, and when the DNS requests the record AAAA, the IPV6 address of the CDN edge node server is fed back to the user. (remark: IPV6 user typically initiates a DNS request for AAAA records)
Step S2 of this embodiment specifically includes:
the user terminal initiates an HTTP request to a corresponding CDN edge node server according to the IPV6 address or the IPV4 address, the CDN edge node server performs local query according to the HTTP request and judges whether a local cache exists or not, if the local cache exists, response content is read and sent to the skylight reconstruction device, if the local cache does not exist, a request is initiated to a source station or a CDN father node, response content fed back by the source station or the CDN father node is obtained, and the response content is sent to the skylight reconstruction device.
In this embodiment, after obtaining the IPV6 address and the IPV4 address, the user terminal initiates a request to the corresponding CDN edge node server. If the CDN edge node server has content requested by the user, the response content is directly sent to the skylight reconstruction device for processing, and if the CDN edge node server does not have the content requested by the user, the response content needs to be obtained from a source station or a CDN father node and then is forwarded to the skylight reconstruction device.
Step S3 of this embodiment specifically includes:
the skylight reconstruction device judges whether the user is an IPV6 user or not according to the user IP in the response content; if the user is an IPV6 user, further judging whether the response content has an external link, if so, rewriting the external link of the response content and feeding back the rewritten response content to the user terminal, and if not, directly feeding back the response content to the user terminal; if the user is not an IPV6 user, the response content is directly fed back to the user terminal.
With the development of network technology, the existing IPV4 network is gradually upgraded to IPV6 network, and the skylight problem is a problem that is inevitably encountered in the development of the next generation internet upgrading IPV6 network. The skylight problem is that when a webpage contains links (outer links) of other website contents, when the user of the IPV6 accesses the website, parts of the contents cannot be displayed, parts of the functions cannot be used, and the like. The present embodiment thus addresses the skylight problem through a deployed skylight retrofit device. Knowing the user type according to the object to be fed back by the response content, if the user is an IPV4 user, no skylight problem exists, and the response content is directly fed back to the user terminal. If the user is an IPV6 user, a skylight problem may exist, and therefore, it is further determined whether an external link exists in the response content, and if the external link does not exist, the response content is directly fed back to the user terminal, and if the external link exists, the external link is rewritten, and the response content after the external link is rewritten is fed back to the user terminal.
Wherein, the feedback of the response content after the outer link rewriting is specifically:
extracting the outer-link domain name in the response content, and obtaining a corresponding outer-link new domain name supporting IPV6 according to a rewriting rule; and rewriting the outer chain domain name into an outer chain new domain name, and feeding back the response content after the outer chain is rewritten to the user terminal.
The out-link new domain name supporting IPV6 in this embodiment is a domain name supporting IPV6 domain name resolution and capable of being resolvable to the present system again. Attention to outer chain rewrite: 1. the skylight reconstruction device can restore the rewritten external link resource to the original URL according to a certain rule when the rewritten external link resource is accessed; 2. the outer chain rewriting rule is to avoid the condition that the length of each level of domain name or the total length of the domain name is too long, otherwise, the domain name cannot be analyzed; 3. the rewritten rule preferably has its own encryption method for preventing other people from easily recognizing the rewritten rule of the system and introducing a non-service request into the system by using the rewritten rule, which affects the security and legitimacy of the system.
Step S4 of this embodiment specifically includes:
and the user terminal accesses the rewritten outer chain, the skylight reconstruction device verifies the safety and the legality of the rewritten outer chain, if the verification is rewritten by the system, the original URL is restored according to the new domain name of the outer chain, response content is obtained through the original URL, and if the verification is not rewritten by the system, the user terminal responds 403 to refuse service or disconnect connection and does not respond.
In this embodiment, the user obtains the rewritten page, and accesses the IPV6CDN edge node server when accessing the external link resource, and the skylight modification device corresponding to the IPV6CDN edge node server restores the external link to the original URL, and accesses through the original URL, and if there is a local cache, reads the cache to respond to the user, and if there is no local cache, obtains a response through a source return and feeds back the user.
For overwriting and accessing of outer links, the following is exemplified.
E.g. user accesswww.wanwuyunlian.comThe page may contain out-link resources that do not support IPV6, such as out-link domain names:
http://www.ipv4.com/1.jpgorhttp://112.45.10.114/2.jpg。
These out-link domain names need to be rewritten using a certain rewrite rule, for example, the rewritten out-link new domain name is:
http://www--ipv4--com--a8x0.wanwuyunlian.com/1.jpgorhttp://112-- 45--10--114--xu2k/2.jpg。
And when the user accesses the network again, performing security validity verification and original URL restoration processing to feed back correct response content. And (4) safety and legality verification: for example, a8x0 and xu2k in the two URLs are encrypted strings calculated according to a certain encryption mode, and whether the URL is rewritten by the system or is requested by other illegal and malicious programs can be judged according to the encrypted strings. When the original URL is restored, the original URL can be restored according to the rewriting rule, such as being restored to
http://www.ipv4.com/1.jpgOrhttp://112.45.10.114/2.jpg。
And then obtaining a response through the restored URL to the source station or obtaining the response from a cache of a CDN edge node server, and sending the response to the user.
In summary, the present embodiment supports IPV6 through the CDN platform, and the source station domain name CNAME is accessed, so that IPV6 user access can be supported without any change in the network deployment of the source server; by deploying the IPV6 skylight improvement device in the CDN platform, the skylight problem existing when an IPV6 user accesses an external chain of a website can be solved without changing the code structure and the service logic of an origin server. The IPV4 and the IPV6 are simultaneously accessed to the CDN, the access speed of all users is improved, meanwhile, the users share cache resources through the IPV4 and the IPV6, the user access speed of the IPV6 is improved, and the problem that the access speed is slow because the number of IPV6 accesses is small and no cache needs to be returned to the source on a CDN cache server is solved.
Example two:
the embodiment provides a CDN platform system based on IPV6 and IPV4, which is suitable for the CDN platform access method based on IPV6 and IPV4 in the first embodiment, and as shown in fig. 2, the CDN platform access method includes: the system comprises a DNS server, a CDN edge node server and a skylight transformation device;
the user terminal sends a DNS request to a DNS server, and the DNS server feeds a DNS response back to the user according to the DNS request;
the user terminal initiates an HTTP request to the CDN edge node server according to the IPV6 address or the IPV4 address obtained by DNS response, the CDN edge node server obtains response content according to the HTTP request and sends the response content to the skylight improvement device;
the skylight reconstruction device judges whether the user is an IPV6 user or not according to the response content, judges whether the response content has an external link or not if the user is an IPV6 user, and feeds back the response content to the user terminal after the external link is rewritten if the response content has the external link;
when the user terminal performs external link access, the skylight improvement device performs security validity verification and original URL restoration, acquires response content according to the original URL, and feeds back the response content to the user terminal.
The skylight reconstruction device of this embodiment is deployed in a CDN edge node server, or the skylight reconstruction device is deployed in a single server.
The user terminal initiates a DNS request of IPV4 or IPV6 of the website domain name according to the local network environment; the DNS server obtains a regional operator to which the user belongs according to the user IP in the DNS request, and inquires an IPV4 address and an IPV6 address of a CDN edge node server served by the regional operator;
and judging whether the response IPV4 address or the IPV6 address is judged according to the DNS request, if the response IPV4 address or the IPV6 address is the DNS request AAAA record, feeding back the IPV6 address of the CDN edge node server to the user terminal, and if the response IPV 35AA record is the DNS request A record, feeding back the IPV4 address of the CDN edge node server to the user terminal.
In this embodiment, after a user initiates a query request to a DNS server, the DNS server feeds back a corresponding CDN edge node server IP address to the user according to the DNS request. And when the DNS requests the record A, the IPV4 address of the CDN edge node server is fed back to the user, and when the DNS requests the record AAAA, the IPV6 address of the CDN edge node server is fed back to the user.
The user terminal initiates an HTTP request to a corresponding CDN edge node server according to the IPV6 address or the IPV4 address, the CDN edge node server performs local query according to the HTTP request and judges whether a local cache exists or not, if the local cache exists, response content is read and sent to the skylight reconstruction device, if the local cache does not exist, a request is initiated to a source station or a CDN father node, response content fed back by the source station or the CDN father node is obtained, and the response content is sent to the skylight reconstruction device.
In this embodiment, after obtaining the IPV6 address and the IPV4 address, the user terminal initiates a request to the corresponding CDN edge node server. If the CDN edge node server has content requested by the user, the response content is directly sent to the skylight reconstruction device for processing, and if the CDN edge node server does not have the content requested by the user, the response content needs to be obtained from a source station or a CDN father node and then is forwarded to the skylight reconstruction device.
The skylight reconstruction device judges whether the user is an IPV6 user or not according to the user IP in the response content; if the user is an IPV6 user, further judging whether the response content has an external link, if so, rewriting the external link of the response content and feeding back the rewritten response content to the user terminal, and if not, directly feeding back the response content to the user terminal; if the user is not an IPV6 user, the response content is directly fed back to the user terminal.
With the development of network technology, the existing IPV4 network is gradually upgraded to IPV6 network, and the skylight problem is a problem that is inevitably encountered in the development of the next generation internet upgrading IPV6 network. The skylight problem is that when a webpage contains links (outer links) of other website contents, when the user of the IPV6 accesses the website, parts of the contents cannot be displayed, parts of the functions cannot be used, and the like. The present embodiment thus addresses the skylight problem through a deployed skylight retrofit device. Knowing the user type according to the object to be fed back by the response content, if the user is an IPV4 user, no skylight problem exists, and the response content is directly fed back to the user terminal. If the user is an IPV6 user, a skylight problem may exist, and therefore, it is further determined whether an external link exists in the response content, and if the external link does not exist, the response content is directly fed back to the user terminal, and if the external link exists, the external link is rewritten, and the response content after the external link is rewritten is fed back to the user terminal.
Wherein, the feedback of the response content after the outer link rewriting is specifically:
extracting the outer-link domain name in the response content, and obtaining a corresponding outer-link new domain name supporting IPV6 according to a rewriting rule; and rewriting the outer chain domain name into an outer chain new domain name, and feeding back the response content after the outer chain is rewritten to the user terminal.
The out-link new domain name supporting IPV6 in this embodiment is a domain name supporting IPV6 domain name resolution and capable of being resolvable to the present system again. Attention to outer chain rewrite: 1. the skylight reconstruction device can restore the rewritten external link resource to the original URL according to a certain rule when the rewritten external link resource is accessed; 2. the outer chain rewriting rule is to avoid the condition that the length of each level of domain name or the total length of the domain name is too long, otherwise, the domain name cannot be analyzed; 3. the rewritten rule preferably has its own encryption method for preventing other people from easily recognizing the rewritten rule of the system and introducing a non-service request into the system by using the rewritten rule, which affects the security and legitimacy of the system.
And the user terminal accesses the rewritten outer chain, the skylight reconstruction device verifies the safety and the legality of the rewritten outer chain, if the verification is rewritten by the system, the original URL is restored according to the new domain name of the outer chain, response content is obtained through the original URL, and if the verification is not rewritten by the system, the user terminal responds 403 to refuse service or disconnect connection and does not respond.
In this embodiment, the user obtains the rewritten page, and accesses the IPV6CDN edge node server when accessing the external link resource, and the skylight modification device corresponding to the IPV6CDN edge node server restores the external link to the original URL, and accesses through the original URL, and if there is a local cache, reads the cache to respond to the user, and if there is no local cache, obtains a response through a source return and feeds back the user.
For overwriting and accessing of outer links, the following is exemplified.
E.g. user accesswww.wanwuyunlian.comThe page may contain out-link resources that do not support IPV6, such as out-link domain names:
http://www.ipv4.com/1.jpgorhttp://112.45.10.114/2.jpg。
These out-link domain names need to be rewritten using a certain rewrite rule, for example, the rewritten out-link new domain name is:
http://www--ipv4--com--a8x0.wanwuyunlian.com/1.jpgorhttp://112-- 45--10--114--xu2k/2.jpg。
And when the user accesses the network again, performing security validity verification and original URL restoration processing to feed back correct response content. And (4) safety and legality verification: for example, a8x0 and xu2k in the two URLs are encrypted strings calculated according to a certain encryption mode, and whether the URL is rewritten by the system or is requested by other illegal and malicious programs can be judged according to the encrypted strings. When the original URL is restored, the original URL can be restored according to the rewriting rule, such as being restored to
http://www.ipv4.com/1.jpgOrhttp://112.45.10.114/2.jpg。
And then obtaining a response through the restored URL to the source station or obtaining the response from a cache of a CDN edge node server, and sending the response to the user.
In summary, the present embodiment supports IPV6 through the CDN platform, and the source station domain name CNAME is accessed, so that IPV6 user access can be supported without any change in the network deployment of the source server; by deploying the IPV6 skylight improvement device in the CDN platform, the skylight problem existing when an IPV6 user accesses an external chain of a website can be solved without changing the code structure and the service logic of an origin server. The IPV4 and the IPV6 are simultaneously accessed to the CDN, the access speed of all users is improved, meanwhile, the users share cache resources through the IPV4 and the IPV6, the user access speed of the IPV6 is improved, and the problem that the access speed is slow because the number of IPV6 accesses is small and no cache needs to be returned to the source on a CDN cache server is solved.
The technical scheme of the invention supports the IPV6 without any change of the source station; users of the IPV6 and the IPV4 can share cache resources, and the CDN acceleration effect of the IPV6 is ensured; through the deployed skylight reconstruction device, the outer chain of the website is rewritten, and the skylight problem existing when a user accesses the outer chain under the pure IPV6 environment is solved.
Furthermore, those of ordinary skill in the art will appreciate that the elements or steps of the various examples described in connection with the embodiments disclosed herein may be embodied as electronic hardware, computer software, or combinations of both, and that the components and steps of the various examples have been described above generally in terms of their functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
In the embodiments provided in the present application, it should be understood that the division of the steps is only one logical functional division, and there may be other division ways in actual implementation, for example, multiple steps may be combined into one step, one step may be split into multiple steps, or some features may be omitted.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; such modifications and substitutions do not depart from the spirit and scope of the present invention, and they should be construed as being included in the following claims and description.
Claims (6)
1. A CDN platform access method based on IPV6IPV4 is characterized by comprising the following steps:
the user terminal sends a DNS request to a DNS server, and the DNS server feeds a DNS response back to the user according to the DNS request;
the user terminal initiates an HTTP request to the CDN edge node server according to the IPV6 address or the IPV4 address obtained by DNS response, the CDN edge node server obtains response content according to the HTTP request and sends the response content to the skylight improvement device;
the method specifically comprises the following steps:
the user terminal initiates an HTTP request to a corresponding CDN edge node server according to the IPV6 address or the IPV4 address, the CDN edge node server performs local query according to the HTTP request and judges whether a local cache exists or not, if the local cache exists, response content is read and sent to the skylight reconstruction device, if the local cache does not exist, a request is initiated to a source station or a CDN father node, response content fed back by the source station or the CDN father node is obtained, and the response content is sent to the skylight reconstruction device;
the skylight reconstruction device judges whether the user is an IPV6 user or not according to the response content, judges whether the response content has an external link or not if the user is an IPV6 user, and feeds back the response content to the user terminal after the external link is rewritten if the response content has the external link;
wherein, the feedback of the response content after the outer link rewriting is specifically:
extracting the outer-link domain name in the response content, and obtaining a corresponding outer-link new domain name supporting IPV6 according to a rewriting rule; rewriting the outer-link domain name into an outer-link new domain name, and feeding back the response content after the outer-link is rewritten to the user terminal;
the new external-link domain name supporting the IPV6 can support the domain name resolution of the IPV6 and can be restored to the original URL by the skylight improving device, and the rewriting rule has a preset encryption method;
when the user terminal performs external link access, the skylight improvement device performs security validity verification and original URL restoration, acquires response content according to the original URL and feeds back the response content to the user terminal;
specifically, the method comprises the following steps:
and the user terminal accesses the rewritten outer chain, the skylight reconstruction device verifies the safety and the legality of the rewritten outer chain, if the verification is rewritten by the system, the original URL is restored according to the new domain name of the outer chain, response content is obtained through the original URL, and if the verification is not rewritten by the system, the user terminal responds 403 to refuse service or disconnect connection and does not respond.
2. The CDN platform access method based on the IPV6IPV4 of claim 1, wherein the user terminal sends a DNS request to a DNS server, and the DNS server feeds back a DNS response to a user according to the DNS request, specifically:
the user terminal initiates a DNS request of IPV4 or IPV6 of the website domain name according to the local network environment;
the DNS server obtains a regional operator to which the user belongs according to the user IP in the DNS request, and inquires an IPV4 address and an IPV6 address of a CDN edge node server served by the regional operator;
and judging whether the response IPV4 address or the IPV6 address is judged according to the DNS request, if the response IPV4 address or the IPV6 address is the DNS request AAAA record, feeding back the IPV6 address of the CDN edge node server to the user terminal, and if the response IPV 35AA record is the DNS request A record, feeding back the IPV4 address of the CDN edge node server to the user terminal.
3. The IPV6IPV 4-based CDN platform access method of claim 1, wherein the skylight reforming device determines whether the user is an IPV6 user or not according to the response content, if the user is an IPV6 user, determines whether the response content has an out-link, if the response content has an out-link, the response content is rewritten by the out-link and then fed back to the user terminal, specifically:
the skylight reconstruction device judges whether the user is an IPV6 user or not according to the user IP in the response content; if the user is an IPV6 user, further judging whether the response content has an external link, if so, rewriting the external link of the response content and feeding back the rewritten response content to the user terminal, and if not, directly feeding back the response content to the user terminal; if the user is not an IPV6 user, the response content is directly fed back to the user terminal.
4. The IPV6IPV 4-based CDN platform access method according to claim 1 wherein the out-link new domain name that supports IPV6 is the domain name that supports IPV6 domain name resolution and can be resolvable to the system again.
5. A CDN platform system based on IPV6 and IPV4, adapted to the CDN platform access method based on IPV6IPV4 of any one of claims 1-4, wherein the CDN platform system comprises: the system comprises a DNS server, a CDN edge node server and a skylight transformation device;
the user terminal sends a DNS request to a DNS server, and the DNS server feeds a DNS response back to the user according to the DNS request;
the user terminal initiates an HTTP request to the CDN edge node server according to the IPV6 address or the IPV4 address obtained by DNS response, the CDN edge node server obtains response content according to the HTTP request and sends the response content to the skylight improvement device;
the skylight reconstruction device judges whether the user is an IPV6 user or not according to the response content, judges whether the response content has an external link or not if the user is the IPV6 user, and carries out external link rewriting on the response content and feeds back the rewritten response content to the user terminal if the response content has the external link.
6. The CDN platform system based on IPV6 and IPV4 and according to claim 5 wherein said skylight retrofit device is deployed in CDN edge node servers or said skylight retrofit device is deployed in a separate server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010202495.1A CN111416862B (en) | 2020-03-20 | 2020-03-20 | CDN platform access method and system based on IPV6IPV4 |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010202495.1A CN111416862B (en) | 2020-03-20 | 2020-03-20 | CDN platform access method and system based on IPV6IPV4 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111416862A CN111416862A (en) | 2020-07-14 |
| CN111416862B true CN111416862B (en) | 2021-06-15 |
Family
ID=71494419
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010202495.1A Active CN111416862B (en) | 2020-03-20 | 2020-03-20 | CDN platform access method and system based on IPV6IPV4 |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111416862B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112600950A (en) * | 2020-12-09 | 2021-04-02 | 福建万物易联网络科技有限公司 | Outer chain rewriting method and system of short crossbar format |
| CN112771835B (en) * | 2020-12-25 | 2023-05-02 | 山石网科通信技术股份有限公司 | Method and device for processing outer link rewriting |
| CN113301178B (en) * | 2021-04-27 | 2022-05-27 | 新华三信息安全技术有限公司 | Method and equipment for realizing skylight agent |
| CN114285856B (en) * | 2021-12-10 | 2024-04-23 | 杭州迪普科技股份有限公司 | IPV4 external link access method and device |
| CN115277809A (en) * | 2022-08-02 | 2022-11-01 | 北京有竹居网络技术有限公司 | Access request processing method, edge server and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101600000A (en) * | 2009-06-26 | 2009-12-09 | 中国电信股份有限公司 | The data communications method and the system of IPv6 user capture IPv4 website |
| CN103856408A (en) * | 2014-02-17 | 2014-06-11 | 中国科学院计算机网络信息中心 | IPv6 and IPv4 intercommunication method based on DNS |
| CN104158918A (en) * | 2014-07-18 | 2014-11-19 | 广州杰赛科技股份有限公司 | Interworking method and system for IPv4 and IPv6 |
| CN106790759A (en) * | 2016-12-29 | 2017-05-31 | 赛尔网络有限公司 | IPv4/IPv6 converting systems and method based on SDN |
| CN109451097A (en) * | 2019-01-02 | 2019-03-08 | 北京宏图佳都通信设备有限公司 | IPv4/IPv6 address conversion system |
| CN110417932A (en) * | 2019-07-30 | 2019-11-05 | 睿哲科技股份有限公司 | Based on IPv6 exterior chain resource graded device, electronic equipment and computer-readable medium |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7539773B2 (en) * | 2004-11-16 | 2009-05-26 | Yokogawa Electric Corporation | Network system using IPv4/IPv6 translator |
| US9467461B2 (en) * | 2013-12-21 | 2016-10-11 | Akamai Technologies Inc. | Countering security threats with the domain name system |
| CN109561078B (en) * | 2018-11-09 | 2022-04-12 | 深圳万物云联科技有限公司 | External link url resource calling method and device |
| CN109543121B (en) * | 2018-11-09 | 2023-11-03 | 深圳万物云联科技有限公司 | Method and device for calling outer link url (real time communication) resources |
-
2020
- 2020-03-20 CN CN202010202495.1A patent/CN111416862B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101600000A (en) * | 2009-06-26 | 2009-12-09 | 中国电信股份有限公司 | The data communications method and the system of IPv6 user capture IPv4 website |
| CN103856408A (en) * | 2014-02-17 | 2014-06-11 | 中国科学院计算机网络信息中心 | IPv6 and IPv4 intercommunication method based on DNS |
| CN104158918A (en) * | 2014-07-18 | 2014-11-19 | 广州杰赛科技股份有限公司 | Interworking method and system for IPv4 and IPv6 |
| CN106790759A (en) * | 2016-12-29 | 2017-05-31 | 赛尔网络有限公司 | IPv4/IPv6 converting systems and method based on SDN |
| CN109451097A (en) * | 2019-01-02 | 2019-03-08 | 北京宏图佳都通信设备有限公司 | IPv4/IPv6 address conversion system |
| CN110225148A (en) * | 2019-01-02 | 2019-09-10 | 北京宏图佳都通信设备有限公司 | IPv4/IPv6 address conversion system |
| CN110417932A (en) * | 2019-07-30 | 2019-11-05 | 睿哲科技股份有限公司 | Based on IPv6 exterior chain resource graded device, electronic equipment and computer-readable medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111416862A (en) | 2020-07-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111416862B (en) | CDN platform access method and system based on IPV6IPV4 | |
| US10412176B2 (en) | Website access method, apparatus, and website system | |
| CN106101231B (en) | Method and device for realizing resource downloading through CDN (content delivery network), server and client | |
| US10511567B2 (en) | Network resource identification | |
| CN111416885B (en) | Outer chain rewriting distributed system with fixed-length domain name | |
| EP2266043B1 (en) | Cache optimzation | |
| CN109543121B (en) | Method and device for calling outer link url (real time communication) resources | |
| US6202087B1 (en) | Replacement of error messages with non-error messages | |
| US20020194382A1 (en) | Method and system for efficient and automated version management of embedded objects in web documents | |
| US20060271641A1 (en) | Method and system for object prediction | |
| CN104754073A (en) | Resource access method and device | |
| CN102025794B (en) | Domain name resolution method, DNS (Domain Name Server) server and system | |
| US20070239732A1 (en) | Method and system for providing improved URL mangling performance using fast re-write | |
| CN102855334B (en) | A kind of browser and the method obtaining dns resolution data thereof | |
| WO2014048241A1 (en) | Browser and domain name resolution method thereof | |
| US7305479B1 (en) | Methods and apparatus for delivery of content requests within a content delivery network | |
| CN105022750A (en) | Resource file loading method and apparatus | |
| US20160191606A1 (en) | Ios device based webpage blocking method and device | |
| CN104980446A (en) | Detection method and system for malicious behavior | |
| KR101172885B1 (en) | Apparatus and method for providing device profile using device identifier | |
| CN110809070A (en) | Website domain name resolution record processing method and device, electronic equipment and storage medium | |
| CN105279156A (en) | Network information communication method and network information browsing device | |
| CN111191156B (en) | Network request resource scheduling method, device and computer readable storage medium | |
| CN108762807B (en) | H5 page analysis method based on strongly-separated solenoid | |
| CN110572485A (en) | Domain name resolution method, device and system |
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 |