Resource extraction method, device and equipment, medium and computer product
By constructing a loop body in the browser and instantiating hyperlink element nodes, click events are dispatched programmatically, solving the problem of complex and unstable resource extraction methods, achieving simple and efficient resource extraction, and avoiding firewall detection.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-12-30
- Publication Date
- 2026-03-13
AI Technical Summary
Existing resource extraction methods are complex and unstable, making it difficult to effectively bypass the detection of firewalls such as Cloudflare.
By constructing a loop during the target browser's runtime, instantiating hyperlink element nodes using the Document Object Model, and programmatically dispatching click events, resources can be extracted directly using the browser's native download capabilities.
It achieves simple and efficient resource extraction, effectively avoids complex firewall detection, has a high pass rate, and is low in cost.
Smart Images
Figure CN121664798A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of network security technology, and in particular to a resource extraction method, apparatus, equipment, medium, and computer product. Background Technology
[0002] Information extraction technology from World Wide Web (WWW) sites has always been an important area of software engineering. Meanwhile, methods for acquiring multimedia data are constantly being updated. In recent years, many websites have deployed cloud firewalls such as Cloudflare to protect multimedia resources and block bots. While this effectively defends against malicious attacks, it also makes it difficult for academic researchers to download multimedia files from web servers. Common Cloudflare firewall protection solutions include two types: the first is 5sShield, specifically designed to defend against various network threats. Another important protection method is setting a Transport Layer Security (TLS) fingerprint. TLS fingerprints can determine the characteristics of TLS communication by examining information such as the cipher suites, protocol versions, and encryption algorithms used during the TLS handshake. In addition, firewalls like Cloudflare can monitor request frequency, mouse movements, and idle time to detect whether network requests are issued by legitimate clients.
[0003] Under the aforementioned protections, there are several ways to bypass the Cloudflare crawler firewall: One is through a fingerprint browser, which helps users switch Internet Protocol (IP) to hide their real IP address. Another method is to use open-source libraries like Cloudflare, which contain various complex algorithms to crawl relevant web resources through Cloudflare protection. However, this method is costly, complex to implement, and has an unstable success rate. Summary of the Invention
[0004] The purpose of this invention is to provide a resource extraction method, apparatus, device, medium, and computer product to solve the problems of complex and unstable resource extraction methods in the prior art.
[0005] To achieve the above objectives, embodiments of the present invention provide a resource extraction method, comprising:
[0006] During the execution of the target browser, a loop body is constructed through the first script, and the loop body includes multiple iteration cycles;
[0007] In each iteration of the loop, a hyperlink element node is instantiated using the document object model of the target browser; wherein, the hyperlink attribute of the hyperlink element node is the resource locator of the resource to be extracted; and the hyperlink element node explicitly declares download control attributes.
[0008] The click event of the hyperlink element node is programmatically dispatched, causing the target browser to download the resource to be extracted, thus completing the resource extraction operation.
[0009] Optionally, the method, wherein instantiating the hyperlink element node through the document object model of the target browser includes:
[0010] Default hyperlink element nodes are created using the document object model's element creation interface;
[0011] Set the hyperlink attribute of the default hyperlink element node to the resource locator of the resource to be extracted;
[0012] Configure download control attributes on the default hyperlink element node, and then obtain the hyperlink element node.
[0013] Optionally, the method, after instantiating the hyperlink element node through the document object model of the target browser, further includes:
[0014] The node insertion method of the document object model is invoked to insert the hyperlink element node into the document flow, triggering the repaint and reflow process of the target browser.
[0015] Optionally, the method, wherein programmatically dispatching click events of the hyperlink element node includes:
[0016] Call the creation event method of the document object model to create the click event;
[0017] If the click event is initialized, the click event is dispatched to the hyperlink element node.
[0018] Optionally, in the method, after programmatically dispatching the click event of the hyperlink element node to cause the target browser to execute the download of the resource to be extracted and completing the resource extraction operation, the method further includes:
[0019] Once the resource to be extracted has been downloaded, the hyperlink element node is deleted using the document object model.
[0020] Optionally, in the method, the loop body further includes a timer, which is used to cause the loop body to execute the next iteration cycle after a delay when the number of parallel threads executing the download process of the resource to be extracted in the target browser exceeds a preset threshold; wherein the delay time is determined according to the file type of the resource to be extracted.
[0021] Optionally, in the method, the loop body further includes a timer, which drives the loop body to perform iterative scheduling according to the preset plurality of iteration cycles.
[0022] To achieve the above objectives, embodiments of the present invention provide a resource extraction device, comprising:
[0023] The first processing module is used to construct a loop body through the first script during the execution of the target browser;
[0024] The second processing module is used to instantiate hyperlink element nodes through the document object model of the target browser in each iteration cycle of the loop body; wherein, the hyperlink attribute of the hyperlink element node is the resource locator of the resource to be extracted; and the hyperlink element node explicitly declares download control attributes.
[0025] The third processing module is used to programmatically dispatch the click events of the hyperlink element nodes, so that the target browser executes the download of the resource to be extracted, and completes the resource extraction operation of the resource to be extracted.
[0026] To achieve the above objectives, embodiments of the present invention provide a resource extraction device, comprising: a processor, a memory, and a program or instructions stored in the memory and executable on the processor; wherein, when the processor executes the program or instructions, it implements the resource extraction method as described above.
[0027] To achieve the above objectives, embodiments of the present invention provide a readable storage medium having a program or instructions stored thereon, wherein the program or instructions, when executed by a processor, implement the steps in the resource extraction method described above.
[0028] To achieve the above objectives, embodiments of the present invention provide a computer program product, which includes computer instructions that, when executed by a processor, implement the steps of the resource extraction method described above.
[0029] The beneficial effects of the above-described technical solution of the present invention are as follows:
[0030] This invention, in its embodiments, constructs a loop with multiple iteration cycles during the target browser's runtime. Within each iteration cycle, hyperlink element nodes are instantiated using the Document Object Model (DOM) to locate and download the resource to be extracted. By programmatically dispatching click events on these hyperlink element nodes, the target browser can execute the download of the resource, achieving the goal of resource extraction. By combining download control attributes with front-end resource scheduling, a pure front-end data collection closed loop is achieved. This directly utilizes the browser's native download capabilities, circumventing complex firewall detection. The technology is simple and boasts a high success rate. Attached Figure Description
[0031] Figure 1 This is a schematic diagram of the resource extraction method described in an embodiment of the present invention;
[0032] Figure 2 This is a schematic diagram of the resource extraction device described in an embodiment of the present invention;
[0033] Figure 3 This is a schematic diagram of the resource extraction device described in an embodiment of the present invention. Detailed Implementation
[0034] To make the technical problems, technical solutions and advantages of the present invention clearer, a detailed description will be given below in conjunction with the accompanying drawings and specific embodiments.
[0035] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of the invention. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments.
[0036] In various embodiments of the present invention, it should be understood that the sequence number of each process described below does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.
[0037] In addition, the terms "system" and "network" are often used interchangeably in this article.
[0038] In the embodiments provided by this invention, it should be understood that "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.
[0039] For ease of understanding, the following describes some aspects of the embodiments of the present invention:
[0040] like Figure 1 As shown, an embodiment of the present invention provides a resource extraction method, which includes:
[0041] Step S10: During the operation of the target browser, a loop body is constructed through the first script, the loop body including multiple iteration cycles;
[0042] It should be noted that during the operation of the target browser, a loop logic is constructed through a JavaScript script (i.e., the first script), specifically using a counter-driven loop body, and iterative scheduling is performed according to the preset total amount of resources (i.e., the multiple iteration cycles). For example, the base number of the multiple iteration cycles can be set to 1000.
[0043] Step S20: In each iteration of the loop body, a hyperlink element node is instantiated using the document object model of the target browser; wherein, the hyperlink attribute of the hyperlink element node is the resource locator of the resource to be extracted; and the hyperlink element node explicitly declares download control attributes.
[0044] It should be noted that within each iteration cycle, the Application Programming Interface (API) for creating DOM elements (document.createElement) built into the Document Object Model (DOM) is used to instantiate an embedded resource requester (i.e., the default hyperlink element node), and the HyperText Reference (href) attribute is set to the normalized Uniform Resource Identifier (URI) of the target resource (i.e., the resource to be extracted). Simultaneously, download control attributes are explicitly displayed. These download control attributes, such as, but not limited to, the download attribute defined in the HTML specification, instruct the target browser to treat the resource to be extracted as a download item, thereby activating the browser's built-in download manager. Finally, a HyperText Markup Language (HTML) 5-anchor element (i.e., the hyperlink element node) carrying download semantics is created, constituting an operational entity that can trigger the target browser's native download pipeline.
[0045] Step S30: The click event of the hyperlink element node is programmatically dispatched, causing the target browser to download the resource to be extracted, thereby completing the resource extraction operation.
[0046] It should be noted that the HTML5 specification defines... Anchor elements natively support the `href` and `download` attributes. The `download` attribute explicitly enables browser-based file download capabilities, a mechanism that operates within the browser's security sandbox. This embodiment of the invention utilizes this feature to dynamically add `` tags (i.e., the hyperlink element nodes) to complete the download of static resources from the website. By programmatically dispatching the click events of the hyperlink element nodes, the event handling pipeline of the target browser is activated, including;
[0047] The capture phase propagates downwards from the Windows object in the Microsoft Windows operating system to the target element;
[0048] The target phase executes the bound event handlers on the target element.
[0049] In the bubbling phase, events trace back up to the root node. This process eventually triggers the native download behavior of the `` tag element (the hyperlink element node), where the network stack of the target browser's kernel takes over the resource request.
[0050] In this embodiment, a loop with multiple iteration cycles is constructed during the target browser's runtime. Within each iteration cycle, hyperlink element nodes are instantiated using the Document Object Model (DOM) to locate and download the resource to be extracted. By programmatically dispatching click events on these hyperlink element nodes, the target browser can execute the download of the resource, achieving the goal of resource extraction. By combining download control attributes with front-end resource scheduling, a pure front-end data collection closed loop is achieved. This directly utilizes the browser's native download capabilities, circumventing complex firewall detection. The technology is simple and has a high success rate.
[0051] Optionally, the method, wherein step S20 includes:
[0052] Default hyperlink element nodes are created using the document object model's element creation interface;
[0053] Set the hyperlink attribute of the default hyperlink element node to the resource locator of the resource to be extracted;
[0054] Configure download control attributes on the default hyperlink element node, and then obtain the hyperlink element node.
[0055] In this embodiment, the built-in DOM element creation API (document.createElement) is used to instantiate and create an embedded resource requester (i.e., the default hyperlink element node), and the href attribute value is set to the canonical URI locator of the target resource (i.e., the resource to be extracted), while the download control attribute is explicitly set.
[0056] Optionally, the method, after step S20, further includes:
[0057] The node insertion method of the document object model is invoked to insert the hyperlink element node into the document flow, triggering the repaint and reflow process of the target browser.
[0058] In this embodiment, after instantiating the hyperlink element node using DOM methods, the `Node.appendChild` method (adding a child node to the node) or the `Element.insertAdjacentElement` method (inserting an element at an adjacent position) is called to dynamically inject the generated element (i.e., the hyperlink element node) into the DOM's render tree. This process must comply with the node operation specifications of the DOM Level 3 Core Specification to ensure that the element can be correctly inserted into the document flow and trigger the target browser's repaint and reflow processes.
[0059] Optionally, the method, wherein step S30 includes:
[0060] Call the creation event method of the document object model to create the click event;
[0061] If the click event is initialized, the click event is dispatched to the hyperlink element node.
[0062] In this embodiment, based on the DOM Events Level 2 specification, the DOM API's createEvent method is called to create a synthesized mouse click event object (i.e., the click event). The mouse event is initialized using the initMouseEvent method (i.e., the click event is initialized). The click event is precisely synthesized and dispatched for each a tag element (i.e., the hyperlink element node) using the dispatchEvent method, thereby activating the browser's event handling pipeline. This process ultimately triggers the native download behavior of the a tag element (i.e., the hyperlink element node), and the network stack of the target browser's kernel takes over the resource request.
[0063] Optionally, the method, after step S30, further includes:
[0064] Once the resource to be extracted has been downloaded, the hyperlink element node is deleted using the document object model.
[0065] In this embodiment, after the download transaction of a single resource (the resource to be extracted corresponding to a hyperlink element node) is completed, the corresponding node is immediately destroyed through DOM operations, such as the removeChild method. Elements (i.e., the hyperlink element nodes) are optimized for memory usage and DOM structure. Whether the downloaded resource has been completed can be determined through event listeners or a timeout strategy.
[0066] Optionally, in the method, the loop body further includes a timer, which is used to cause the loop body to execute the next iteration cycle after a delay when the number of parallel threads executing the download process of the resource to be extracted in the target browser exceeds a preset threshold; wherein the delay time is determined according to the file type of the resource to be extracted.
[0067] In this embodiment, commonly used browser engines in the prior art (such as Blink, WebKit, and Gecko) typically impose a hard limit of 6-8 concurrent HTTP / 1.1 connections from the same origin (as recommended by the Request for Comments (RFC) specification). To prevent the browser's main thread (including the JavaScript execution engine) from being blocked, network stack congestion, and potential user interface (UI) freezing due to the instantaneous creation of excessive download tasks, an asynchronous scheduling strategy is introduced. A timer (e.g., a setTimeout function or a requestIdleCallback function) is integrated into the loop structure (i.e., the loop body) to force a fixed delay (e.g., 200ms) between consecutive download batches. This throttling mechanism ensures that the number of active download threads is always within the browser's safe concurrency threshold (i.e., the preset threshold). The fixed delay (i.e., the delay duration) can be set according to the file type of the resource to be extracted; for example, the fixed delay for video files is greater than the fixed delay for text files.
[0068] Optionally, in the method, the loop body further includes a timer, which drives the loop body to perform iterative scheduling according to the preset plurality of iteration cycles.
[0069] In this embodiment, the loop body is iteratively scheduled according to the preset multiple iteration cycles using the timer. The complete logic of the loop body is encapsulated in an Immediately Invoked Function Expression (IIFE), ensuring namespace isolation and self-executing characteristics, which can be directly deployed to the target browser console or injected into the page context as a user script for execution.
[0070] The embodiments of this invention rely entirely on the browser's own infrastructure to perform network input / output (I / O) operations. The resulting Transport Layer Security (TLS) handshake fingerprints, HTTP session characteristics, User Agent (UA) identifiers, and even TCP / IP stack behaviors are completely isomorphic to regular requests triggered by real user interactions. Therefore, this traffic pattern can effectively circumvent the anomaly detection rules of Web Application Firewalls (WAFs) such as Cloudflare, which are based on behavior analysis and fingerprint recognition.
[0071] It should be noted that in specific scenarios, such as storing image hosting services or video files with regular URLs, front-end technologies can be used to bypass firewalls and download multimedia files like images. Using front-end technologies can circumvent complex browser same-origin policy checks and TLS fingerprinting, significantly reducing costs. In terms of performance, leveraging the download capabilities of modern browsers, crawling performance can be comparable to that of ordinary web crawlers. This invention protects this core concept and engineering control details as a whole. Without sacrificing performance, front-end technologies can circumvent complex browser same-origin policy checks and TLS fingerprinting, and because the requests originate from the user's real environment, the risk of IP blocking can be avoided, significantly reducing costs.
[0072] like Figure 2 As shown, to achieve the above objectives, embodiments of the present invention provide a resource extraction device, comprising:
[0073] The first processing module 201 is used to construct a loop body through the first script during the execution of the target browser;
[0074] The second processing module 202 is used to instantiate hyperlink element nodes through the document object model of the target browser in each iteration cycle of the loop body; wherein, the hyperlink attribute of the hyperlink element node is the resource locator of the resource to be extracted; and the hyperlink element node explicitly declares download control attributes.
[0075] The third processing module 203 is used to programmatically dispatch the click events of the hyperlink element nodes, so that the target browser executes the download of the resource to be extracted, and completes the resource extraction operation of the resource to be extracted.
[0076] Optionally, in the aforementioned apparatus, the second processing module 202 includes:
[0077] The first processing unit is used to create a default hyperlink element node using the document object model's element creation interface;
[0078] The second processing unit is used to set the hyperlink attribute of the default hyperlink element node to the resource locator of the resource to be extracted;
[0079] The first acquisition unit is used to configure download control attributes on the default hyperlink element node and acquire the hyperlink element node.
[0080] Optionally, the device further includes:
[0081] The fourth processing module is used to call the node insertion method of the document object model to insert the hyperlink element node into the document flow, triggering the repaint and reflow process of the target browser.
[0082] Optionally, in the aforementioned apparatus, the third processing module 203 includes:
[0083] The third processing unit is used to call the creation event method of the document object model to create the click event;
[0084] The fourth processing unit is used to dispatch the click event to the hyperlink element node when the click event is initialized.
[0085] Optionally, the device further includes:
[0086] The fifth processing module is used to delete the hyperlink element node through the document object model after the resource to be extracted has been downloaded.
[0087] Optionally, in the aforementioned apparatus, the loop further includes a timer, which is used to cause the loop to execute the next iteration cycle after a delay if the number of parallel threads executing the download process of the resource to be extracted in the target browser exceeds a preset threshold; wherein the delay duration is determined according to the file type of the resource to be extracted.
[0088] Optionally, in the aforementioned apparatus, the loop body further includes a timer, the timer being used to drive the loop body to perform iterative scheduling according to the preset plurality of iteration cycles.
[0089] It should be noted that the apparatus provided in this embodiment of the invention can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.
[0090] like Figure 3 As shown, to achieve the above objectives, an embodiment of the present invention provides a resource extraction device, including: a processor 301, a memory 302, and a program or instructions stored in the memory 302 and executable on the processor; wherein, when the processor 301 executes the program or instructions, it implements the various processes of the resource extraction method embodiment described above and achieves the same technical effect, which will not be described again here to avoid repetition.
[0091] The resource extraction device also includes a transceiver 303, used to receive and send data under the control of the processor 301.
[0092] Among them, Figure 3 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 301 and memory represented by memory 302 together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. Transceiver 303 can be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium. For different user equipment, the user interface 304 can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.
[0093] The processor 301 is responsible for managing the bus architecture and general processing, while the memory 302 can store the data used by the processor 301 when performing operations.
[0094] To achieve the above objectives, embodiments of the present invention provide a readable storage medium having a program or instructions stored thereon, wherein the program or instructions, when executed by a processor, implement the steps in the resource extraction method described above.
[0095] To achieve the above objectives, embodiments of the present invention provide a computer program product, which includes computer instructions that, when executed by a processor, implement the steps of the resource extraction method described above.
[0096] It should be further noted that the terminals described in this specification include, but are not limited to, smartphones, tablets, etc., and many of the functional components described are referred to as modules in order to emphasize the independence of their implementation.
[0097] In this embodiment of the invention, the module can be implemented in software so that it can be executed by various types of processors. For example, an identified executable code module may include one or more physical or logical blocks of computer instructions, which may be constructed as objects, procedures, or functions. Nevertheless, the executable code of the identified module does not need to be physically located together, but may include different instructions stored in different bits, which, when logically combined, constitute the module and achieve the module's intended purpose.
[0098] In practice, an executable code module can be a single instruction or many instructions, and can even be distributed across multiple different code segments, different programs, and across multiple memory devices. Similarly, operational data can be identified within the module and can be implemented in any suitable form and organized within any suitable data structure. This operational data can be collected as a single dataset or distributed across different locations (including different storage devices), and can exist, at least in part, solely as electronic signals within the system or network.
[0099] When a module can be implemented using software, considering the current level of hardware technology, modules that can be implemented in software can be implemented using hardware circuits by those skilled in the art to achieve the corresponding functions, without considering cost. These hardware circuits include conventional very-large-scale integrated circuits (VLSI) or gate arrays, as well as existing semiconductors such as logic chips and transistors, or other discrete components. Modules can also be implemented using programmable hardware devices, such as field-programmable gate arrays, programmable array logic, and programmable logic devices.
[0100] The exemplary embodiments described above are with reference to the accompanying drawings. Many different forms and embodiments are feasible without departing from the spirit and teachings of the invention. Therefore, the invention should not be construed as limiting the exemplary embodiments set forth herein. Rather, these exemplary embodiments are provided to make the invention complete and convey its scope to those skilled in the art. In these drawings, component dimensions and relative dimensions may be exaggerated for clarity. The terminology used herein is for the purpose of describing particular exemplary embodiments only and is not intended to be limiting. As used herein, unless clearly indicated otherwise, the singular forms “a,” “an,” and “the” are intended to include all such forms. It will be further understood that the terms “comprising” and / or “including”, when used in this specification, indicate the presence of the stated features, integers, steps, operations, components, and / or elements, but do not exclude the presence or addition of one or more other features, integers, steps, operations, components, and / or groups thereof. Unless otherwise indicated, when stated, a range of values includes the upper and lower limits of the range and any subranges in between.
[0101] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.
Claims
1. A resource extraction method, characterized in that, include: During the execution of the target browser, a loop body is constructed through the first script, and the loop body includes multiple iteration cycles; In each iteration of the loop, a hyperlink element node is instantiated using the document object model of the target browser; wherein, the hyperlink attribute of the hyperlink element node is the resource locator of the resource to be extracted; and the hyperlink element node explicitly declares download control attributes. The click event of the hyperlink element node is programmatically dispatched, causing the target browser to download the resource to be extracted, thus completing the resource extraction operation.
2. The method according to claim 1, characterized in that, Instantiating hyperlink element nodes through the target browser's document object model includes: Default hyperlink element nodes are created using the document object model's element creation interface; Set the hyperlink attribute of the default hyperlink element node to the resource locator of the resource to be extracted; Configure download control attributes on the default hyperlink element node, and then obtain the hyperlink element node.
3. The method according to claim 1, characterized in that, After instantiating the hyperlink element node using the target browser's document object model, the method further includes: The node insertion method of the document object model is invoked to insert the hyperlink element node into the document flow, triggering the repaint and reflow process of the target browser.
4. The method according to claim 1, characterized in that, Programmatically dispatching click events for the hyperlink element nodes includes: Call the creation event method of the document object model to create the click event; If the click event is initialized, the click event is dispatched to the hyperlink element node.
5. The method according to claim 1, characterized in that, After programmatically dispatching click events of the hyperlink element nodes to cause the target browser to download the resource to be extracted and completing the resource extraction operation, the method further includes: Once the resource to be extracted has been downloaded, the hyperlink element node is deleted using the document object model.
6. The method according to claim 1, characterized in that, The loop body also includes a timer, which is used to cause the loop body to execute the next iteration cycle after a delay when the number of parallel threads executing the download process of the resource to be extracted in the target browser exceeds a preset threshold; wherein, the delay time is determined according to the file type of the resource to be extracted.
7. The method according to claim 1, characterized in that, The loop body also includes a timer, which is used to drive the loop body to perform iterative scheduling according to the preset plurality of iteration cycles.
8. A resource extraction device, characterized in that, include: The first processing module is used to construct a loop body through the first script during the execution of the target browser; The second processing module is used to instantiate hyperlink element nodes through the document object model of the target browser in each iteration cycle of the loop body; wherein, the hyperlink attribute of the hyperlink element node is the resource locator of the resource to be extracted; and the hyperlink element node explicitly declares download control attributes. The third processing module is used to programmatically dispatch the click events of the hyperlink element nodes, so that the target browser executes the download of the resource to be extracted, and completes the resource extraction operation of the resource to be extracted.
9. A resource extraction device, comprising: A processor, a memory, and a program or instructions stored in the memory and executable on the processor; characterized in that, when the processor executes the program or instructions, it implements the resource extraction method as described in any one of claims 1-7.
10. A readable storage medium having a program or instructions stored thereon, characterized in that, When the program or instructions are executed by the processor, they implement the steps in the resource extraction method as described in any one of claims 1-7.
11. A computer program product, characterized in that, It includes computer instructions that, when executed by a processor, implement the steps of the resource extraction method as described in any one of claims 1-7.