CN116708553A - Data processing method, device, equipment and program product of agent tool - Google Patents
Data processing method, device, equipment and program product of agent tool Download PDFInfo
- Publication number
- CN116708553A CN116708553A CN202310637711.9A CN202310637711A CN116708553A CN 116708553 A CN116708553 A CN 116708553A CN 202310637711 A CN202310637711 A CN 202310637711A CN 116708553 A CN116708553 A CN 116708553A
- Authority
- CN
- China
- Prior art keywords
- data
- request path
- protobuf
- file name
- request
- 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.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 11
- 238000013507 mapping Methods 0.000 claims abstract description 48
- 238000004458 analytical method Methods 0.000 claims abstract description 32
- 238000012545 processing Methods 0.000 claims description 73
- 238000000034 method Methods 0.000 claims description 26
- 230000004044 response Effects 0.000 claims description 14
- 238000004590 computer program Methods 0.000 claims description 4
- 230000011218 segmentation Effects 0.000 claims description 3
- 238000007405 data analysis Methods 0.000 abstract description 3
- 239000003795 chemical substances by application Substances 0.000 description 12
- 238000010586 diagram Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 230000003993 interaction Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 239000000463 material Substances 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 239000000872 buffer Substances 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000000547 structure data Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a data processing method, device, equipment and program product of a proxy tool, and relates to the technical field of network data analysis. A data processing method of a proxy tool, comprising: acquiring a request path of the packet capturing data; acquiring a preset mapping list of the request path; matching protobuf file names corresponding to the request paths according to the mapping list; and analyzing the packet capturing data corresponding to the protobuf file name to generate an analysis result. According to the embodiment of the application, the protobuf analysis can be carried out on the data packet when the network data packet is grabbed.
Description
Technical Field
The present application relates to the field of network data analysis technologies, and in particular, to a data processing method, apparatus, device, and program product for a proxy tool.
Background
At present, a user can initiate or watch online live broadcast through terminal equipment such as a smart phone and the like. In the live broadcast process, system operation and maintenance personnel need to observe live broadcast data in real time and analyze flow through software such as agents and the like, and debug equipment.
The inventor of the application discovers that the existing agent tool or packet grabbing tool can only grab data packets generally, but cannot carry out protobuf analysis on the grabbed data and obtain specific plaintext fields, and the software is not high in usability.
Disclosure of Invention
According to an aspect of the present application, there is provided a data processing method of a proxy tool, including: acquiring a request path of the packet capturing data; acquiring a preset mapping list of the request path; matching protobuf file names corresponding to the request paths according to the mapping list; and analyzing the packet capturing data corresponding to the protobuf file name to generate an analysis result.
According to some embodiments, a request path for acquiring packet-grabbing data includes: acquiring the request path through a front-end page; and acquiring the corresponding packet capturing data according to the request path.
According to some embodiments, matching, according to the mapping list, a protobuf file name corresponding to the request path includes: determining whether the request path exists in the mapping list; if so, matching the corresponding protobuf file name in the mapping list for the request path; if not, generating the protobuf file name based on the request path according to the format of the protobuf file name.
According to some embodiments, generating the protobuf filename based on the request path in the format of the protobuf filename includes: splitting the request path to obtain the request volume number: 230196CI
Solving a segmentation character string of the path; and splicing the segmentation character strings according to the format of the protobuf file name to generate the protobuf file name.
According to some embodiments, a data type of the bundle data is determined, the data type comprising request data and response data, before the parsing of the bundle data corresponding to the protobuf filename to generate a parsing result.
According to some embodiments, parsing the bale data corresponding to the protobuf filename to generate a parsed result includes: analyzing the packet capturing data corresponding to the protobuf file name according to the data type of the packet capturing data; acquiring plaintext data corresponding to the packet capturing data under the condition that the analysis of the packet capturing data is successful; and returning the plaintext data to a front-end page to be displayed as the analysis result.
According to some embodiments, in case of a failure in parsing of the packet-grabbing data, returning a result of the failure in parsing to the front-end page; acquiring input content sent by the front-end page, wherein the input content comprises a corresponding relation between the request path and the protobuf file name; acquiring a protobuf file name corresponding to the request path according to the corresponding relation; analyzing the packet capturing data according to the data type of the packet capturing data and the corresponding protobuf file name; and updating the mapping list according to the corresponding protobuf file name.
According to an aspect of the present application, there is provided a data processing apparatus of a proxy tool, comprising: the grabbing module is used for acquiring grabbing data and a request path of the grabbing data; the processing module is used for acquiring a preset mapping list of the data paths; matching protobuf file names corresponding to the data paths according to the mapping list; determining the data type of the packet capturing data; and the analysis module analyzes the packet capturing data corresponding to the protobuf file name according to the data type so as to generate an analysis result.
According to an aspect of the present application, there is provided an electronic apparatus including: one or more processors; a storage means for storing one or more programs; the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the methods as described above.
According to an aspect of the application there is provided a computer program product comprising a computer program or instructions which, when executed by a processor, carries out a method as hereinbefore described.
According to the embodiment of the application, the mapping relation between the request path and the protobuf file name is preset in the technical scheme of the application, and the mapping relation is matched with the request path in the captured data, so that the analysis of protobuf path information is realized while the data packet is captured, and the proxy work volume number is improved: 230196CI
The software is easy to use.
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 application as claimed.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the description below are only some embodiments of the present application.
Fig. 1 shows a schematic diagram of a proxy tool according to an exemplary embodiment of the application.
Fig. 2 shows a flow chart of a data processing method of a proxy tool according to an exemplary embodiment of the application.
FIG. 3 illustrates an initial interface schematic of a proxy tool according to an example embodiment of the application.
Fig. 4 shows a front-end page schematic of a proxy tool according to an example embodiment of the application.
Fig. 5 shows a block diagram of a data processing apparatus of a proxy tool according to an exemplary embodiment of the application.
Fig. 6 shows a block diagram of an electronic device according to an example embodiment of the application.
Detailed Description
The user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or fully authorized by each party, and the collection, use and processing of related data is required to comply with the relevant laws and regulations and standards of the relevant country and region, and is provided with corresponding operation entries for the user to select authorization or rejection.
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments can be embodied in many forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar parts, and thus a repetitive description thereof will be omitted.
The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a roll number for the present application: 230196CI
A full understanding of the examples. One skilled in the relevant art will recognize, however, that the application can be practiced without one or more of the specific details, or with other methods, components, materials, devices, operations, etc. In these instances, well-known structures, methods, devices, implementations, materials, or operations are not shown or described in detail.
The flow diagrams depicted in the figures are exemplary only, and do not necessarily include all of the elements and operations/steps, nor must they be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the order of actual execution may be changed according to actual situations.
The terms first, second and the like in the description and in the claims and in the above-described figures are used for distinguishing between different objects and not necessarily for describing a sequential or chronological order. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus.
The application provides a data processing method, a device, equipment and a program product of a proxy tool, which can match a request path in captured data with a mapping list of a preset request path and a protobuf file name so as to analyze the captured data.
A data processing method, apparatus, device and program product of a proxy tool according to an embodiment of the present application will be described in detail below with reference to the accompanying drawings.
The present application relates to the following terms:
protobuf: namely Protocol Buffers, is a language and platform independent method for extensible and serialized structure data, and can be used for (data) communication protocols, data storage and the like. According to the protobuf method, the information transmitted during communication is packaged through a message data structure defined by protobuf, and then compiled into a binary code stream for transmission or storage.
Fig. 1 shows a schematic diagram of a proxy tool according to an exemplary embodiment of the application.
As shown in fig. 1, the agent includes a front-end page 100 and a data processing apparatus 200.
After the agent tool is started, the user end connects the agent volume number through a network (such as a wireless communication link): 230196CI
A tool. In the case that the user side generates the network interaction data, the front-end page 100 grabs and displays a request path of the data, and acquires the corresponding packet grabbing data through the request path.
The user side may be a variety of electronic devices with a display screen including, but not limited to, smartphones, portable computers, tablet computers, and the like.
After the front-end page 100 obtains the request path, the data processing apparatus 200 reads a preset mapping list of the request path and determines whether the obtained request path exists in the mapping list of the request path. The mapping list of the request path includes a corresponding relationship between the request path and a protobuf file name.
In the case where the obtained request path is included in the map list of request paths, the data processing apparatus 200 matches the corresponding protobuf file name for the obtained request path.
In the case where the obtained request path is not included in the map list of request paths, the data processing apparatus 200 performs a concatenation process on the obtained request path according to the format of the protobuf file name to generate a protobuf file name corresponding to the obtained request path.
After obtaining the protobuf file name corresponding to the request path, the data processing apparatus 200 further determines, through a preset application program interface, a data type of the packet capturing data, so as to determine that the packet capturing data is request data or response data.
The data processing apparatus 200 analyzes the request data or the response data corresponding to the protobuf file name.
In the case where the data type is that the parsing of the packet data of the request data or the response data is successful, the data processing apparatus 200 returns the plaintext data obtained by the parsing to the front-end page 100.
In the case where the data type is the request data or the packet data of the response data fails to parse, the data processing apparatus 200 returns the result of the parse failure to the front page. The data processing apparatus 200 obtains the input content of the operator on the front page in response to the instruction of the operator on the front page. The data processing apparatus 200 obtains the protobuf file name corresponding to the request path according to the corresponding relationship between the request path and the protobuf file name in the input content. The data processing apparatus 200 again analyzes the request path according to the protobuf file name corresponding to the obtained request path, and updates the mapping list of the request path.
The data processing apparatus 200 sends the plaintext data obtained by parsing the packet capturing data to the front-end page 100, so as to display the plaintext data obtained by parsing on the front-end page 100 as a parsing result.
Roll number: 230196CI
It should be appreciated that the number of clients, front-end pages and data processing devices in fig. 1 is merely illustrative. Any number of clients, front-end pages, and data processing devices may be provided as desired.
Fig. 2 shows a flow chart of a data processing method of a proxy tool according to an exemplary embodiment of the application.
As shown in fig. 2, in step S110, the data processing apparatus acquires a request path for packet data.
For example, in step S110, the data processing apparatus acquires the packet-grabbing data and the request path of the packet-grabbing data through the front-end page.
After the user terminal is connected with the started agent tool through the network, the data processing device intercepts a request path of data in the process of network interaction of the user terminal through a front-end page.
The data processing device obtains packet capturing data corresponding to the request path according to the intercepted request path.
According to some embodiments, the packet-grabbing data is encrypted binary data.
In step S120, the data processing apparatus acquires a mapping list of preset request paths.
For example, in step S120, the data processing apparatus acquires a mapping list including correspondence between request paths and protobuf file names, which is preset and updated.
According to some embodiments, the data processing apparatus obtains a mapping list of updated request paths from a server side of the agent and maintains it locally.
In step S130, the data processing apparatus matches the protobuf file name corresponding to the request path according to the mapping list.
For example, in step S130, the data processing apparatus matches the acquired request path with the mapping list of the request path, and obtains the protobuf file name corresponding to the request path according to the matching result.
The data processing device matches the request path obtained through the front-end page with a preset mapping list of the request path to judge whether the obtained request path exists in the mapping list of the request path.
In the case where the acquired request path exists in the map list of request paths, the data processing apparatus obtains a protobuf file name matching the acquired request path in the map list of request paths.
Roll number: 230196CI
Under the condition that the acquired request path does not exist in the mapping list of the request path, the data processing device divides the acquired request path, and according to the format of the protobuf file name, the divided character strings of the divided request path are spliced to form the protobuf file name corresponding to the acquired request path.
According to some embodiments, the data processing apparatus segments the request path acquired through the front page and acquires the segment strings page, home, assuming that the request path is/page/home. According to the format of the protobuf file name, the data processing device capitalizes the first letter of the split character string and splices the split character string, so that the protobuf file name of the request path/page/home is obtained: pageHome.
According to some embodiments, after obtaining the protobuf file name corresponding to the request path and before analyzing the packet capturing data corresponding to the protobuf file name, the data processing apparatus further determines, through a preset application program interface, a data type of the packet capturing data, so as to determine that the packet capturing data is request data or response data.
In step S140, the data processing apparatus parses the bundle data corresponding to the protobuf file name to generate a parsing result.
For example, in step S140, the data processing apparatus parses the packet capturing data corresponding to the protobuf file name according to the type of the packet capturing data, and obtains the parsing result.
The data processing device performs protobuf analysis on the packet capturing data (including request data or response data) corresponding to the protobuf file name.
Under the condition that the analysis of the packet capturing data is successful, the data processing device acquires plaintext data generated after the analysis of the packet capturing data in protobuf, and sends the plaintext data obtained after the analysis to a front-end page as an analysis result, and the front-end page displays the plaintext data.
And under the condition that the analysis of the packet-grabbing data fails, the data processing device sends an analysis result of the analysis failure to the front-end page. The data processing device responds to an input instruction of an operator on a front-end page, and obtains a protobuf file name corresponding to a request path according to input content in a preset format input by the operator on the front-end page. The input content in the preset format comprises a corresponding relation between a request path and a protobuf file name. The data processing device obtains the protobuf file name through the corresponding relation between the request path and the protobuf file name.
According to some embodiments, assuming that the request path is/page/home, after parsing the packet-grabbing data corresponding to the request path/page/home fails, the data processing apparatus will parse the failed knot volume number: 230196CI
And returning to the front page, and obtaining the input content/page/home which is input by the operator on the front page according to the preset format. The corresponding relation between the request path and the protobuf file name in the preset format is' request path: protobuf filename). The data processing device obtains a protobuf file name HotPageName corresponding to the request path/page/home according to the corresponding relation.
The data processing device analyzes the protobuf file name obtained according to the input content from the front-end page and the packet capturing data corresponding to the file name again, and updates the mapping list of the server side and the local request path according to the file name.
According to the embodiment of the application, the technical scheme can analyze the plaintext information corresponding to the protobuf path in the data packet while the proxy tool grabs the network data packet, so that the usability of the proxy tool software is improved.
FIG. 3 illustrates an initial interface schematic of a proxy tool according to an example embodiment of the application.
Fig. 4 shows a front-end page schematic of a proxy tool according to an example embodiment of the application.
As shown in fig. 3, the operator activates the agent tool via a "start" button in the initial interface.
After the user end connects with the agent tool through the network and generates the network data, the data processing device intercepts the request path into the network data through the front end page as shown in fig. 4.
The data processing device matches the intercepted request path with a mapping list of a preset request path. If the intercepted request path is in the mapping list of the request path, the data processing device matches the corresponding protobuf file name for the intercepted request path. The intercepted request path is not in the mapping list of the request path, and the data processing device generates a protobuf file name corresponding to the intercepted request path according to the format of the protobuf file name.
After determining the data type of the packet capturing data corresponding to the intercepted request path, the data processing device analyzes the packet capturing data and the corresponding protobuf file name, and sends the analysis result of the packet capturing data to a front end page shown in fig. 4 for display.
And under the condition that the packet capturing data analysis is successful, the data processing device sends the plaintext data obtained through analysis to a front-end page shown in fig. 4 for display.
In case of failed analysis of the packet capturing data, the data processing device sends the analysis failure result to the front-end page shown in fig. 4 for display. After determining that the analysis fails, the operator turns through the roll number: 230196CI
The input box of the initial interface shown in fig. 3 inputs the request path and the corresponding protobuf file name according to the preset format, and sends the input content to the data processing device.
For example, the preset format corresponding to the input box shown in fig. 3 is "url: pbname", that is, "request path: protobuf filename).
As shown in fig. 3, after the operator inputs the request path and the corresponding protobuf file name in the input box according to the preset format, the operator may click on the "pb list" button, so that the data processing apparatus updates the mapping list of the request path stored in the server, and obtains the latest mapping list of the request path from the server and stores the latest mapping list in the local. If no content is input in the input box by the operator, after clicking the "pb list" button, the data processing device directly acquires the latest mapping list of the request path from the server side, and replaces the local mapping list of the request path.
And the data processing device analyzes the packet capturing data corresponding to the protobuf file name again according to the protobuf file name corresponding to the acquired request path and acquires an analysis result.
Fig. 5 shows a block diagram of a data processing apparatus of a proxy tool according to an exemplary embodiment of the application.
As shown in fig. 5, the data processing apparatus 200 includes a grabbing module 210, a processing module 220, and an analyzing module 230.
After the agent is started, the user end connects the agent through a network (such as a wireless communication link). In the case that the user side generates the network interaction data, the capturing module 210 captures and displays a request path of the data through the front-end page, and obtains the corresponding capturing data through the request path.
After obtaining the request path, the processing module 220 reads a mapping list of preset request paths, and determines whether the obtained request path exists in the mapping list of the request path. The mapping list of the request path includes a corresponding relationship between the request path and a protobuf file name.
In the case that the obtained request path is included in the mapping list of request paths, the processing module 220 matches the corresponding protobuf file name for the obtained request path.
In the case that the obtained request path is not included in the mapping list of the request paths, the processing module 220 performs a splicing process on the obtained request paths according to the format of the protobuf file name to generate protobuf file names corresponding to the obtained request paths.
After obtaining the protobuf file name corresponding to the request path, the processing module 220 further determines, through a preset application program interface, a data type of the packet capturing data, so as to determine that the packet capturing data is a volume number: 230196CI
Request data or response data.
The parsing module 230 parses request data or response data corresponding to a protobuf file name.
In the case that the parsing of the packet data with the data type of the request data or the response data is successful, the parsing module 230 returns the plaintext data obtained by the parsing to the front-end page.
In the case that the data type is the packet data parsing failure of the request data or the response data, the parsing module 230 returns the result of the parsing failure to the front page.
The processing module 220 obtains the input content of the operator on the front page in response to the instruction of the operator on the front page.
The processing module 220 obtains the protobuf file name corresponding to the request path according to the corresponding relation between the request path and the protobuf file name in the input content.
The parsing module 230 parses again according to the protobuf file name corresponding to the obtained request path. At the same time, the processing module 220 updates the mapping list of the request path.
The parsing module 230 sends the plaintext data obtained by parsing the packet capturing data to a front-end page, so that the plaintext data obtained by parsing is displayed on the front-end page as a parsing result.
Fig. 6 shows a block diagram of an electronic device according to an example embodiment of the application.
As shown in fig. 6, the electronic device 600 is only an example, and should not be construed as limiting the functionality and scope of use of the embodiments of the present application.
As shown in fig. 6, the electronic device 600 is in the form of a general purpose computing device. Components of electronic device 600 may include, but are not limited to: at least one processing unit 610, at least one memory unit 620, a bus 630 connecting the different system components (including the memory unit 620 and the processing unit 610), a display unit 640, etc. In which a storage unit stores program codes that can be executed by the processing unit 610, so that the processing unit 610 performs the methods according to various exemplary embodiments of the present application described in the present specification. For example, the processing unit 610 may perform the method as shown in fig. 2.
The storage unit 620 may include readable media in the form of volatile storage units, such as Random Access Memory (RAM) 6201 and/or cache memory unit 6202, and may further include Read Only Memory (ROM) 6203.
The storage unit 620 may also include a program volume number having a set (at least one) of program modules 6205: 230196CI
Sequence/utility 6204, such program modules 6205 include, but are not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.
Bus 630 may be a local bus representing one or more of several types of bus structures including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or using any of a variety of bus architectures.
The electronic device 600 may also communicate with one or more external devices 700 (e.g., keyboard, pointing device, bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device 600, and/or any device (e.g., router, modem, etc.) that enables the electronic device 600 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 650. Also, electronic device 600 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through network adapter 660. The network adapter 660 may communicate with other modules of the electronic device 600 over the bus 630. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 600, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
From the description of the embodiments above, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. The technical solution according to the embodiments of the present application may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, and includes several instructions to cause a computing device (may be a personal computer, a server, a mobile terminal, or a network device, etc.) to perform the method according to the embodiments of the present application.
The software product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, volume number: 230196CI
Portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the preceding.
The computer readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable storage medium may also be any readable medium that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).
The computer-readable medium carries one or more programs which, when executed by one of the devices, cause the computer-readable medium to perform the aforementioned functions.
Those skilled in the art will appreciate that the modules may be distributed throughout several devices as described in the embodiments, and that corresponding variations may be implemented in one or more devices that are unique to the embodiments. The modules of the above embodiments may be combined into one module, or may be further split into a plurality of sub-modules.
According to some embodiments of the application, when the proxy tool grabs the data packet, the proxy buf analysis is performed on the data packet, so that the plaintext information can be ensured to be correctly returned through the proxy buf path, and the usability of proxy software is improved.
Roll number: 230196CI
The foregoing detailed description of the embodiments of the application has been presented only to assist in understanding the method and its core ideas of the application. Meanwhile, based on the idea of the present application, those skilled in the art can make changes or modifications on the specific embodiments and application scope of the present application, which belong to the protection scope of the present application. In view of the foregoing, this description should not be construed as limiting the application.
Claims (10)
1. A data processing method of a proxy tool, comprising:
acquiring a request path of the packet capturing data;
acquiring a preset mapping list of the request path;
matching protobuf file names corresponding to the request paths according to the mapping list;
and analyzing the packet capturing data corresponding to the protobuf file name to generate an analysis result.
2. The method of claim 1, wherein obtaining the request path for the packet-grabbing data comprises:
acquiring the request path through a front-end page;
and acquiring the corresponding packet capturing data according to the request path.
3. The method of claim 1, wherein matching the protobuf filename corresponding to the request path according to the mapping list comprises:
determining whether the request path exists in the mapping list;
if so, matching the corresponding protobuf file name in the mapping list for the request path;
if not, generating the protobuf file name based on the request path according to the format of the protobuf file name.
4. The method of claim 3, wherein generating the protobuf filename based on the request path in the format of the protobuf filename comprises:
dividing the request path to obtain a divided character string of the request path;
and splicing the segmentation character strings according to the format of the protobuf file name to generate the protobuf file name.
5. The method of claim 1, wherein the scratch pad number is determined prior to the parsing the scratch pad data corresponding to the protobuf filename to generate a parsing result: 230196CI
The data type of the packet data includes request data and response data.
6. The method of claim 1, wherein parsing the bale data corresponding to the protobuf filename to generate a parsed result comprises:
analyzing the packet capturing data corresponding to the protobuf file name according to the data type of the packet capturing data;
acquiring plaintext data corresponding to the packet capturing data under the condition that the analysis of the packet capturing data is successful;
and returning the plaintext data to a front-end page to be displayed as the analysis result.
7. The method as recited in claim 6, further comprising:
returning a result of the analysis failure to the front-end page under the condition that the analysis of the packet capturing data fails;
acquiring input content sent by the front-end page, wherein the input content comprises a corresponding relation between the request path and the protobuf file name;
acquiring a protobuf file name corresponding to the request path according to the corresponding relation;
analyzing the packet capturing data according to the data type of the packet capturing data and the corresponding protobuf file name; and
and updating the mapping list according to the corresponding protobuf file name.
8. A data processing apparatus of a proxy tool, comprising:
the grabbing module is used for acquiring grabbing data and a request path of the grabbing data;
the processing module is used for acquiring a preset mapping list of the data paths; matching protobuf file names corresponding to the data paths according to the mapping list; determining the data type of the packet capturing data;
and the analysis module analyzes the packet capturing data corresponding to the protobuf file name according to the data type so as to generate an analysis result.
9. An electronic device, comprising:
one or more processors;
roll number: 230196CI
A storage means for storing one or more programs;
when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-7.
10. A computer program product comprising a computer program or instructions which, when executed by a processor, implements the method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310637711.9A CN116708553A (en) | 2023-05-31 | 2023-05-31 | Data processing method, device, equipment and program product of agent tool |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310637711.9A CN116708553A (en) | 2023-05-31 | 2023-05-31 | Data processing method, device, equipment and program product of agent tool |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116708553A true CN116708553A (en) | 2023-09-05 |
Family
ID=87838585
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310637711.9A Pending CN116708553A (en) | 2023-05-31 | 2023-05-31 | Data processing method, device, equipment and program product of agent tool |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116708553A (en) |
-
2023
- 2023-05-31 CN CN202310637711.9A patent/CN116708553A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112738791B (en) | User information correlation backfill method, device, equipment and medium based on 5G core network | |
| US20080228504A1 (en) | Technique to Deflect Incident Ticket Submission in Real-Time | |
| CN110753050B (en) | Method and device for generating protocol document, computer storage medium and electronic equipment | |
| CN110858172A (en) | Automatic test code generation method and device | |
| CN114500614B (en) | Satellite telemetry data processing method and device, electronic equipment and readable medium | |
| US10775751B2 (en) | Automatic generation of regular expression based on log line data | |
| CN108984202B (en) | Electronic resource sharing method and device and storage medium | |
| CN107634947A (en) | Limitation malice logs in or the method and apparatus of registration | |
| CN113761412B (en) | Application page display method and device, electronic equipment, medium and application system | |
| CN113268245A (en) | Code analysis method, device and storage medium | |
| CN114490383A (en) | Remote debugging system, remote debugging method, computing device and readable medium | |
| CN112988599A (en) | Page debugging method and device, electronic equipment and storage medium | |
| CN111767229A (en) | Performance test method, device and equipment | |
| CN111045934A (en) | Page analysis method, device, client, storage medium and electronic equipment | |
| CN111680288B (en) | Container command execution method, device, equipment and storage medium | |
| CN113516729A (en) | Chart drawing method and device and computer readable storage medium | |
| CN114449523B (en) | Flow filtering method, device, equipment and medium for satellite measurement and control system | |
| CN116708553A (en) | Data processing method, device, equipment and program product of agent tool | |
| CN111158661A (en) | System interface docking method, device, medium and electronic equipment | |
| CN114416597A (en) | Test case record generation method and device | |
| CN112749078B (en) | Buried point testing method and device | |
| CN114285774A (en) | Flow recording method and device, electronic equipment and storage medium | |
| CN109660669B (en) | Method, system, equipment and storage medium for collecting user operation information | |
| CN113569083A (en) | Intelligent sound box local end digital evidence obtaining system and method based on data traceability model | |
| CN112596824A (en) | Information interaction method and device, electronic equipment and storage medium |
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 |