WO2015179244A1 - Procédé et système d'acquisition de pages web - Google Patents

Procédé et système d'acquisition de pages web Download PDF

Info

Publication number
WO2015179244A1
WO2015179244A1 PCT/US2015/031153 US2015031153W WO2015179244A1 WO 2015179244 A1 WO2015179244 A1 WO 2015179244A1 US 2015031153 W US2015031153 W US 2015031153W WO 2015179244 A1 WO2015179244 A1 WO 2015179244A1
Authority
WO
WIPO (PCT)
Prior art keywords
web page
address
domain name
gslb
referenced content
Prior art date
Application number
PCT/US2015/031153
Other languages
English (en)
Inventor
Shanyuan GAO
Original Assignee
Alibaba Group Holding Limited
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority claimed from CN201410213336.6A external-priority patent/CN105100294B/zh
Application filed by Alibaba Group Holding Limited filed Critical Alibaba Group Holding Limited
Priority to EP15728677.4A priority Critical patent/EP3146698B1/fr
Publication of WO2015179244A1 publication Critical patent/WO2015179244A1/fr

Links

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/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • 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/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/561—Adding application-functional data or data for application control, e.g. adding metadata

Definitions

  • the present application relates to a method and a system for acquiring web pages.
  • CDN Content Delivery Network
  • the CDN publishes content of a web page to the network "edge" that is closest to a user. Consequently, the user can obtain web page content from a closer web server, which increases a response speed in accessing the web page.
  • web pages are typically composed of web page basic frameworks and web page-referenced content (such as cascading style sheets (CSS), JavaScript, photographs, video, etc.).
  • CSS cascading style sheets
  • the web page-referenced content uses different domain names than the web page basic frameworks.
  • the different web page-referenced content uses different domain names.
  • the domain names of the web page-referenced content include static.excdn.cn, img01.excdn.cn, img02.excdn.cn, js.excdn.cn, and vedio.excdn.cn. Therefore, conventionally, when a web page is acquired, the web page basic framework constituting the web page is acquired based on a domain name of the web page basic framework, and each web page-referenced content forming the web page is acquired based on a domain name of the each web page-referenced content constituting the web page.
  • FIG. 1 is a flowchart of a conventional process for acquiring web pages.
  • the conventional process includes the following: a browser acquires a web page domain name (e.g., www.example.com) of a to-be-accessed web page. After finding that a present location (the browser itself and the operating system (OS)) has not cached an Internet Protocol (IP) address corresponding to the web page domain name, the browser sends a domain name resolution request including the web page domain name to a local Domain Name Server (DNS) (1 A). The local DNS receives the domain name resolution request.
  • a web page domain name e.g., www.example.com
  • IP Internet Protocol
  • DNS local Domain Name Server
  • the IP address corresponding to the web page domain name is acquired through a root DNS and a global server load balancer (GSLB), and the IP address corresponding to the web page domain name is sent back to the browser (IB).
  • the browser uses the received IP address corresponding to the web page domain name to establish a connection with the web server for the to-be-accessed web page and sends a hypertext transfer protocol (HTTP) request including the IP address to the web server (2A).
  • HTTP hypertext transfer protocol
  • the web server receives the HTTP request and sends a web page basic framework (2B) corresponding to the IP address back to the browser.
  • the browser receives the web page basic framework sent back by the web server, analyzes the web page basic framework, obtains domain names of multiple web page-referenced content, issues domain name resolution requests including the domain names of the web page-referenced content (each domain name resolution request including a domain name of one corresponding web page-referenced content), and obtains the IP addresses of the web page- referenced content (similar to 1A and IB).
  • the browser requests web page-referenced content from the corresponding web page-referenced content server (such as an image-referenced content server) (3 A) based on the IP address of the web page-referenced content.
  • the web page-referenced content server sends the web page-referenced content back to the browser (3B).
  • Operations 1 A, IB, 3A, and 3B can be repeated several times.
  • the operations can be repeated as many times as the domain names of the web page-referenced content exist.
  • the browser acquires all the web page-referenced content included in the to-be-accessed web page.
  • the browser combines all the web page- referenced content with the web page basic framework to obtain the web page.
  • FIG. 1 is a flowchart of a conventional process for acquiring web pages.
  • FIG. 2 is a flowchart of an embodiment of a process for acquiring web pages.
  • FIG. 3 is a flowchart of another embodiment of a process for acquiring web pages.
  • FIG. 4 is a flowchart of an embodiment of a process for acquiring a first IP address corresponding to a web page domain name of a to-be-accessed web page.
  • FIG. 5 is a flowchart of an embodiment of a process for acquiring a first IP address corresponding to a web page domain name and a global server load balancer address after the local DNS has received a domain name resolution request.
  • FIG. 6 is a functional block diagram of an embodiment of a process for acquiring web pages.
  • FIG. 7 is a flowchart of an embodiment of a process for resolving a domain name.
  • FIG. 8A is a structural diagram of an embodiment of a web server for acquiring web pages.
  • FIG. 8B is a structural diagram of an embodiment of a first sending module.
  • FIG. 9 A is a structural diagram of an embodiment of a browser for acquiring web pages.
  • FIG. 9B is a structural diagram of an embodiment of a second acquiring module.
  • FIG. 9C is a structural diagram of an embodiment of a third sending module.
  • FIG. 10 is a structural diagram of an embodiment of a Global Server Load Balancer for acquiring web pages.
  • FIG. 11 is a structural diagram of another embodiment of a Global Server Load
  • FIG. 12 is a functional diagram illustrating an embodiment of a programmed computer system for acquiring web pages.
  • the invention can be implemented in numerous ways, including as a process; an apparatus; a system; a composition of matter; a computer program product embodied on a computer readable storage medium; and/or a processor, such as a processor configured to execute instructions stored on and/or provided by a memory coupled to the processor.
  • these implementations, or any other form that the invention may take, may be referred to as techniques.
  • the order of the steps of disclosed processes may be altered within the scope of the invention.
  • a component such as a processor or a memory described as being configured to perform a task may be implemented as a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task.
  • the term 'processor' refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.
  • FIG. 2 is a flowchart of an embodiment of a process for acquiring web pages.
  • the process 100 is implemented by the web server 720 of FIG. 7 and comprises:
  • the server acquires an HTTP request including a first IP address.
  • the HTTP request is issued by a browser executing on a device after the browser acquires the first IP address corresponding to a web page domain name of a to-be- accessed web page.
  • a browser is discussed extensively for purposes of example; however, other applications such as standalone applications implementing a browser core or similar functions can also be used to issue the HTTP request.
  • the HTTP request includes a GSLB address.
  • a GSLB is a load balancer used to balance load among content servers from different regions in a CDN.
  • the GSLB selects a server to service the customer based on distance to the server.
  • the HTTP request can be a request sent in operation 2 of FIG. 7.
  • the HTTP request corresponds to GET http://www.example.cn/ HTTP/1.0.
  • the acquiring of the HTTP request including the first IP address comprises: acquiring an HTTP request including a first IP address and a GSLB address.
  • the GSLB address can correspond to the GSLB address used by the browser to obtain the first IP address corresponding to the web page domain name of the to-be-accessed web page.
  • the browser In the process of acquiring the first IP address corresponding to the web page domain name of the to-be-accessed web page, the browser records the GSLB address that is being used, and then includes the GSLB address in an HTTP request, and sends the HTTP request to the present location.
  • the present location is a location from which the HTTP request was initiated, such as the true IP address of the browser. .
  • the server looks up a web page basic framework corresponding to the first IP address.
  • the web page basic framework refers to a framework (e.g., a HyperText Markup Language (HTML) file) that when executed obtains additional web page content and forms a web page using the content.
  • HTML HyperText Markup Language
  • corresponding relationships between IP addresses and web page basic frameworks are set up in advance. After the first IP address is acquired, the web page basic framework corresponding to the first IP address is obtained by looking up a pre-established correspondence between the IP address and the web page basic framework.
  • the server analyzes the web page basic framework and obtains domain names of web page-referenced content corresponding to the first IP address.
  • the web page basic framework includes locations of various content specified by the web page.
  • the web page cannot be obtained until the web page basic framework has been combined with the web page-referenced content.
  • the one or more domain names of the web page-referenced content that is to be used in the web page basic framework can be obtained by analyzing the web page basic framework.
  • the domain names of the web page-referenced content include img01.excdn.cn, img02.excdn.cn, static.excdn.cn, etc.
  • the server sends a domain name resolution request to a global server load balancer (GSLB), the domain name resolution request including the one or more domain names of the web page-referenced content.
  • GSLB global server load balancer
  • the domain name resolution request after receiving the domain name resolution request, the domain name resolution request.
  • the GSLB resolves the one or more domain names of the web page-referenced content. For each web page-referenced content, based on a local CDN's IP address and the GSLB's own scheduling algorithm, the GSLB obtains a second IP address of each web page-referenced content
  • the second IP address is obtained among a plurality of available IP addresses of CDN servers storing the content, selected by the GSLB using a known scheduling algorithm such as round robin or weighted round robin to load balance the CDN servers.
  • the domain name resolution request can also include a user IP address of the browser that issued the HTTP request.
  • the GSLB receives the domain name resolution request, resolves the one or more domain names of the web page-referenced content, and combines the user IP address and the GSLB's own scheduling algorithm to obtain a second IP address of each web page-referenced content corresponding to a domain name for each web page- cited content among the one or more domain names of the web page-cited content.
  • the GSLB uses a scheduling algorithm (e.g., round robin or weighted round robin) to select an appropriate second IP address.
  • the GSLB uses the true IP address of the user as a key to find the second IP addresses for the domain (e.g.,
  • the present location can transmit the true IP address of the user's browser to the GSLB.
  • the true IP address of the user is included in the HTTP request.
  • the GSLB performs one or more resolutions in combination with the user IP address.
  • the second IP address (i.e., the IP address that is closest to the user network "edge") for each web page-referenced content can be obtained. Because the resolution result, i.e., the second IP address of each piece of web page-referenced content, is resolved based on the true IP address of the user, the uncertainty involved in the conventional process is eliminated when a local DNS IP address is sent to a GSLB for reference and resolution.
  • the sending of the domain name resolution request to the GSLB comprises: sending a domain name resolution request to the GSLB corresponding to the GSLB address.
  • the sending of the domain name resolution request to the global load balancer comprises: looking up local GSLB configuration information and obtaining the GSLB address corresponding to the present location, the GSLB configuration information including the GSLB address corresponding to the present location, and then sending a domain name resolution request to the GSLB corresponding to the found GSLB address.
  • the GSLB configuration information can be set up in advance locally, and the GSLB address corresponding to the present location can be obtained by looking up the local GSLB configuration information.
  • the sending of a domain name resolution request to the global load balancer comprises:
  • GSLB global load balancer
  • EDNS Extension Domain Name System
  • HTTP Hypertext Transfer Protocol
  • the server acquires a second IP address from the GSLB for the web page- referenced content.
  • a second IP address is received from the GSLB for each web page-referenced content.
  • the server sends the web page basic framework and the second IP address for the web page-cited content to the browser, causes the browser to acquire the web page and display the web page.
  • the web page basic framework and the second IP address of the web page-referenced content can be packaged into the HTTP response sent back to the browser.
  • the second IP address of a piece of web page-referenced content img01.excdn.cn can be 223.5.6.7
  • the second IP address of another piece of web page referenced content img02.execdn.cn can be 223.5.6.8 or 223.5.6.9.
  • the second IP addresses of the web page-referenced content can be packaged in a self-defined HTTP header, e.g., X-GSLB-INFO: img01.excdn.cn,60,A,223.5.6.7;img02.excdn.cn,60,A,223.5.6.8
  • semicolons (;) can be used to divide up multiple resolution results
  • commas (,) can be used to divide up multiple fields within a single resolution result.
  • the fields in the above example are, in order: domain name, time to live (TTL), record type, and resolution result.
  • ) can be used to divide multiple resolution results. Any other feasible approach may be employed with no limitation imposed in this regard.
  • the second IP address of img01.excdn.cn is 223.5.6.7
  • the second IP address of img02.excdn.cn is 223.5.6.8 or 223.5.6.9.
  • the web page basic framework and the second IP address(es) of the web page-referenced content are packaged into the HTTP response that is sent back to the browser.
  • the browser can extract the web page basic framework and the second IP address(es) of the web page-referenced content from the HTTP response using a browser plugin, an ActiveX plugin, a client proxy, etc.
  • the extracted web page basic framework and the second IP address of each web page-referenced content can be stored in a browser DNS cache, an operating system DNS cache, a host file, etc.
  • the extraction component e.g., a browser plugin, an ActiveX plugin, a client proxy, etc.
  • the browser plugin, the ActiveX plugin, the client proxy, etc. can acquire the second IP address of each web page-referenced content from the browser DNS cache, the operating system DNS cache, the host file, etc. and directly send the request to the corresponding second IP addresses and skip the DNS resolution process.
  • the browser acquires each web page-referenced content from each web page-referenced content server corresponding to the second IP address of each web page- referenced content and combines the web page basic framework with each web page-referenced content to obtain the web page.
  • the process 100 includes: after acquiring an HTTP request including a first IP address, the server obtains one or more domain names of the web page-referenced content corresponding to the first IP address, and sends a domain name resolution request directly to a global server load balancer (GSLB).
  • GSLB global server load balancer
  • the server is not required to issue multiple domain name resolution requests. Rather, the server may send the resolved second IP addresses to the browser in a single HTTP response header or a webpage that is sent in response.
  • the time for acquiring the web page- referenced content is reduced, which increases web page acquisition efficiency and speeds up web page loading. Scheduling based on the true IP address of the user greatly increases scheduling accuracy.
  • DNS resolution is performed through a web server instead of through the traditional client model. Typically, the resolution time between the web server and the GSLB will be less than a client-issued resolution time, and web page loading speed is increased.
  • FIG. 3 is a flowchart of another embodiment of a process for acquiring web pages.
  • the process 200 is implemented by the browser 710 of FIG. 7 and comprises:
  • the browser acquires a first IP address corresponding to a web page domain name of a to-be-accessed web page.
  • the browser sends an HTTP request including the first IP address to a web server.
  • the web server After receiving the HTTP request, the web server looks up the web page basic framework corresponding to the first IP address, analyzes the web page basic framework, obtains one or more domain names for web page-cited content corresponding to the first IP address, and sends a domain name resolution request to a global load balancer (GSLB), the domain name resolution request including the one or more domain names of the web page- referenced content.
  • GSLB global load balancer
  • the domain name resolution request after receiving the domain name resolution request, the
  • GSLB resolves the one or more domain names of the web page-referenced content and combines a local CDN IP address with the GSLB's own scheduling algorithm to obtain a second IP address of the web page -referenced content corresponding to a domain name for each web page-referenced content among the one or more domain names of the web page-referenced content.
  • the domain name resolution request also includes the local user IP address. Accordingly, after the GSLB receives the domain name resolution request, the GSLB resolves the domain names of the web page-referenced content, combines the user IP address with the GSLB's own scheduling algorithm, and obtains an IP address of each web page- referenced content corresponding to a domain name for each web page-referenced content among the domain names of the web page-referenced content.
  • the browser receives a web page basic framework sent by the web server and a second IP address for each GSLB-obtained web page-referenced content forwarded by the web server.
  • the browser acquires each web page-referenced content from each web page- referenced content web server corresponding to the second IP address of each web page-referenced content, and combines the web page basic framework with each web page-referenced content to obtain the web page.
  • FIG. 4 is a flowchart of an embodiment of a process for acquiring a first IP address corresponding to a web page domain name of a to-be-accessed web page.
  • the process 2100 is an implementation of operation 210 of FIG. 3 and comprises:
  • the browser acquires the web page domain name of the to-be-accessed web page.
  • the web page domain name is acquired when the user enters the web page domain name into the browser or otherwise selects the web page domain name from a link, bookmark, etc.
  • the browser determines whether the first IP address corresponding to the web page domain name and the GSLB address have been cached locally. In the event that either the first IP address or the GSLB address have not been cached locally, control is passed to operation 2130; otherwise, control is passed to operation 2150.
  • the browser sends a domain name resolution request including the web page domain name to a local DNS to cause the local DNS to acquire the first IP address
  • the local DNS is typically configured by an operator of the network to be used by the user.
  • FIG. 5 is a flowchart of an embodiment of a process for acquiring a first IP address corresponding to a web page domain name and a global server load balancer address after the local DNS has received a domain name resolution request.
  • the process 21300 is an implementation of operation 2130 of FIG. 4 and comprises:
  • the local DNS determines whether the first IP address corresponding to the web page domain name and the GSLB address have been locally cached. In the event that the first IP address and the GSLB address have been locally cached, control is passed to operation 21320; otherwise, control is passed to operation 21340.
  • the local DNS determines whether the cached first IP address
  • the local DNS sends the cached first IP address corresponding to the web page domain name and the GSLB address back to the present location (for example, the browser).
  • the local DNS sends a domain name resolution request including the web page domain name to a root domain name server (root DNS) and acquires an authoritative name server through the root domain name server.
  • root DNS root domain name server
  • the root domain name server typically does not provide A (address) record resolution service for designated domain names, but instead sends back name server (NS) records for the relevant domain names (e.g., nsl .example.cn, ns2.example.cn for example.cn).
  • NS records are domain name server records for designating which DNS servers resolve the domain names.
  • the root domain name server instructs the local DNS to request resolution from the servers for the relevant NS records. Depending on the situation, this process can be repeated more than one time.
  • the local DNS obtains the authoritative domain name server for the final service (e.g., example.cn).
  • the local DNS obtains the GSLB IP address through the authoritative domain name server.
  • the first IP address corresponding to the web page domain name can be obtained by the GSLB resolving the web page domain name included in the domain name resolution request.
  • the authoritative name server can designate itself as the GSLB, or can designate another server as the GSLB.
  • the GSLB performs load balancing among multiple CDN nodes and locates a CDN node which is optimal for accessing the web page based on the IP address of the request source (the IP address of the local DNS) or the client IP address.
  • the GSLB takes the IP address of the located CDN node as the IP address corresponding to the web page domain name.
  • the local DNS sends the GSLB IP address that was obtained through the authoritative domain name server and the first IP address that corresponds to the web page domain name and that was obtained by the GSLB back to the present location. Moreover, the local DNS caches the GSLB IP address and the first IP address corresponding to the web page domain name in the local DNS.
  • the GSLB IP address and the first IP address corresponding to the web page domain name are cached in the local DNS for use by the next same query request.
  • the browser receives the first IP address corresponding to the web page domain name and the GSLB address, which are sent back by the local DNS.
  • the browser sends an HTTP request including the first IP address to the web server.
  • the web server looks up a web page basic framework corresponding to the first IP address, analyzes the web page basic framework, obtains domain names for web page-referenced content corresponding to the first IP address, and sends a domain name resolution request to the global load balance server (GSLB).
  • GSLB global load balance server
  • the browser sends an HTTP request including the first IP address and the GSLB address to the web server.
  • the web server looks up the web page basic framework corresponding to the first IP address, analyzes the web page basic framework, obtains domain names for the web page-referenced content corresponding to the first IP address, and sends a domain name resolution request to the global load balance server (GSLB) corresponding to the GSLB address.
  • GSLB global load balance server
  • the browser determines whether the locally cached first IP address corresponding to the web page domain name and the GSLB address are valid. In the event that the locally cached first IP address corresponding to the web page domain name and the GSLB address are valid, control is passed to operation 2160; otherwise, control is passed to operation 2130.
  • a web page domain name or GSLB address being valid corresponds to a record existing for the web page domain name or GSLB address and a time to live (TTL) being more than 0.
  • TTL time to live
  • the browser first determines whether a first IP address record corresponding to the web page domain name has been cached in the local browser DNS cache. In the event that the first IP address record has been cached, the browser determines whether the cached first IP address corresponding to the web page domain name is valid. In the event that the cached first IP address corresponding to the web page domain name is valid, control is passed to operation 2160.
  • the browser determines, based on the operating system, whether a record of the first IP address corresponding to the web page domain name has been cached in the host file (e.g., in a Linux operating system: /etc/hosts, in a Windows operating system:
  • %SystemRoot% ⁇ system32 ⁇ drivers ⁇ etc ⁇ hosts of the local operating system.
  • the browser determines whether the cached first IP address corresponding to the web page domain name is valid. In the event that the cached first IP address corresponding to the web page domain name is valid, control is passed to operation 2160. In the event that the first IP address corresponding to the web page domain name has not been cached in the host file of the local operating system, or the cached first IP address corresponding to the web page domain name is invalid, then control is passed to operation 2130.
  • the browser acquires the locally cached first IP address corresponding to the web page domain name and the GSLB address.
  • the browser sends an HTTP request including the first IP address to a web server.
  • the web server looks up a web page basic framework corresponding to the first IP address, analyzes the web page basic framework, obtains domain names for web page- referenced content corresponding to the first IP address, and sends a domain name resolution request to a global load balance server (GSLB).
  • GSLB global load balance server
  • the browser sends the HTTP request including the first IP address and GSLB address to the web server.
  • the web server looks up the web page basic framework corresponding to the first IP address, analyzes the web page basic framework, obtains the domain names for the web page-referenced content corresponding to the first IP address, and sends the domain name resolution request to the global load balance server (GSLB) corresponding to the GSLB address.
  • GSLB global load balance server
  • the process 200 for acquiring web pages includes: when the web page includes multiple web page-referenced content, issuing multiple domain name resolution requests is not needed. Time to acquire the web page-referenced content is reduced, which increases web page acquisition efficiency and can speed up web page loading. Scheduling is performed based on the true IP address of the user, which greatly increases scheduling accuracy. DNS resolution is performed through a web server instead of through the traditional client model. Typically, resolution time between the web server and the GSLB will be less than the time associated with client-issued resolution. Web page loading speed can be increased.
  • FIG. 6 is a functional block diagram of an embodiment of a process for acquiring web pages.
  • the process 300 is implemented by the GSLB 730 of FIG. 7 and comprises:
  • the GSLB receives a domain name resolution request, the domain name resolution request including domain names of web page-referenced content in a to-be-accessed web page and a user IP address of a browser corresponding to the to-be-accessed web page.
  • the GSLB resolves the domain names of the web page-referenced content, and combines the user IP address with the present location's own scheduling algorithm to obtain a second IP address of each web page-referenced content corresponding to a domain name for each web page-referenced content among the domain names of the web page-referenced content.
  • the GSLB After obtaining the second IP address of each web page-referenced content corresponding to the domain name for the each web page-referenced content among the domain names of the web page-referenced content, the GSLB sends the second IP address of each web page-referenced content corresponding to the domain name of each web page-referenced content to a web server, causes the web server to send the second IP address of each web page-referenced content and the web page basic framework corresponding to the first IP address to the browser, the first IP address corresponding to the web page domain name of the to-be-accessed web page, and causes the browser to acquire the web page and display the acquired web page.
  • the process 300 for resolving domain name web pages includes: when the web page includes multiple web page-referenced content, issuing domain name resolution requests on multiple occasions is not necessary. Acquiring the web page-referenced content takes less time, which increases web page acquisition efficiency and can speed up web page loading. Scheduling, based on the true IP address of the user, greatly increases scheduling accuracy. DNS resolution is achieved through a web server instead of through the traditional client model. Typically, the resolution time between the web server and the GSLB is less than the time associated with client- issued resolution, and web page loading speed can be increased.
  • FIG. 7 is a flowchart of an embodiment of a process for resolving a domain name.
  • the process 700 is performed by a browser 710, a web server 720, a GSLB 730, and a web page application content server 740.
  • a browser 710 issues a normal domain name resolution request for a web page (e.g., www.example.cn) to complete the domain name resolution process via a GSLB 730.
  • a web page e.g., www.example.cn
  • browser 710 sends a domain name resolution request that has the form of a DNS request, for example, "www.example.cn IN A" to GSLB 730 (IB).
  • the GSLB returns a domain name resolution result that has the form of a DNS Answer Message, for example,
  • browser 710 issues an HTTP request to a web server (2) based on the domain name resolution result sent back by the DNS or GSLB. For example, browser 710 issues an HTTP request that has the form of "GET
  • the web server 720 based on its own configuration files, the web page content requiring service, and other such information, looks up a web page basic framework, obtains domain names of web page application content (e.g., img01.excdn.cn, img02.excdn.cn, static.excdn.cn, etc.), and issues, based on EDNS, HTTP, or other such approach, a domain name resolution request including the domain names of the web page-referenced content to the GSLB 730.
  • domain names of web page application content e.g., img01.excdn.cn, img02.excdn.cn, static.excdn.cn, etc.
  • the web server 720 can also include the true IP address of the user in the domain name resolution request and send the domain name resolution request to the GSLB 730 (3A).
  • An example of such a domain name resolution request using the true IP address of 10.1.1.2. of the user (3A) is GET /imgOl . excdn.cn HTTP/l . l ⁇ r ⁇ nClient-IP: 10.1.1.2.
  • the GSLB integrating the user's true IP address conveyed by the web server with its own scheduling algorithm, sends the resolution result back to the web server 720 (3B).
  • An example of such a resolution result (3B) is img01.excdn.cn,60,A,223.5.6.7.
  • the web server 720 sends the resolution result back to the browser 710 (4).
  • An example of the result being returned (4) is X-GSLB-INFO: img01.excdn.cn,60,A,223.5.6.7;img02.excdn.cn,60,A,223.5.6.8
  • the browser 710 directly issues a request (5 A) to a network application content server 740 (such as an image web server) based on the relevant resolution result in the web page and receives a response (5B).
  • An example of the request (5 A) issued by the browser corresponds to a conventional request, and an example of the response that is received (5B) corresponds to a conventional response. Conducting multiple DNS resolutions for multiple relevant domain names is no longer needed.
  • FIG. 8 A is a structural diagram of an embodiment of a web server for acquiring web pages.
  • the web server 400 is configured to perform process 100 of FIG. 2 and comprises: a first acquiring module 410, a querying module 420, a first sending module 430, a processing module 440, and a second sending module 450.
  • the first acquiring module 410 acquires a hypertext transfer protocol (HTTP) request including a first network protocol (IP) address.
  • HTTP hypertext transfer protocol
  • IP network protocol
  • the querying module 420 looks up a web page basic framework corresponding to the first IP address, analyzes the web page basic framework, and obtains domain names of web page-referenced content corresponding to the first IP address.
  • the first sending module 430 sends a domain name resolution request to a global server load balancer (GSLB), the domain name resolution request including the domain names of the web page-referenced content.
  • GSLB global server load balancer
  • the processing module 440 acquires, from the GSLB, a second IP address of each web page-referenced content.
  • the second IP address of the each web page-referenced content corresponds to a domain name for each web page-referenced content among the domain names of the web page-referenced content.
  • the second sending module 450 sends a web page basic framework and the second IP address of each web page-referenced content to a browser to cause the browser to acquire the web page and to display the acquired web page.
  • the first acquiring module 410 is further configured to acquire the HTTP request including the first IP address and the GSLB address.
  • FIG. 8B is a structural diagram of an embodiment of a first sending module.
  • the first sending module 4300 is an implementation of the first sending module 430 of FIG. 8A and comprises: a first sending unit 4310, a first querying unit 4320, a second sending unit 4330, a third sending unit 4340, and a processing unit 4350.
  • the first sending unit 4310 sends a domain name resolution request to the GSLB corresponding to the GSLB address.
  • the first querying unit 4320 looks up local GSLB
  • the GSLB configuration information includes the GSLB address corresponding to the present location.
  • the second sending unit 4330 sends a domain name resolution request to the GSLB corresponding to the GSLB address.
  • the third sending unit 4340 sends the domain name resolution request to the GSLB based on an extended domain name server (EDNS) or HTTP.
  • EDNS extended domain name server
  • the HTTP request is issued by the browser after the browser acquires a first IP address corresponding to a web page domain name of the to-be-accessed web page.
  • the processing unit 4350 sends a domain name resolution request to the global load balancer (GSLB).
  • the domain resolution request includes domain names of the web page-referenced content, and after issuing the user IP address of the browser of the HTTP request with the result that the GSLB receives the domain name resolution request, resolving the domain names of all web page-referenced content, and combining the user IP address with the GSLB's own scheduling algorithm, the processing unit 4350 obtains a second IP address of each web page-referenced content corresponding to a domain name for each web page-referenced content among the domain names of the web page-referenced content.
  • one of the functions of a web server which is also called a WWW (World Wide Web) server, is to provide online information browsing services.
  • Original content handlers original content parsers
  • content handlers content parsers
  • GSLB clients final content handlers
  • final content parsers can be set up in the web server.
  • the functions of the first acquiring module and the querying module in looking up the web page basic framework corresponding to the first IP address are implemented through an original content handler; the query module's function includes analyzing the web page basic framework to obtain the domain names of the web page-referenced content corresponding to the first IP address implemented through a content handler; the functions of the first sending module and the functions of the processing module are implemented through a GSLB client; and the functions of the second sending module are implemented through a final content handler.
  • the web server includes: when the web page includes multiple web page-referenced content, issuing multiple domain name resolution requests is not needed. Acquiring the web page- referenced content takes less time, which increases web page acquisition efficiency and can speed up web page loading. Scheduling is based on the true IP address of the user, which greatly increases scheduling accuracy. DNS resolution is achieved through a web server instead of through the traditional client model. Typically, resolution time between the web server and the GSLB will be less than the time associated with client-issued resolution, and web page loading speed can be increased.
  • FIG. 9 A is a structural diagram of an embodiment of a browser for acquiring web pages.
  • the browser 500 implements the process 200 of FIG. 3 and comprises: a second acquiring module 510, a third sending module 520, a first receiving module 530, and a combining module 540.
  • the second acquiring module 510 acquires a first IP address corresponding to a web page domain name of a to-be-accessed web page. [0110] In some embodiments, after sending an HTTP request for the first IP address to a web server with the result that the web server receives the HTTP request, the third sending module 520 looks up the web page basic framework corresponding to the first IP address, analyzes a web page basic framework, obtains domain names for web page-referenced content corresponding to the first IP address, and sends a domain name resolution request to the global load balancer (GSLB), the domain name resolution request including the domain names of the web page-referenced content.
  • GSLB global load balancer
  • the first receiving module 530 receives a web page basic framework sent by the web server and a second IP address of each web page-referenced content forwarded by the web server and obtained by the GSLB, the second IP address of each web page- referenced content corresponding to a domain name for each web page-referenced content among the domain names of the web page-referenced content.
  • the combining module 540 acquires the each web page- referenced content from each web page-referenced content server corresponding to the second IP address of the each web page-referenced content, and combines the web page basic framework with the each web page-referenced content to obtain a web page.
  • FIG. 9B is a structural diagram of an embodiment of a second acquiring module.
  • the second acquiring module 5100 is an implementation of the second acquiring module 510 of FIG. 9A and comprises: a second acquiring unit 5110, a second querying unit 5120, a fourth sending unit 5130, a receiving unit 5140, an assessing unit 5150, and a third acquiring unit 5160.
  • the second acquiring unit 5110 acquires the web page domain name of the to-be-accessed web page.
  • the second querying unit 5120 determines whether the first
  • IP address corresponding to the web page domain name and the GSLB address have been locally cached.
  • the fourth sending unit 5130 in the event that the query result of the second querying unit 5120 is not cached, sends a domain name resolution request including the web page domain name to the local domain name server (DNS), causes the local DNS to acquire the first IP address corresponding to the web page domain name and a GSLB address after the local DNS has received the domain name resolution request.
  • DNS local domain name server
  • the receiving unit 5140 receives the first IP address corresponding to the web page domain name and the GSLB address, which are sent back by the local DNS.
  • FIG. 9C is a structural diagram of an embodiment of a third sending module.
  • the third sending module 5200 is an implementation of the third sending module 520 of FIG. 9A and comprises: a fifth sending unit 5210.
  • the fifth sending unit 5210 sends an HTTP request including the first IP address and the GSLB address to the web server.
  • the web server looks up the web page basic framework corresponding to the first IP address, analyzes the web page basic framework, obtains domain names for the web page- referenced content corresponding to the first IP address, and sends a domain name resolution request to the global load balance server (GSLB) corresponding to the GSLB address.
  • GSLB global load balance server
  • the assessing unit 5150 determines whether the locally cached first IP address corresponding to the web page domain name and the GSLB address are valid.
  • the third acquiring unit 5160 if the assessment result of the assessing unit 5150 is valid, acquires the locally cached first IP address corresponding to the web page domain name and the GSLB address.
  • the third sending module 5200 further comprises a sixth sending unit 5220.
  • the sixth sending unit 5220 sends an HTTP request including the first IP address and the GSLB address to the web server.
  • the web server looks up the web page basic framework corresponding to the first IP address, analyzes the web page basic framework, obtains domain names for all web page- referenced content corresponding to the first IP address, and sends a domain name resolution request to the global load balance server (GSLB) corresponding to the GSLB address.
  • GSLB global load balance server
  • the 5100 further comprises a notifying unit 5170.
  • the notifying unit 5170 if the assessment result of the assessing unit 5150 is not valid, notifies the fourth sending unit 5130 to send a domain name resolution request including the web page domain name to the local DNS.
  • GSLB handlers GSLB Parse
  • DNS cache domain name caches
  • the functions of the first receiving module and the combining module can be implemented through a GSLB handler.
  • the first IP address that was obtained by the second acquiring module and that corresponds to the web page domain name of the to-be-accessed web page can be cached in the domain name cache.
  • the functions of the second acquiring module and the third sending module are implemented through a traditional domain name client (traditional DNS client) (including DNS resolving and caching modules in the client operating system) in the client computer.
  • DNS client traditional domain name client
  • the client computer can use an operating system such as Windows, Linux, Mac OS, iOS, Android, etc.
  • the browser is run on the client computer.
  • the browser 500 as described includes: when the web page includes multiple web page-referenced content, issuing multiple domain name resolution requests is not required.
  • FIG. 10 is a structural diagram of an embodiment of a Global Server Load Balancer for acquiring web pages.
  • the global server load balancer (GSLB) 600 implements the process 300 of FIG. 6 and comprises: a second receiving module 610 and a resolving module 620.
  • the second receiving module 610 receives a domain name resolution request, the domain name resolution request including domain names of web page- referenced content in a to-be-accessed web page and a user IP address of a browser corresponding to the to-be-accessed web page.
  • the resolving module 620 resolves the domain names of the web page-referenced content, and combines the user IP address with the present location's own scheduling algorithm to obtain the second IP address of each web page-referenced content corresponding to a domain name for each web page-referenced content among the domain names of the web page-referenced content.
  • FIG. 11 is a structural diagram of another embodiment of a Global Server Load
  • the global load balancer (GSLB) 900 implements the process 300 of FIG. 6 and comprises: a second receiving module 910, a resolving module 920, and a fourth sending module 930.
  • the second receiving module 910 and the resolving module are identical to each other.
  • the fourth sending module 930 sends the second IP address of each web page-referenced content corresponding to a domain name of each web page-referenced content to a web server, causes the web server to send the second IP address of each web page- referenced content and the web page basic framework corresponding to the first IP address to a browser, the first IP address corresponding to the web page domain name of the to-be-accessed web page, and causes the browser to acquire the web page and display the web page.
  • GSLBs achieve traffic scheduling on wide-area networks (including the Internet) between servers in different areas.
  • the GSLBs ensure access quality by guaranteeing that a client uses nearest optimal server services.
  • a scheduling policy database (policy DB) (scheduling policy databases include scheduling algorithms) and a HTTPDNS processor or EDNS processor is set up in a GSLB.
  • the functions of the second receiving module, the resolving module, and the fourth sending module can be implemented through the HTTPDNS processor or the EDNS processor.
  • the described GSLB when the web page contains multiple web page-referenced content, does not need to issue multiple domain name resolution requests. Acquiring the web page- referenced content takes less time, which increases web page acquisition efficiency and can speed up web page loading. Scheduling is based on the true IP address of the user, which greatly increases scheduling accuracy. DNS resolution is achieved through a web server instead of through the traditional client model. Typically, the resolution time between the web server and the GSLB will be less than the time associated with client-issued resolution, and web page loading speed can be increased.
  • the modules and units described above can be implemented as software components executing on one or more general purpose processors, as hardware such as programmable logic devices and/or Application Specific Integrated Circuits designed to perform certain functions or a combination thereof.
  • the modules and units can be embodied by a form of software products which can be stored in a nonvolatile storage medium (such as optical disk, flash storage device, mobile hard disk, etc.), including a number of instructions for making a computer device (such as personal computers, servers, network equipment, etc.) implement the methods and units described in the embodiments of the present invention.
  • the modules and/or units may be implemented on a single device or distributed across multiple devices.
  • the functions of the modules and/or units may be merged into one another or further split into multiple sub-modules and/or sub-units.
  • FIG. 12 is a functional diagram illustrating an embodiment of a programmed computer system for acquiring web pages. As will be apparent, other computer system
  • Computer system 800 which includes various subsystems as described below, includes at least one microprocessor subsystem (also referred to as a processor or a central processing unit (CPU)) 802.
  • processor 802 can be implemented by a single-chip processor or by multiple processors.
  • processor 802 is a general purpose digital processor that controls the operation of the computer system 800. Using instructions retrieved from memory 810, the processor 802 controls the reception and manipulation of input data, and the output and display of data on output devices (e.g., display 818).
  • output devices e.g., display 818
  • Processor 802 is coupled bi-directionally with memory 810, which can include a first primary storage, typically a random access memory (RAM), and a second primary storage area, typically a read-only memory (ROM).
  • primary storage can be used as a general storage area and as scratch-pad memory, and can also be used to store input data and processed data.
  • Primary storage can also store programming instructions and data, in the form of data objects and text objects, in addition to other data and instructions for processes operating on processor 802.
  • primary storage typically includes basic operating instructions, program code, data and objects used by the processor 802 to perform its functions (e.g., programmed instructions).
  • memory 810 can include any suitable computer- readable storage media, described below, depending on whether, for example, data access needs to be bi-directional or uni-directional.
  • processor 802 can also directly and very rapidly retrieve and store frequently needed data in a cache memory (not shown).
  • a removable mass storage device 812 provides additional data storage capacity for the computer system 800, and is coupled either bi-directionally (read/write) or uni-directionally (read only) to processor 802.
  • storage 812 can also include computer-readable media such as magnetic tape, flash memory, PC-CARDS, portable mass storage devices, holographic storage devices, and other storage devices.
  • a fixed mass storage 820 can also, for example, provide additional data storage capacity. The most common example of mass storage 820 is a hard disk drive.
  • Mass storages 812, 820 generally store additional programming instructions, data, and the like that typically are not in active use by the processor 802. It will be appreciated that the information retained within mass storages 812 and 820 can be incorporated, if needed, in standard fashion as part of memory 810 (e.g., RAM) as virtual memory.
  • bus 814 can also be used to provide access to other subsystems and devices. As shown, these can include a display monitor 818, a network interface 816, a keyboard 804, and a pointing device 806, as well as an auxiliary input/output device interface, a sound card, speakers, and other subsystems as needed.
  • the pointing device 806 can be a mouse, stylus, track ball, or tablet, and is useful for interacting with a graphical user interface.
  • the network interface 816 allows processor 802 to be coupled to another computer, computer network, or telecommunications network using a network connection as shown.
  • the processor 802 can receive information (e.g., data objects or program instructions) from another network or output information to another network in the course of performing method/process steps.
  • Information often represented as a sequence of instructions to be executed on a processor, can be received from and outputted to another network.
  • An interface card or similar device and appropriate software implemented by e.g.,
  • processor 802 can be used to connect the computer system 800 to an external network and transfer data according to standard protocols. For example, various process embodiments disclosed herein can be executed on processor 802, or can be performed across a network such as the Internet, intranet networks, or local area networks, in conjunction with a remote processor that shares a portion of the processing. Additional mass storage devices (not shown) can also be connected to processor 802 through network interface 816.
  • auxiliary I/O device interface (not shown) can be used in conjunction with computer system 800.
  • the auxiliary I/O device interface can include general and customized interfaces that allow the processor 802 to send and, more typically, receive data from other devices such as microphones, touch-sensitive displays, transducer card readers, tape readers, voice or handwriting recognizers, biometrics readers, cameras, portable mass storage devices, and other computers.
  • the computer system shown in FIG. 12 is but an example of a computer system suitable for use with the various embodiments disclosed herein.
  • Other computer systems suitable for such use can include additional or fewer subsystems.
  • bus 814 is illustrative of any interconnection scheme serving to link the subsystems.
  • Other computer architectures having different configurations of subsystems can also be utilized.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

La présente invention concerne une acquisition de pages Web consistant à acquérir une requête de protocole de transfert hypertexte (HTTP) comprenant une première adresse de protocole Internet (IP), à rechercher un cadre de base de page Web correspondant à la première adresse IP, à obtenir une pluralité de noms de domaine d'une pluralité d'éléments de contenu référencé de page Web correspondant à la première adresse IP, à envoyer une requête de résolution de nom de domaine à un équilibreur de charge global (GSLB), la requête de résolution de nom de domaine comprenant la pluralité de noms de domaine de la pluralité d'éléments de contenu référencé de page Web, à acquérir une pluralité de secondes adresses IP de la pluralité d'éléments de contenu référencé de page Web, et à envoyer le cadre de base de page Web et la pluralité de secondes adresses IP de la pluralité des éléments à un navigateur.
PCT/US2015/031153 2014-05-20 2015-05-15 Procédé et système d'acquisition de pages web WO2015179244A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP15728677.4A EP3146698B1 (fr) 2014-05-20 2015-05-15 Procédé et système d'acquisition de pages web

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201410213336.6A CN105100294B (zh) 2014-05-20 2014-05-20 获取网页的方法、系统、网络服务器、浏览器和gslb
CN201410213336.6 2014-05-20
US14/712,527 US10225315B2 (en) 2014-05-20 2015-05-14 Method and system for acquiring web pages
US14/712,527 2015-05-14

Publications (1)

Publication Number Publication Date
WO2015179244A1 true WO2015179244A1 (fr) 2015-11-26

Family

ID=53385937

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/031153 WO2015179244A1 (fr) 2014-05-20 2015-05-15 Procédé et système d'acquisition de pages web

Country Status (1)

Country Link
WO (1) WO2015179244A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106301928A (zh) * 2016-08-22 2017-01-04 深圳市茁壮网络股份有限公司 一种网页解析、获取方法及装置
CN111447291A (zh) * 2018-12-29 2020-07-24 北京奇虎科技有限公司 基于dns的调度方法、系统及电子设备
CN112883072A (zh) * 2021-03-10 2021-06-01 哈尔滨工业大学（威海） 基于网络服务商国别标注的域名国家可控性评估方法
CN113366816A (zh) * 2019-04-12 2021-09-07 三星电子株式会社 通过域名服务器解析发现边缘服务器或边缘服务的方法和系统
CN114024936A (zh) * 2020-07-17 2022-02-08 北京搜狗科技发展有限公司 一种基于httpdns的dns解析方法及装置
EP3905640A4 (fr) * 2019-02-18 2022-03-02 Huawei Technologies Co., Ltd. Procédé d'ordonnancement de n?ud de périphérie de réseau de distribution de contenu, et appareil
WO2022179353A1 (fr) * 2021-02-25 2022-09-01 上海哔哩哔哩科技有限公司 Procédé et appareil de résolution de nom de domaine, et dispositif informatique

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070233851A1 (en) * 2006-03-31 2007-10-04 Cisco Technology, Inc. System and method for handling persistence information in a network
US20100131639A1 (en) * 2008-11-25 2010-05-27 Raghav Somanahalli Narayana Systems and Methods For GSLB Site Persistence
US20110202632A1 (en) * 2010-02-12 2011-08-18 Research In Motion Limited Method, system and apparatus for delivering web content

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070233851A1 (en) * 2006-03-31 2007-10-04 Cisco Technology, Inc. System and method for handling persistence information in a network
US20100131639A1 (en) * 2008-11-25 2010-05-27 Raghav Somanahalli Narayana Systems and Methods For GSLB Site Persistence
US20110202632A1 (en) * 2010-02-12 2011-08-18 Research In Motion Limited Method, system and apparatus for delivering web content

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106301928A (zh) * 2016-08-22 2017-01-04 深圳市茁壮网络股份有限公司 一种网页解析、获取方法及装置
CN111447291A (zh) * 2018-12-29 2020-07-24 北京奇虎科技有限公司 基于dns的调度方法、系统及电子设备
CN111447291B (zh) * 2018-12-29 2024-04-05 三六零科技集团有限公司 基于dns的调度方法、系统及电子设备
EP3905640A4 (fr) * 2019-02-18 2022-03-02 Huawei Technologies Co., Ltd. Procédé d'ordonnancement de n?ud de périphérie de réseau de distribution de contenu, et appareil
US11888958B2 (en) 2019-02-18 2024-01-30 Petal Cloud Technology Co., Ltd. Content delivery network CDN edge node scheduling method and device
CN113366816A (zh) * 2019-04-12 2021-09-07 三星电子株式会社 通过域名服务器解析发现边缘服务器或边缘服务的方法和系统
CN113366816B (zh) * 2019-04-12 2024-02-13 三星电子株式会社 通过域名服务器解析发现边缘服务器或边缘服务的方法和系统
US11962656B2 (en) 2019-04-12 2024-04-16 Samsung Electronics Co., Ltd. Method and system for discovering edge-server or edge-service through domain name server (DNS) resolution
CN114024936A (zh) * 2020-07-17 2022-02-08 北京搜狗科技发展有限公司 一种基于httpdns的dns解析方法及装置
WO2022179353A1 (fr) * 2021-02-25 2022-09-01 上海哔哩哔哩科技有限公司 Procédé et appareil de résolution de nom de domaine, et dispositif informatique
CN112883072A (zh) * 2021-03-10 2021-06-01 哈尔滨工业大学（威海） 基于网络服务商国别标注的域名国家可控性评估方法

Similar Documents

Publication Publication Date Title
US10225315B2 (en) Method and system for acquiring web pages
US11647096B2 (en) Method and apparatus for automatically optimizing the loading of images in a cloud-based proxy service
US9769240B2 (en) Loading of web resources
US9565265B2 (en) Method and apparatus for automatically optimizing the loading of images in a cloud-based proxy service
WO2015179244A1 (fr) Procédé et système d'acquisition de pages web
US10104037B2 (en) Method and system for network access request control
US9900328B2 (en) Web redirection for content scanning
US20150026301A1 (en) Systems, apparatus, and methods for mobile device detection
WO2021047239A1 (fr) Procédé, dispositif et système d'acquisition de page
US9672295B2 (en) Computer system
JP2018160264A (ja) バッチ最適化レンダリング及びフェッチアーキテクチャ

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15728677

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2015728677

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015728677

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE