CN111079040B - Resource sniffing method, device, terminal, server and storage medium - Google Patents
Resource sniffing method, device, terminal, server and storage medium Download PDFInfo
- Publication number
- CN111079040B CN111079040B CN201911176222.8A CN201911176222A CN111079040B CN 111079040 B CN111079040 B CN 111079040B CN 201911176222 A CN201911176222 A CN 201911176222A CN 111079040 B CN111079040 B CN 111079040B
- Authority
- CN
- China
- Prior art keywords
- loading
- domain name
- target server
- resource
- domain
- 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
Classifications
-
- 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/957—Browsing optimisation, e.g. caching or content distillation
-
- 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
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Computer Hardware Design (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The disclosure relates to a resource sniffing method, a device, an electronic device and a storage medium, wherein the method comprises the following steps: sending an access request to a target server through a first domain name; if the web page data fed back by the target server is received through the first domain name, loading the resources of other domain names of the target server through the first domain name in the process of loading the web page data, and determining the loading results of the other domain names; and feeding back the loading result to the target server so that the target server determines the available domain name according to the loading result. The domain name sniffing method and the domain name sniffing device can realize sniffing of the domain name through the browser used by the user instead of using the fixed browser or simulator, so that the domain name can be sniffed in various network environments, the accuracy of the sniffing result is improved, and the service availability is ensured.
Description
Technical Field
The present disclosure relates to internet technologies, and in particular, to a resource sniffing method, a device, a terminal, a server, and a storage medium.
Background
To cope with access to complex HTTP (S) application services, the same WEB service may be used with multiple domain names at the same time. Especially, when the sharing related service is issued, a plurality of domain names exist, but the network environment is complex, and under different regions or different browsers, the condition that a link of a domain name is hijacked by an intermediate network operator or the browser itself can occur, so that normal access cannot be performed.
In the related art, a fixed client is basically adopted to poll and access a server according to a sniffing mode of service accessibility, and for a WEB end, a real WEB browser is generally used or a WEB browser is simulated to send a request to the server, and whether the service is normal or not is judged according to whether a return result and the correctness of the return result. In the method, since a WEB browser or a simulator is used for sniffing, whether sniffing service is normal or not can be solidified only in a network environment, and the real limited situation is difficult to poll in a simulator mode, so that the sniffing result has lower accuracy.
Disclosure of Invention
The disclosure provides a resource sniffing method, a device, a terminal, a server and a storage medium, so as to at least solve the problem of low sniffing result accuracy in the related art. The technical scheme of the present disclosure is as follows:
According to a first aspect of embodiments of the present disclosure, there is provided a resource sniffing method, including:
sending an access request to a target server through a first domain name;
if the web page data fed back by the target server is received through the first domain name, loading the resources of other domain names of the target server through the first domain name in the process of loading the web page data, and determining the loading results of the other domain names;
and feeding back the loading result to the target server so that the target server determines the available domain name according to the loading result.
Optionally, in the process of loading the web page data, loading the resources of other domain names of the target server through the first domain name, and determining a loading result of the other domain names, including:
in the process of loading the webpage data, a static resource acquisition request is sent to the target server through the first domain name;
receiving static resources returned by the target server, wherein the static resources comprise domain name loading files;
in the process of loading the static resource, a file is loaded according to the domain name, and a loading request of the static resource of the appointed domain name is sent to the target server through the first domain name;
If the feedback of the target server is received, determining that the loading result of the static resource of the designated domain name is successful; and if the feedback of the target server is not received, determining that the loading result of the static resource of the designated domain name is loading failure.
Optionally, the static resource includes at least one of cascading style sheets CSS, JS, hypertext markup language HTML, and pictures.
Optionally, in the process of loading the web page data, loading the resources of other domain names of the target server through the first domain name, and determining a loading result of the other domain names, including:
under the condition of supporting cross-domain access, in the process of loading the webpage data, sending an AJAX request for a designated domain name of the target server through the first domain name;
if the feedback resource of the target server is received, loading the feedback resource, and determining that the loading result corresponding to the AJAX request of the designated domain name is successful in loading; if the feedback resource of the target server is not received, determining that the loading result corresponding to the AJAX request of the designated domain name is loading failure.
According to a second aspect of embodiments of the present disclosure, there is provided a resource sniffing method, comprising:
Receiving loading results sent by a plurality of browsers to obtain a plurality of loading results, wherein the loading results are obtained by loading resources of other domain names of a target server through a first domain name in the process of loading webpage data when the browser receives the webpage data of the target server through the first domain name;
and determining available domain names according to the plurality of loading results.
Optionally, the determining the available domain name according to the multiple loading results includes:
counting the loading results of the same domain name in the loading results;
if the loading result of one domain name meets the preset condition, determining that the domain name is unavailable; if the loading result of a domain name does not meet the preset condition, determining that the domain name is available;
the available domain names are recorded.
According to a third aspect of embodiments of the present disclosure, there is provided a resource sniffing device comprising:
the access request sending module is configured to send an access request to the target server through the first domain name;
the resource loading module is configured to load resources of other domain names of the target server through the first domain name and determine loading results of the other domain names in the process of loading the webpage data if the webpage data fed back by the target server is received through the first domain name;
And the loading result feedback module is configured to feed back the loading result to the target server so that the target server determines the available domain name according to the loading result.
Optionally, the resource loading module includes:
the static resource request unit is configured to send a static resource acquisition request to the target server through the first domain name in the process of loading the webpage data;
the static resource receiving unit is configured to receive a static resource returned by the target server, wherein the static resource comprises a domain name loading file;
the loading request generation unit is configured to send a loading request of the static resource of the designated domain name to the target server through the first domain name according to the domain name loading file in the process of loading the static resource;
the static loading result determining unit is configured to determine that the loading result of the static resource of the designated domain name is successful if the feedback of the target server is received; and if the feedback of the target server is not received, determining that the loading result of the static resource of the designated domain name is loading failure.
Optionally, the static resource includes at least one of CSS, JS, HTML and a picture.
Optionally, the resource loading module includes:
an AJAX request sending unit configured to send an AJAX request for a specified domain name of the target server through the first domain name in a process of loading the web page data in case of supporting cross-domain access;
the AJAX loading result determining unit is configured to load the feedback resource if the feedback resource of the target server is received, and determine that the loading result corresponding to the AJAX request of the designated domain name is successful in loading; if the feedback resource of the target server is not received, determining that the loading result corresponding to the AJAX request of the designated domain name is loading failure.
According to a fourth aspect of embodiments of the present disclosure, there is provided a resource sniffing device comprising:
the loading result receiving module is configured to receive loading results sent by a plurality of browsers to obtain a plurality of loading results, wherein the loading results are obtained by loading resources of other domain names of a target server through a first domain name in the process of loading the webpage data when the browser receives the webpage data of the target server through the first domain name;
and the available domain name determining module is configured to determine available domain names according to the plurality of loading results.
Optionally, the available domain name determining module includes:
the loading result statistics unit is configured to count loading results of the same domain name in the plurality of loading results;
the available domain name determining unit is configured to determine that a domain name is unavailable if the loading result of the domain name meets a preset condition; if the loading result of a domain name does not meet the preset condition, determining that the domain name is available;
and a domain name recording unit configured to record the available domain name.
According to a fifth aspect of embodiments of the present disclosure, there is provided a terminal comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the resource sniffing method as described in the first aspect.
According to a sixth aspect of embodiments of the present disclosure, there is provided a server comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the resource sniffing method as described in the second aspect.
According to a seventh aspect of embodiments of the present disclosure, there is provided a storage medium, which when executed by a processor of a terminal, enables the terminal to perform the resource sniffing method as described in the first aspect, or which when executed by a processor of a server, enables the server to perform the resource sniffing method as described in the second aspect.
According to an eighth aspect of embodiments of the present disclosure, there is provided a computer program product comprising readable program code which, when executed by a processor of a terminal, enables the terminal to perform the resource sniffing method as described in the first aspect, or which, when executed by a processor of a server, enables the server to perform the resource sniffing method as described in the second aspect.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:
according to the method and the device for the network domain name sniffing, if the access request is sent to the target server through the first domain name and the webpage data fed back by the target server are received, in the process of loading the webpage data, the resources of other domain names of the target server are loaded through the first domain name, loading results of the other domain names are determined, and the loading results are fed back to the target server, so that the target server determines available domain names according to the loading results, sniffing of the domain names can be achieved through a browser used by a user instead of a fixed browser or simulator, the domain names can be sniffed under various network environments, accuracy of the sniffing results is improved, and service availability is guaranteed.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.
FIG. 1 is a flow chart illustrating a resource sniffing method according to an exemplary embodiment;
FIG. 2 is a schematic diagram of sniffing other domain names by accessing a successful domain name in an embodiment of the present disclosure;
FIG. 3 is a flowchart illustrating a resource sniffing method, according to an example embodiment;
FIG. 4 is a flowchart illustrating a resource sniffing method, according to an example embodiment;
FIG. 5 is a flowchart illustrating a resource sniffing method, according to an example embodiment;
FIG. 6 is a block diagram of a resource sniffer device, shown according to an example embodiment;
FIG. 7 is a block diagram of a resource sniffer device, shown according to an example embodiment;
FIG. 8 is a block diagram of a terminal shown in accordance with an exemplary embodiment;
fig. 9 is a block diagram of a server, according to an example embodiment.
Detailed Description
In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
For network services actively pushed to users, the server actively issues domain names to users for access, such as a shared page similar to a spread, or a spread page similar to a WeChat friend circle. When a user accesses these domain names, due to high traffic or other factors, it is possible that the user may be hijacked by the operator to return pages that are not the user would have access to. For this situation, the accessibility of the domain name needs to be sniffed, and the embodiment of the disclosure utilizes the WEB service of the embodiment to sniff the accessibility of the same service under other domain names, and can dynamically adjust the issued available domain name according to the sniffed result so as to better ensure the availability of the WEB service.
Fig. 1 is a flowchart illustrating a resource sniffing method for performing accessibility sniffing on multiple domain names of a target server by a browser in an HTTP (S) -based browser, as shown in fig. 1, according to an exemplary embodiment.
In step S11, an access request is sent to the target server by the first domain name.
The target server is a server capable of providing target services, and one target server can correspond to a plurality of domain names.
In step S12, if the web page data fed back by the target server is received through the first domain name, in the process of loading the web page data, the resources of other domain names of the target server are loaded through the first domain name, and the loading results of the other domain names are determined.
As shown in fig. 2, when a user accesses a target server through a browser or an operator platform, a domain name to be accessed by the user is issued by the target server, and among a plurality of domain names issued by the target server, an unavailable (e.g., blocked) domain name and an available domain name may occur. As shown in fig. 2, assuming that the target server corresponds to the a domain name, the B domain name and the C domain name, if the user accesses the target server using the a domain name, the a domain name may be used to sniff whether the user can access the B domain name and the C domain name when the user successfully accesses the target server. Also, when the user accesses the target server, the issued domain name is the B domain name, then when the B domain name is available, it can be used to sniff whether the user can access the a domain name and the C domain name.
If the browser receives the webpage data fed back by the target server through the first domain name, the browser is determined to successfully access the target server through the first domain name, and the availability of the first domain name is indicated, so that other domain names corresponding to the target server can be sniffed through the first domain name in the process of loading the webpage data, namely resources of other domain names of the target server are loaded through the first domain name, and the resource accessibility condition of the other domain names of the target server is determined. Accessibility to other domain names may be sniffed by requesting resources of the other domain names from the target server. The first domain name is the domain name currently used by the browser. The browser is a browser used by a user, and is not a fixed browser and a simulator in the related art, so that the network environments where a plurality of browsers are located can be utilized to perform accessibility sniffing on the domain name of the target server respectively.
When sniffing the resource accessibility of a domain name, the loading result of the domain name can be determined by whether the feedback resource of the domain name is received, namely, if the feedback resource is received, the domain name is determined to be available, and if the feedback resource is not received, the domain name is determined to be unavailable.
In the embodiment of the disclosure, the domain name of the target server does not need to be sniffed by using a fixed browser or simulator, but the domain name of the target server is sniffed by using the browser used by the user.
In step S13, the loading result is fed back to the target server, so that the target server determines the available domain name according to the loading result.
After the browser loads the resource of one domain name and determines the loading result of the domain name, the loading result is fed back to the target server, and the target server can determine the available domain name according to the feedback results of a plurality of browsers, so that the available domain name is selected for issuing when the domain name is issued subsequently, and the availability of WEB service is ensured.
The target server can determine the blocking result of the domain name according to the loading result fed back by the browser, and then determine the available domain name. The blocking result of the domain name may include that the domain name is completely blocked, which means that no type of media type (mintype) of HTTP resource can be accessed, and that the domain name is partially blocked. If all the resources corresponding to a domain name are not blocked, determining that the domain name is not blocked; if part of resources corresponding to a domain name are blocked, determining that the domain name is blocked; if all the resources corresponding to a domain name are blocked, determining that the domain name is completely blocked.
According to the method and the device for the target server, if the access request is sent to the target server through the first domain name and the webpage data fed back by the target server are received, in the process of loading the webpage data, the resources of other domain names of the target server are loaded through the first domain name, loading results of the other domain names are determined, and the loading results are fed back to the target server, so that the target server can determine available domain names according to the loading results, sniffing of the domain names can be achieved through a browser used by a user instead of using a fixed browser or simulator, the domain names can be sniffed under various network environments, accuracy of the sniffing results is improved, and service availability is guaranteed.
Fig. 3 is a flowchart illustrating a resource sniffing method, as shown in fig. 3, for performing accessibility sniffing on multiple domain names of a target server by a browser in a browser based on the HTTP (S) protocol, according to an exemplary embodiment, which sniffs static resources of other domain names by successfully accessing a first domain name of the target server, mainly, including the following steps.
In step S31, an access request is sent to the target server by the first domain name.
In step S32, if the web page data fed back by the target server is received through the first domain name, in the process of loading the web page data, a static resource acquisition request is sent to the target server through the first domain name.
After the browser successfully accesses the target server through the first domain name, in the process of loading the webpage data to be accessed, the browser needs to interact with the target server for a plurality of times to complete the loading of the webpage data, wherein the loading of the static resources of the webpage is involved, and when the static resources of the webpage are required to be loaded, the browser firstly needs to send a static resource acquisition request to the target server. Wherein the static resources include at least one of CSS (Cascading Style Sheets, cascading style sheet), JS (JavaScript), HTML (HyperText Markup Language ) and pictures. The CSS is a computer language for representing file styles such as HTML or XML (Extensible Markup Language ), and the CSS not only can statically modify a web page, but also can dynamically format elements of the web page in cooperation with various scripting languages. JS is an interpreted scripting language, a dynamic type, weak type, prototype-based language, built-in support type. HTML is an identifying language that includes a series of tags by which the format of documents on a network can be unified, making discrete Internet resources connected as a logical entity.
The process of loading the webpage data by the browser comprises the following steps: requesting an HTML page from a server, analyzing the HTML by a browser, requesting CSS and JS from the server, performing request API interface by JS, assembling the page according to data, requesting pictures from the server by JS, and displaying a webpage. When the browser needs to load the resource, the corresponding resource is required to be requested to the target server, and after the target server returns the corresponding resource, the browser loads the resource.
In step S33, a static resource returned by the target server is received, where the static resource includes a domain name loading file.
After receiving the static resource acquisition request sent by the browser, the target server returns the static resource requested by the browser, and the static resource returned by the target server comprises a domain name loading file. The domain name loading file is an instruction file for loading static resources of a specified domain name, and the static resources also comprise at least one of CSS, JS, HTML and pictures. The specified domain name is a domain name other than the first domain name corresponding to the target server.
For example, when the browser needs to load the CSS, a CSS acquisition request is sent to the target server, and the CSS returned by the target server is received, and the target server returns to send the CSS to include the domain name loading file. When the browser needs to load JS, a JS acquisition request is sent to a target server, the JS returned by the target server is received, and the JS returned by the target server comprises a domain name loading file. When the browser needs to load the picture, a picture loading request is sent to the target server, the picture returned by the target server is received, and the picture returned by the target server comprises a domain name loading file.
In step S34, in the process of loading the static resource, a file is loaded according to the domain name, and a loading request for the static resource of the specified domain name is sent to the target server through the first domain name.
The domain name loading file comprises static resources corresponding to the designated domain name to be loaded. After receiving the static resource, the browser loads the received static resource, and in the process of loading the static resource, loads the static resource of the appointed domain name through the first domain name according to the domain name loading file, namely, sends a loading request of the static resource of the appointed domain name to the target server through the first domain name.
In step S35, if feedback from the target server is received, determining that the loading result of the static resource for the specified domain name is successful; and if the feedback of the target server is not received, determining that the loading result of the static resource of the designated domain name is loading failure.
If the feedback of the target server is received, loading the static resource of the appointed domain name, determining that the loading result of the static resource of the appointed domain name is successful, if the loading of the static resource of the appointed domain name fails, loading the static resource of the appointed domain name cannot be performed, and determining that the loading result of the static resource of the appointed domain name is failed. When introducing a static resource for a specified domain name, the browser needs to send an acquisition request for the static resource for the specified domain name to a target server, if feedback of the target server is received, the static resource can be loaded, an introduction identifier is set for the loaded static resource, whether loading is successful or not is determined by inquiring whether the introduction identifier is contained or not, namely, if the static resource comprises the introduction identifier, the static resource for the specified domain name is determined to be loaded successfully, and if the static resource does not have the introduction identifier, the static resource for the specified domain name is determined to be loaded failed.
For example, if the browser loads the CSS of the specified domain name, it determines that the CSS of the specified domain name is not blocked, and if the browser fails to load the JS of the specified domain name, it determines that the JS of the specified domain name is blocked.
In step S36, the loading result is fed back to the target server, so that the target server determines the available domain name according to the loading result.
According to the method and the device for the static resource loading, in the process of loading the webpage data returned by the target server, the server returns the static resource when the static resource is requested to the target server, meanwhile, the static resource comprises the domain name loading file, in the process of loading the static resource, the loading request of the static resource of the appointed domain name can be sent to the target server through the first domain name according to the domain name loading file, if feedback of the target server is received, the loading result of the static resource of the appointed domain name is determined to be successful, if feedback of the target server is not received, the loading result of the static resource of the appointed domain name is determined to be failed to be loaded, sniffing of the static resource of the appointed domain name through successfully accessing the first domain name of the target server is achieved instead of sniffing by using a fixed browser or simulator, so that the domain name can be sniffed under various network environments, accuracy of sniffing results is improved, and availability of the static resource in service is guaranteed.
Fig. 4 is a flowchart illustrating a resource sniffing method, as shown in fig. 4, for performing accessibility sniffing on multiple domain names of a target server through a browser in a browser based on the HTTP (S) protocol, according to an exemplary embodiment, in which the sniffing is performed on AJAX requests of other domain names mainly by successfully accessing a first domain name of the target server, including the following steps.
In step S41, an access request is sent to the target server by the first domain name.
In step S42, if the web page data fed back by the target server is received through the first domain name, in the process of loading the web page data, an AJAX request for the specified domain name of the target server is sent through the first domain name under the condition that cross-domain access is supported.
The specified domain name is a domain name other than the first domain name corresponding to the target server. AJAX (Asynchronous Java and XML, asynchronous JS and XML) is a WEB development technology that asynchronously requests data, helping to improve user experience and page performance. The core of the AJAX technology is an XMLHttpRequest object (XHR for short), which provides a smooth interface for sending requests to the server and parsing the server response, enabling more information to be fetched from the server in an asynchronous manner.
When the AJAX requests of other domain names except the first domain name need to be sniffed by the browser, the cross-domain access of the browser needs to be allowed, so that resources corresponding to the AJAX requests of other domain names can be loaded. Therefore, under the condition of supporting cross-domain access, the browser can enable the XHR object to send an AJAX request of the appointed domain name of the target server through the first domain name, namely the XHR object sends an HTTP request of the appointed domain name of the target server through the first domain name, and receives feedback of the target server.
In step S43, if a feedback resource of the target server is received, loading the feedback resource, and determining that the loading result corresponding to the AJAX request of the specified domain name is successful loading; if the feedback resource of the target server is not received, determining that the loading result corresponding to the AJAX request of the designated domain name is loading failure.
If the XHR object receives the feedback resource of the target server, the feedback resource of the target server is sent to the browser, the browser receives the feedback resource of the target server, and determines that the AJAX request of the specified domain name is not blocked, namely, determines that the loading result corresponding to the AJAX request of the specified domain name is successful in loading. If the XHR object does not receive the feedback resource of the target server within the preset time after sending the AJAX request, the information that the feedback is not received can be sent to the browser, the browser receives the information and determines that the AJAX request of the designated domain name is blocked, namely, determines that the loading result corresponding to the AJAX request of the designated domain name is loading failure.
In step S44, the loading result is fed back to the target server, so that the target server determines the available domain name according to the loading result.
According to the method and the device for the data acquisition of the target server, in the process of loading the webpage data returned by the target server, under the condition of supporting cross-domain access, an AJAX request of the target server for the designated domain name is sent through the first domain name, if a feedback resource of the target server is received, the feedback resource is loaded, and a loading result corresponding to the AJAX request of the designated domain name is determined to be successful in loading, if the feedback resource of the target server is not received, the loading result corresponding to the AJAX request of the designated domain name is determined to be failed in loading, sniffing of the AJAX request of the designated domain name through the first domain name successfully accessing the target server is achieved, instead of sniffing by using a fixed browser or simulator, so that the domain name can be sniffed in various network environments, accuracy of the sniffing result is improved, and availability of the AJAX request in service is guaranteed.
Fig. 5 is a flowchart illustrating a resource sniffing method used in a target server to determine available domain names through loading results fed back by a browser, as shown in fig. 5, according to an exemplary embodiment, including the following steps.
In step S51, a plurality of loading results are obtained by receiving loading results sent by a plurality of browsers, where the loading results are obtained by loading resources of other domain names of a target server through a first domain name in the process of loading webpage data when the browser receives the webpage data of the target server through the first domain name.
After the first browser successfully accesses the target server through the first domain name, in the process of loading the webpage data returned by the target server, loading the resources of other domain names of the target server through the first domain name, and returning a loading result to the target server; after the second browser successfully accesses the target server through the second domain name, in the process of loading the webpage data returned by the target server, loading the resources of other domain names of the target server through the second domain name, and returning a loading result to the target server; similarly, other browsers can also sniff for resource accessibility through the first domain name, the second domain name or other domain names, and return the loading result to the target server. The target server may receive the loading results fed back by the multiple browsers, i.e. the target server receives the multiple loading results. One browser can feed back one loading result or feed back a plurality of loading results.
In step S52, an available domain name is determined according to the plurality of loading results.
The loading result may include that a specific resource of one domain name may or may not be loaded, for example, CSS of one domain name may be loaded, JS may not be loaded, etc.
The plurality of loading results may be loading results for a plurality of domain names. And counting a plurality of loading results according to the domain name, so that the available domain name can be determined.
In an exemplary embodiment, the determining the available domain name according to the plurality of loading results may include: counting the loading results of the same domain name in the loading results; if the loading result of one domain name meets the preset condition, determining that the domain name is unavailable; if the loading result of a domain name does not meet the preset condition, determining that the domain name is available; the available domain names are recorded.
The preset condition is a condition for determining whether a domain name is blocked.
And counting the plurality of loading results according to the same domain name to obtain the loading result of each domain name. The loading result of a domain name may include available resources and unavailable resources, and the number of browsers corresponding to each resource. If the proportion of the number of the browsers corresponding to the unavailable resources of one domain name in the browsers returning the sniffing result reaches a preset proportion, determining that the resources are unavailable; if all resources of a domain name are not available, determining that the domain name is not available; if all resources for a domain name are available, then the domain name is determined to be available. Recording the available domain name and recording the partially unavailable domain name and the unavailable resources of the domain name. And the available domain names are conveniently selected and issued subsequently through statistics of loading results and recording of the available domain names.
When a user propagates a sharing page, a domain name acquisition request of the sharing page to be propagated is sent to a target server through a sharing platform (such as WeChat and the like), and when the target server receives the domain name acquisition request, the target server can issue an available domain name, so that the service availability can be ensured. When the existing domain names have unavailable resources, new domain names can be regenerated and issued to ensure the availability of the service.
According to the method and the device for the domain name sniffing, the loading results sent by the plurality of browsers are received, the available domain name is determined according to the plurality of loading results, and as the loading results are obtained by loading resources of other domain names when the browser successfully accesses the target server, sniffing of the domain name can be achieved through the browser used by a user instead of sniffing by using a fixed browser or simulator, so that the domain name can be sniffed in various network environments, accuracy of the sniffing results is improved, the issued domain name is adjusted according to the sniffing results, and service availability is guaranteed.
Fig. 6 is a block diagram illustrating a resource sniffer device, according to an example embodiment. Referring to fig. 6, the apparatus includes an access request transmitting module 61, a resource loading module 62, and a loading result feedback module 63.
The access request sending module 61 is configured to send an access request to the target server through the first domain name;
the resource loading module 62 is configured to load resources of other domain names of the target server through the first domain name and determine loading results of the other domain names in the process of loading the webpage data if the webpage data fed back by the target server is received through the first domain name;
the loading result feedback module 63 is configured to feed back the loading result to the target server, so that the target server determines the available domain name according to the loading result.
Optionally, the resource loading module includes:
the static resource request unit is configured to send a static resource acquisition request to the target server through the first domain name in the process of loading the webpage data;
the static resource receiving unit is configured to receive a static resource returned by the target server, wherein the static resource comprises a domain name loading file;
the loading request generation unit is configured to send a loading request of the static resource of the designated domain name to the target server through the first domain name according to the domain name loading file in the process of loading the static resource;
The static loading result determining unit is configured to determine that the loading result of the static resource of the designated domain name is successful if the feedback of the target server is received; and if the feedback of the target server is not received, determining that the loading result of the static resource of the designated domain name is loading failure.
Optionally, the static resource includes at least one of CSS, JS, HTML and a picture.
Optionally, the resource loading module includes:
an AJAX request sending unit configured to send an AJAX request for a specified domain name of the target server through the first domain name in a process of loading the web page data in case of supporting cross-domain access;
the AJAX loading result determining unit is configured to load the feedback resource if the feedback resource of the target server is received, and determine that the loading result corresponding to the AJAX request of the designated domain name is successful in loading; if the feedback resource of the target server is not received, determining that the loading result corresponding to the AJAX request of the designated domain name is loading failure.
According to the method and the device for the target server, the access request is sent to the target server through the first domain name by the access request sending module, if the resource loading module receives the webpage data fed back by the target server through the first domain name, in the process of loading the webpage data, the first domain name is used for loading resources of other domain names of the target server, loading results of the other domain names are determined, the loading results are fed back to the target server by the loading result feedback module, so that the target server can determine available domain names according to the loading results, sniffing of the domain names can be achieved through a browser used by a user instead of the fixed browser or simulator, so that the domain names can be sniffed in various network environments, accuracy of sniffing results is improved, and service availability is guaranteed.
Fig. 7 is a block diagram illustrating a resource sniffer device, according to an example embodiment. Referring to fig. 7, the apparatus includes a loading result receiving module 71 and an available domain name determining module 72.
The loading result receiving module 71 is configured to receive loading results sent by a plurality of browsers to obtain a plurality of loading results, wherein the loading results are obtained by loading resources of other domain names of a target server through a first domain name in the process of loading the webpage data when the browser receives the webpage data of the target server through the first domain name;
the available domain name determination module 72 is configured to determine available domain names based on the plurality of loading results.
Optionally, the available domain name determining module includes:
the loading result statistics unit is configured to count loading results of the same domain name in the plurality of loading results;
the available domain name determining unit is configured to determine that a domain name is unavailable if the loading result of the domain name meets a preset condition; if the loading result of a domain name does not meet the preset condition, determining that the domain name is available;
and a domain name recording unit configured to record the available domain name.
According to the method and the device for the domain name sniffing, the loading results sent by the plurality of browsers are received through the loading result receiving module, the available domain name determining module determines available domain names according to the plurality of loading results, and as the loading results are obtained by loading resources of other domain names when the browser successfully accesses the target server, sniffing of the domain names can be achieved through the browser used by a user instead of the fixed browser or simulator, so that the domain names can be sniffed under various network environments, accuracy of the sniffing results is improved, issued domain names are adjusted according to the sniffing results, and service availability is guaranteed.
The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.
Fig. 8 is a block diagram of a terminal according to an exemplary embodiment. For example, the terminal 800 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, or the like.
Referring to fig. 8, a terminal 800 may include one or more of the following components: a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, and a communication component 816.
The processing component 802 generally controls overall operation of the apparatus 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to perform all or part of the steps of the methods described above. Further, the processing component 802 can include one or more modules that facilitate interactions between the processing component 802 and other components. For example, the processing component 802 can include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.
The memory 804 is configured to store various types of data to support operations at the terminal 800. Examples of such data include instructions for any application or method operating on the terminal 800, contact data, phonebook data, messages, pictures, videos, and the like. The memory 804 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
The power supply component 806 provides power to the various components of the terminal 800. The power components 806 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the terminal 800.
The multimedia component 808 includes a screen between the terminal 800 and the user that provides an output interface. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or slide action, but also the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and/or a rear camera. The front camera and/or the rear camera may receive external multimedia data when the terminal 800 is in an operation mode, such as a photographing mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.
The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a Microphone (MIC) configured to receive external audio signals when the terminal 800 is in an operation mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may be further stored in the memory 804 or transmitted via the communication component 816. In some embodiments, audio component 810 further includes a speaker for outputting audio signals.
The I/O interface 812 provides an interface between the processing component 802 and peripheral interface modules, which may be a keyboard, click wheel, buttons, etc. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.
The sensor assembly 814 includes one or more sensors for providing status assessment of various aspects of the terminal 800. For example, the sensor assembly 814 may detect an on/off state of the terminal 800, a relative positioning of the components, such as a display and keypad of the terminal 800, a change in position of the terminal 800 or a component of the terminal 800, the presence or absence of user contact with the terminal 800, an orientation or acceleration/deceleration of the terminal 800, and a change in temperature of the terminal 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 816 is configured to facilitate communication between the terminal 800 and other devices, either wired or wireless. The device 800 may access a wireless network based on a communication standard, such as WiFi, an operator network (e.g., 2G, 3G, 4G, or 5G), or a combination thereof. In one exemplary embodiment, the communication component 816 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component 816 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the terminal 800 can be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for executing the methods described above.
In an exemplary embodiment, a storage medium is also provided, such as a memory 804 including instructions executable by the processor 820 of the terminal 800 to perform the above-described method. Alternatively, the storage medium may be a non-transitory computer readable storage medium, which may be, for example, ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
Fig. 9 is a block diagram of a server, according to an example embodiment. Referring to FIG. 9, server 900 includes a processing component 922 that further includes one or more processors and memory resources represented by memory 932 for storing instructions, such as applications, executable by processing component 922. The application programs stored in memory 932 may include one or more modules that each correspond to a set of instructions. Further, processing component 922 is configured to execute instructions to perform the above-described methods.
The server 900 may also include a power component 926 configured to perform power management for the server 900, a wired or wireless network interface 950 configured to connect the server 900 to a network, and an input output (I/O) interface 958. The server 900 may operate based on an operating system stored in memory 932, such as Windows Server, mac OS XTM, unixTM, linuxTM, freeBSDTM, or the like.
In an exemplary embodiment, a storage medium is also provided that includes instructions, such as memory 932 including instructions, that are executable by processing component 922 of server 900 to perform the above-described method. Alternatively, the storage medium may be a non-transitory computer readable storage medium, which may be, for example, ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
In an exemplary embodiment, a computer program product is also provided, comprising readable program code executable by the processor 820 of the terminal 800 to perform the above-described resource sniffing method or by the processing component 922 of the server 900 to perform the above-described resource sniffing method. Alternatively, the program code may be stored in a storage medium of the terminal 800 or the server 900, which may be a non-transitory computer readable storage medium, such as ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the invention is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the invention is limited only by the appended claims.
Claims (15)
1. A method of resource sniffing, comprising:
sending an access request to a target server through a first domain name;
if web page data fed back by the target server is received through a first domain name, loading resources of other domain names of the target server through the first domain name in the process of loading the web page data, and determining loading results of the other domain names, wherein the first domain name is any one of a plurality of domain names corresponding to the target server, and the other domain names are different domain names from the first domain name in the plurality of domain names corresponding to the target server;
and feeding back the loading result to the target server so that the target server can determine available domain names according to the loading results of a plurality of browsers, wherein the plurality of browsers are in various network environments.
2. The method according to claim 1, wherein in the process of loading the web page data, loading the resources of the other domain names of the target server through the first domain name, and determining the loading result of the other domain names, includes:
In the process of loading the webpage data, a static resource acquisition request is sent to the target server through the first domain name;
receiving static resources returned by the target server, wherein the static resources comprise domain name loading files;
in the process of loading the static resource, a file is loaded according to the domain name, and a loading request of the static resource of the appointed domain name is sent to the target server through the first domain name;
if the feedback of the target server is received, determining that the loading result of the static resource of the designated domain name is successful; and if the feedback of the target server is not received, determining that the loading result of the static resource of the designated domain name is loading failure.
3. The method of claim 2, wherein the static resources comprise at least one of cascading style sheets CSS, JS, hypertext markup language HTML, and pictures.
4. The method according to claim 1, wherein in the process of loading the web page data, loading the resources of the other domain names of the target server through the first domain name, and determining the loading result of the other domain names, includes:
Under the condition of supporting cross-domain access, in the process of loading the webpage data, sending an AJAX request for a designated domain name of the target server through the first domain name;
if the feedback resource of the target server is received, loading the feedback resource, and determining that the loading result corresponding to the AJAX request of the designated domain name is successful in loading; if the feedback resource of the target server is not received, determining that the loading result corresponding to the AJAX request of the designated domain name is loading failure.
5. A method of resource sniffing, comprising:
receiving loading results sent by a plurality of browsers to obtain a plurality of loading results, wherein the loading results are obtained by loading resources of other domain names of a target server through a first domain name in the process of loading webpage data when the browser receives the webpage data of the target server through the first domain name, the first domain name and the other domain names are respectively domain names corresponding to the target server, and the plurality of browsers are in various network environments;
and determining available domain names according to the plurality of loading results.
6. The method of claim 5, wherein determining available domain names based on the plurality of loading results comprises:
Counting the loading results of the same domain name in the loading results;
if the loading result of one domain name meets the preset condition, determining that the domain name is unavailable; if the loading result of a domain name does not meet the preset condition, determining that the domain name is available;
the available domain names are recorded.
7. A resource sniffing device, comprising:
the access request sending module is configured to send an access request to the target server through the first domain name;
the resource loading module is configured to load resources of other domain names of the target server through a first domain name if web page data fed back by the target server is received through the first domain name, and determine a loading result of the other domain names, wherein the first domain name is any domain name of a plurality of domain names corresponding to the target server, and the other domain names are different domain names from the first domain name in the plurality of domain names corresponding to the target server;
and the loading result feedback module is configured to feed back the loading result to the target server so that the target server can determine available domain names according to the loading results of a plurality of browsers, wherein the plurality of browsers are in various network environments.
8. The apparatus of claim 7, wherein the resource loading module comprises:
the static resource request unit is configured to send a static resource acquisition request to the target server through the first domain name in the process of loading the webpage data;
the static resource receiving unit is configured to receive a static resource returned by the target server, wherein the static resource comprises a domain name loading file;
the loading request generation unit is configured to send a loading request of the static resource of the designated domain name to the target server through the first domain name according to the domain name loading file in the process of loading the static resource;
the static loading result determining unit is configured to determine that the loading result of the static resource of the designated domain name is successful if the feedback of the target server is received; and if the feedback of the target server is not received, determining that the loading result of the static resource of the designated domain name is loading failure.
9. The apparatus of claim 8, wherein the static resources comprise at least one of CSS, JS, HTML and pictures.
10. The apparatus of claim 7, wherein the resource loading module comprises:
An AJAX request sending unit configured to send an AJAX request for a specified domain name of the target server through the first domain name in a process of loading the web page data in case of supporting cross-domain access;
the AJAX loading result determining unit is configured to load the feedback resource if the feedback resource of the target server is received, and determine that the loading result corresponding to the AJAX request of the designated domain name is successful in loading; if the feedback resource of the target server is not received, determining that the loading result corresponding to the AJAX request of the designated domain name is loading failure.
11. A resource sniffing device, comprising:
the loading result receiving module is configured to receive loading results sent by a plurality of browsers to obtain a plurality of loading results, wherein the loading results are obtained by loading resources of other domain names of a target server through a first domain name in the process of loading webpage data when the browser receives the webpage data of the target server through the first domain name, the first domain name and the other domain names are respectively domain names corresponding to the target server, and the plurality of browsers are in various network environments;
And the available domain name determining module is configured to determine available domain names according to the plurality of loading results.
12. The apparatus of claim 11, wherein the available domain name determination module comprises:
the loading result statistics unit is configured to count loading results of the same domain name in the plurality of loading results;
the available domain name determining unit is configured to determine that a domain name is unavailable if the loading result of the domain name meets a preset condition; if the loading result of a domain name does not meet the preset condition, determining that the domain name is available;
and a domain name recording unit configured to record the available domain name.
13. A terminal, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the resource sniffing method of any of claims 1 to 4.
14. A server, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the resource sniffing method of claim 5 or 6.
15. A storage medium, which when executed by a processor of a terminal, enables the terminal to perform the resource sniffing method of any of claims 1 to 4, or which when executed by a processor of a server, enables the server to perform the resource sniffing method of claim 5 or 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911176222.8A CN111079040B (en) | 2019-11-26 | 2019-11-26 | Resource sniffing method, device, terminal, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911176222.8A CN111079040B (en) | 2019-11-26 | 2019-11-26 | Resource sniffing method, device, terminal, server and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111079040A CN111079040A (en) | 2020-04-28 |
| CN111079040B true CN111079040B (en) | 2023-09-01 |
Family
ID=70311701
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911176222.8A Active CN111079040B (en) | 2019-11-26 | 2019-11-26 | Resource sniffing method, device, terminal, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111079040B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111770161B (en) * | 2020-06-28 | 2022-06-07 | 北京百度网讯科技有限公司 | https sniffing jump method and device |
| CN114827158A (en) * | 2021-01-18 | 2022-07-29 | 网宿科技股份有限公司 | Configuration information loading method, system and server |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103327135A (en) * | 2013-06-27 | 2013-09-25 | 贝壳网际（北京）安全技术有限公司 | Domain name resolution method, device and client |
| CN109246227A (en) * | 2018-09-26 | 2019-01-18 | 北京达佳互联信息技术有限公司 | A kind of data request method, device, terminal device and storage medium |
| CN109600385A (en) * | 2018-12-28 | 2019-04-09 | 北京神州绿盟信息安全科技股份有限公司 | A kind of access control method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040199520A1 (en) * | 2003-04-04 | 2004-10-07 | Parsons Advanced Holdings, Inc. | Method for checking the availability of a domain name |
-
2019
- 2019-11-26 CN CN201911176222.8A patent/CN111079040B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103327135A (en) * | 2013-06-27 | 2013-09-25 | 贝壳网际（北京）安全技术有限公司 | Domain name resolution method, device and client |
| CN109246227A (en) * | 2018-09-26 | 2019-01-18 | 北京达佳互联信息技术有限公司 | A kind of data request method, device, terminal device and storage medium |
| CN109600385A (en) * | 2018-12-28 | 2019-04-09 | 北京神州绿盟信息安全科技股份有限公司 | A kind of access control method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111079040A (en) | 2020-04-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106569800B (en) | Front-end interface generation method and device | |
| CN107329743B (en) | Application page display method and device and storage medium | |
| CN107203398B (en) | Application distribution method and device | |
| CN107193606B (en) | Application distribution method and device | |
| CN106851695B (en) | Method, device and system for testing network speed | |
| US10831514B2 (en) | Display method and device of application interface | |
| CN107239351B (en) | Pasting method and device | |
| CN109525652B (en) | Information sharing method, device, equipment and storage medium | |
| CN111639276A (en) | Resource preloading method and device and storage medium | |
| CN111079040B (en) | Resource sniffing method, device, terminal, server and storage medium | |
| CN110413169B (en) | Information display method, device and medium | |
| CN105808304B (en) | Code deployment method, device and system | |
| CN106708967B (en) | Page display method and device | |
| CN104572230B (en) | Script file loading method and device and script file generating method and device | |
| CN111695064B (en) | Buried point loading method and device | |
| CN112486770A (en) | Client dotting reporting method and device, electronic equipment and storage medium | |
| CN105630948B (en) | Network page display method and device | |
| CN111782997A (en) | Method and device for loading webpage and storage medium | |
| CN110968492A (en) | Information processing method and device, and storage medium | |
| CN107679205B (en) | Multimedia data playing method and device, computer equipment and storage medium | |
| CN111061633B (en) | Webpage first screen time detection method, device, terminal and medium | |
| CN105868354B (en) | Webpage repairing method and device | |
| CN111131000B (en) | Information transmission method, device, server and terminal | |
| CN113407879B (en) | Data reporting method, device and readable medium | |
| CN109947640B (en) | Regression test-based core function coverage statistical method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |