CN116760811B - HTTP data processing method, device and readable storage medium - Google Patents
HTTP data processing method, device and readable storage medium Download PDFInfo
- Publication number
- CN116760811B CN116760811B CN202311030544.8A CN202311030544A CN116760811B CN 116760811 B CN116760811 B CN 116760811B CN 202311030544 A CN202311030544 A CN 202311030544A CN 116760811 B CN116760811 B CN 116760811B
- Authority
- CN
- China
- Prior art keywords
- data
- http
- data file
- static data
- 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.)
- Active
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 14
- 230000003068 static effect Effects 0.000 claims abstract description 90
- 238000000034 method Methods 0.000 claims abstract description 25
- 238000012545 processing Methods 0.000 claims abstract description 24
- 238000004519 manufacturing process Methods 0.000 claims abstract description 15
- 238000013507 mapping Methods 0.000 claims abstract description 12
- 238000012546 transfer Methods 0.000 claims abstract description 10
- 238000004088 simulation Methods 0.000 abstract description 12
- 238000011161 development Methods 0.000 description 18
- 238000005516 engineering process Methods 0.000 description 5
- 230000006978 adaptation Effects 0.000 description 2
- 125000004122 cyclic group Chemical group 0.000 description 2
- 230000007547 defect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000011835 investigation Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 238000012360 testing method 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/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/13—File access structures, e.g. distributed indices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/14—Details of searching files based on file metadata
-
- 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
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Library & Information Science (AREA)
- Computer And Data Communications (AREA)
Abstract
The application provides an HTTP data processing method, an HTTP data processing device and a readable storage medium, and relates to the technical field of networks. The method comprises the following steps: acquiring a hypertext transfer protocol (HTTP) request sent by an interface calling party to request data from a Uniform Resource Locator (URL) address pointed by the HTTP request; the interface calling party is a front end or a rear end, and the front end and the rear end are respectively developed; determining whether a corresponding first static data file exists in a target path corresponding to the HTTP request or not according to a file directory path mapping mode of the URL address; if the first static data file exists, the first static data file is returned to the front end or the back end. According to the scheme, the requirement of configuration is simplified by using the directory mapping URL, the data simulation service can be quickly built, complex data structure configuration is avoided by using the static data file, and the production efficiency is improved.
Description
Technical Field
The present application relates to the field of network technologies, and in particular, to a method and an apparatus for processing HTTP data, and a readable storage medium.
Background
The prior art scheme is that a complete interface system is provided, a hypertext transfer protocol (Hypertext Transfer Protocol, HTTP) interface is defined, a data format is defined, and finally interface data simulation is performed by randomly generating values or returning fixed values.
For example, the principle of mock.js, which is commonly used in the market, is to start a local node service, and to map the interface out by using an HTTP service by defining basic information of the interface, such as a request path, a request mode, a request parameter, and the like, and defining a format of a return parameter and a generation rule of return data, so as to call and simulate the return of the data. The existing basic flow is as follows: installing a mock.js; newly creating a Mock (virtual) file; defining interface attributes; defining a data format; the Mock service is started.
The flow of the prior art has the following disadvantages:
1) The operation is complex, the use cost is high, and the software use process needs to be familiar.
2) The interface request flow needs to be known and familiar with the formatting rules of the analog data.
3) And cannot be compatible with all data formats, and returned data only supports json (JS key value pair data, which is a lightweight data exchange format) data formats.
4) The real interface data cannot be generated, and the data returned by the interface are all simulation data generated according to rules.
Disclosure of Invention
The application aims to provide an HTTP data processing method, an HTTP data processing device and a readable storage medium, so as to solve the defects in the prior art.
To achieve the above object, an embodiment of the present application provides an HTTP data processing method, including:
acquiring a hypertext transfer protocol (HTTP) request sent by an interface calling party to request data from a Uniform Resource Locator (URL) address pointed by the HTTP request; the interface calling party is a front end or a back end, and the front end and the back end are respectively developed;
determining whether a corresponding first static data file exists in a target path corresponding to the HTTP request or not according to a file directory path mapping mode of the URL address;
and if the first static data file exists, returning the first static data file to the front end or the back end.
Optionally, determining whether the corresponding first static data file exists in the target path corresponding to the HTTP request includes:
analyzing and dividing the URL address to generate a path data set;
and determining whether a corresponding first static data file exists in the target path according to the path data set.
Optionally, the first static data file is used as a data carrier of analog data, and supports a preset data format;
the preset data format comprises at least one of a program file format, a picture file format, a text data format, a preset system data format, a sound format and a compressed file data format.
Optionally, before determining whether the corresponding first static data file exists in the target path corresponding to the HTTP request, the method further includes:
establishing a directory structure corresponding to an interface URL according to the interface URL;
and establishing a corresponding second static data file under the directory structure, and starting the HTTP service.
Optionally, in the debug scenario of the present network, the method further includes:
acquiring real production data generated by a current network interface;
and overlaying the real production data on the second static data file.
Optionally, the method further comprises:
if the static data file does not exist, failure information is returned to the front end or the back end; the failure information is used to indicate that a static data file is not found in the target path.
Optionally, the HTTP request is a data acquisition request or a data submission request.
To achieve the above object, an embodiment of the present application further provides an HTTP data processing apparatus, including:
the first acquisition module is used for acquiring a hypertext transfer protocol (HTTP) request sent by an interface calling party so as to request data from a Uniform Resource Locator (URL) address pointed by the HTTP request; the interface calling party is a front end or a back end, and the front end and the back end are respectively developed;
the first determining module is used for determining whether a corresponding first static data file exists in a target path corresponding to the HTTP request in a mode of mapping the URL address through a file directory path;
and the first processing module is used for returning the first static data file to the front end or the back end if the first static data file exists.
Optionally, the first determining module includes:
the first processing unit is used for analyzing and dividing the URL address to generate a path data set;
and the first determining unit is used for determining whether a corresponding first static data file exists in the target path according to the path data group.
To achieve the above object, an embodiment of the present application further provides a readable storage medium having stored thereon a program or instructions which, when executed by a processor, implement the steps in the HTTP data processing method as set forth in any one of the above.
The technical scheme of the application has the following beneficial effects:
in the embodiment of the application, a hypertext transfer protocol (HTTP) request sent by an interface calling party is obtained so as to request data from a Uniform Resource Locator (URL) address pointed by the HTTP request; the interface calling party is a front end or a rear end, and the front end and the rear end are respectively developed; determining whether a corresponding first static data file exists in a target path corresponding to the HTTP request or not according to a file directory path mapping mode of the URL address; if the first static data file exists, returning the first static data file to the front end or the back end; the method for mapping the URL by using the directory in the scheme simplifies the configuration requirement, can quickly build the data simulation service, avoids complex data structure configuration by using a static data file mode, and improves the production efficiency.
Drawings
Fig. 1 is a flow chart of an HTTP data processing method according to an embodiment of the present application;
fig. 2 is an application schematic diagram of an HTTP data processing method according to an embodiment of the present application;
fig. 3 is a schematic block diagram of an HTTP data processing apparatus according to an embodiment of the present application.
Detailed Description
In order to make the technical problems, technical solutions and advantages to be solved more apparent, the following detailed description will be given with reference to the accompanying drawings and specific embodiments.
It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
In various embodiments of the present application, it should be understood that the sequence numbers of the following processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
The related technology is used for the sake of integrity, the interface and the parameter simulation data are defined according to the related configuration of the user, the most critical disadvantage in the related technology is complexity, and under the development mode of front-end and back-end separation, the high-speed development progress and the iteration period are both in the efficiency of the compression intermediate link, and the most critical disadvantage is the complexity in use. Another problem is that the related art only supports json one data format, limiting its use scenario. Finally, although the simulation data can approximate to the real data through specific configuration, the simulation data is not the real data, and the data sample in the production state cannot be truly restored in the scene, so that the simulation data can only be used in the development period, and the problem in production debugging cannot be solved. Aiming at a plurality of defects in the related art, the application provides an HTTP data processing method, an HTTP data processing device and a readable storage medium.
Referring to fig. 1, an HTTP data processing method according to an embodiment of the present application includes:
step 11, obtaining a hypertext transfer protocol (HTTP) request sent by an interface calling party to request data from a Uniform Resource Locator (URL) address pointed by the HTTP request; the interface caller is a front end or a back end, and the front end and the back end are respectively developed.
Here, the front end and the back end may be performed synchronously or asynchronously; the front end and the back end may be in different development stages, for example, the whole project development is divided into three stages, the front end development may be a first stage, the back end development may be a second or third stage, or the front end development may be a second or third stage, and the back end development may be a first stage. Of course, the development of the back end to the development completion test stage, the development of the front end to the development middle stage, and the like are also possible.
It should be noted that the front-back end environment must be kept consistent, and the front-end development must build a development environment for the back-end development, and the back-end is the same, so that development cost is increased.
And step 12, determining whether a corresponding first static data file exists in a target path corresponding to the HTTP request in a file directory path mapping mode for the URL address.
And step 13, if the first static data file exists, returning the first static data file to the front end or the back end.
In the embodiment of the application, the interface can be normally accessed without interface configuration in a mode of mapping the request path of the interface through the file directory path; the interface data is stored as an interface static data file, so that complex data format configuration is not needed, data simulation rules are not needed to be known, and data needed by the interface can be returned. The technical scheme of the application is flexible, has large application scene and high use efficiency, and can solve the pain point of actual development.
Optionally, step 12 described above includes:
analyzing and dividing the URL address to generate a path data set;
and determining whether a corresponding first static data file exists in the target path according to the path data set.
In the embodiment of the application, the URL address is analyzed, if the analyzed URL address is "/api/user/getUserInfo", the "/api/user/getUserInfo" is divided, and the generated path data group is [ "api", "user", "getUserInfo" ]; and circularly traversing the path data set to check whether the target path corresponding to the URL address is the first static data file. For example: "api" corresponds to a directory, and the cyclic viewing of "user" is also a directory, continuing to cyclic "getUserInfo", and finding that the corresponding static data file is "getUserInfo json" or "getUserInfo. Xml". If the first static data file corresponding to the URL address is 'getUserInfo. Json', if 'getUserInfo. Json' is circularly found at the moment, determining whether the corresponding first static data file exists in the target path.
Optionally, the method further comprises:
if the static data file does not exist, failure information is returned to the front end or the back end; the failure information is used to indicate that a static data file is not found in the target path.
Optionally, the failure information includes:
400: representing an error request;
404: representing that the requested static data file does not exist;
503: indicating that the service is not available.
In the present application, in step 12, if it is determined that the static data file does not exist, it may be understood that the corresponding static data file cannot be found in the target path corresponding to the current HTTP request, for example, the static data file corresponding to the URL address in the HTTP request is "getuserinfo. Json", and the found static data file is "getuserinfo. Xml", or the "getuserinfo. Json" file is not found, or the URL address pair in the HTTP request is wrong, so that the designated static data file cannot be found, and the like, and it is determined that the static data file does not exist, and failure information is returned to the front end or the back end.
Optionally, the first static data file is used as a data carrier of analog data, and supports a preset data format;
the preset data format comprises at least one of a program file format, a picture file format, a text data format, a preset system data format, a sound format and a compressed file data format.
In the embodiment of the application, the complex data structure configuration is avoided by skillfully utilizing the first static data file, wherein the first static data file is used as a data carrier of analog data and supports a preset data format, and the preset data format can support any data format and meets all use scenes.
For example, the preset data format includes: picture data format, program data format, text information data format, etc. For another example, the text data format includes: TXT, DOC, PPT, DOCX, XLSX, PPTX, etc.; the picture file format includes: JPG, PNG, PDF, TIFF, SWF, etc.; the video format includes: FLV, RMVB, MP4, MVB, etc.; the sound format includes: WMA, MP3, etc.; the system format includes: RAR, EXE, etc.; the compressed file data format includes: RAR, etc. Program data formats include jsp format, xml format, json format, ajax format, and the like. The static data file of the application supports any one of the formats and meets all use scenes.
Optionally, before step 12, the method further includes:
establishing a directory structure corresponding to an interface URL according to the interface URL;
and establishing a corresponding second static data file under the directory structure, and starting the HTTP service.
In the embodiment of the present application, before acquiring a static data file, an HTTP service needs to be started, so that a directory structure corresponding to an interface URL is manually established according to the interface URL in a preset manner or manually, for example, a directory structure is created according to an interface URL path, for example: the catalog api needs to be created, the user catalog is created under the api catalog, and the second static data file getUserInfo. Json is created under the user catalog. The second static data file is established in advance through an interface URL, and the first static data file is carried through the URL carried by the HTTP request and searches the static file data corresponding to the HTTP request. After the corresponding second static data file is established under the directory structure, the interface data is written, the HTTP service is started, and the service component express in the HTTP service can be started.
By combining the technical scheme, the application can use the node service component express to provide HTTP service, when the interface request call is initiated, the static data file of the corresponding file directory is searched according to the request path, and after the file is found, the file content is output, thus completing the interface call and data return.
Optionally, in the debug scenario of the present network, the method further includes:
acquiring real production data generated by a current network interface;
and overlaying the real production data on the second static data file.
The embodiment of the application also has the advantage in debugging the current network environment, and the data simulation service can return the real current network data by copying the method of the current network interface real return data to cover the second static data file, thereby facilitating the problem investigation.
Optionally, the HTTP request is a data acquisition request or a data submission request.
In the embodiment of the present application, the request modes of the HTTP request include two types, respectively: the HTTP request in step 11 may be one of a data acquisition request (i.e., get request) and a data commit request (i.e., post request).
Wherein, the get request is a request for sending the requested data, the post request is a request for submitting the data, the URL is a standard resource address on the Internet, the get request can acquire the corresponding static data file through the URL, and the static data file supports all file formats, so that not only the webpage data can be acquired.
Referring to fig. 2, in one embodiment of the present application, data is requested from a URL address pointed to by an HTTP request by obtaining the HTTP request sent by an interface caller, that is, the interface call request; the application further analyzes the URL address corresponding to the HTTP request, and segments the URL address to generate a path data set; circularly accessing the path data set, judging whether a current path (namely a target path corresponding to the URL address) has a corresponding static data file, if so, acquiring the static data file, analyzing the file, acquiring data, and returning the analyzed data to an interface calling party; if the static data file does not exist, namely that the file cannot be found, failure information is returned to the interface calling party.
In summary, the scheme of the application skillfully utilizes the static data file to avoid complex data structure configuration and improve the production efficiency; the method of mapping URLs by using the catalogue also simplifies the configuration requirement, and the technology of the proposal can be used for quickly constructing data simulation service; any data format can be supported, and all use scenes are satisfied; the technology also has advantages in debugging of the current network environment, and the data simulation service can return the real current network data by copying the method of the current network interface to truly return the data and cover the static data file, so that the problem investigation is convenient.
Referring to fig. 3, an embodiment of the present application further provides an HTTP data processing apparatus, including:
a first obtaining module 31, configured to obtain a hypertext transfer protocol HTTP request sent by an interface caller, so as to request data from a URL address pointed by the HTTP request; the interface calling party is a front end or a back end, and the front end and the back end are respectively developed;
a first determining module 32, configured to determine, by mapping a file directory path to a URL address, whether a corresponding first static data file exists in a target path corresponding to the HTTP request;
the first processing module 33 is configured to return the first static data file to the front end or the back end if the first static data file exists.
Optionally, the first determining module 32 includes:
the first processing unit is used for analyzing and dividing the URL address to generate a path data set;
and the first determining unit is used for determining whether a corresponding first static data file exists in the target path according to the path data group.
Optionally, the first static data file is used as a data carrier of analog data, and supports a preset data format;
the preset data format comprises at least one of a program file format, a picture file format, a text data format, a preset system data format, a sound format and a compressed file data format.
Optionally, the HTTP data processing apparatus further includes:
the first establishing module is used for establishing a directory structure corresponding to the interface URL according to the interface URL;
and the second processing module is used for establishing a corresponding second static data file under the directory structure and starting the HTTP service.
Optionally, the HTTP data processing apparatus further includes:
the second acquisition module is used for acquiring real production data generated by the current network interface;
and the third processing module is used for overlaying the real production data on the second static data file.
Optionally, the HTTP data processing apparatus further includes:
the fourth processing module is used for returning failure information to the front end or the back end if the static data file does not exist; the failure information is used to indicate that a static data file is not found in the target path.
Optionally, the HTTP request is a data acquisition request or a data submission request.
The embodiments of the HTTP data processing method are applicable to the embodiments of the HTTP data processing apparatus, and the same technical effects can be achieved.
The readable storage medium of the embodiment of the present application stores a program or an instruction, which when executed by a processor, implements the steps in the HTTP data processing method described above, and can achieve the same technical effects, and is not described herein again for avoiding repetition.
The processor is a processor in the HTTP data processing method described in the foregoing embodiment. The readable storage medium includes a computer readable storage medium such as a Read-Only Memory (ROM), a random access Memory (Random Access Memory RAM), a magnetic disk or an optical disk.
The exemplary embodiments described above are described with reference to the drawings, many different forms and embodiments are possible without departing from the spirit and teachings of the present application, and therefore, the present application should not be construed as limited to the exemplary embodiments set forth herein. Rather, these exemplary embodiments are provided so that this disclosure will be thorough and complete, and will convey the scope of the application to those skilled in the art. In the drawings, the size of the elements and relative sizes may be exaggerated for clarity. The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. Unless otherwise indicated, a range of values includes the upper and lower limits of the range and any subranges therebetween.
While the foregoing is directed to the preferred embodiments of the present application, it will be appreciated by those skilled in the art that various modifications and adaptations can be made without departing from the principles of the present application, and such modifications and adaptations are intended to be comprehended within the scope of the present application.
Claims (7)
1. A method for processing HTTP data, comprising:
acquiring a hypertext transfer protocol (HTTP) request sent by an interface calling party to request data from a Uniform Resource Locator (URL) address pointed by the HTTP request; the interface calling party is a front end or a back end, and the front end and the back end are respectively developed; the front and back environments need to be kept consistent;
determining whether a corresponding first static data file exists in a target path corresponding to the HTTP request or not according to a file directory path mapping mode of the URL address, wherein the method comprises the following steps: analyzing and dividing the URL address to generate a path data set; circularly traversing the path data set, and determining whether a corresponding first static data file exists in the target path;
if the first static data file exists, returning the first static data file to the front end or the back end;
wherein, under the debugging scene of the present network, the method further comprises:
acquiring real production data generated by a current network interface;
overlaying the real production data with a second static data file; the second static data file is a corresponding static data file established under a directory structure corresponding to the interface URL.
2. The method according to claim 1, wherein the first static data file is used as a data carrier for analog data, supporting a preset data format;
the preset data format comprises at least one of a program file format, a picture file format, a text data format, a preset system data format, a sound format and a compressed file data format.
3. The method of claim 1, wherein before determining whether the corresponding first static data file exists in the target path corresponding to the HTTP request, the method further comprises:
establishing a directory structure corresponding to an interface URL according to the interface URL;
and establishing a corresponding second static data file under the directory structure, and starting the HTTP service.
4. The method according to claim 1, wherein the method further comprises:
if the static data file does not exist, failure information is returned to the front end or the back end; the failure information is used to indicate that a static data file is not found in the target path.
5. The method of claim 1, wherein the HTTP request is a data acquisition request or a data commit request.
6. An HTTP data processing apparatus, comprising:
the first acquisition module is used for acquiring a hypertext transfer protocol (HTTP) request sent by an interface calling party so as to request data from a Uniform Resource Locator (URL) address pointed by the HTTP request; the interface calling party is a front end or a back end, and the front end and the back end are respectively developed; the front and back environments need to be kept consistent;
the first determining module is used for determining whether a corresponding first static data file exists in a target path corresponding to the HTTP request in a mode of mapping the URL address through a file directory path; wherein the first determining module includes: the first processing unit is used for analyzing and dividing the URL address to generate a path data set; a first determining unit, configured to cycle through the path data set, and determine whether a corresponding first static data file exists in the target path;
the first processing module is used for returning the first static data file to the front end or the rear end if the first static data file exists;
wherein, the HTTP data processing device further comprises:
the second acquisition module is used for acquiring real production data generated by the current network interface;
the third processing module is used for overlaying the real production data on a second static data file; the second static data file is a corresponding static data file established under a directory structure corresponding to the interface URL.
7. A readable storage medium having stored thereon a program or instructions which when executed by a processor realizes the steps in the HTTP data processing method according to any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311030544.8A CN116760811B (en) | 2023-08-16 | 2023-08-16 | HTTP data processing method, device and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311030544.8A CN116760811B (en) | 2023-08-16 | 2023-08-16 | HTTP data processing method, device and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116760811A CN116760811A (en) | 2023-09-15 |
| CN116760811B true CN116760811B (en) | 2023-11-03 |
Family
ID=87961212
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311030544.8A Active CN116760811B (en) | 2023-08-16 | 2023-08-16 | HTTP data processing method, device and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116760811B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108959455A (en) * | 2018-06-15 | 2018-12-07 | 上海陆家嘴国际金融资产交易市场股份有限公司 | Single page Web application implementation method, device, computer equipment and storage medium |
| CN109388425A (en) * | 2018-08-17 | 2019-02-26 | 东莞数汇大数据有限公司 | A kind of interface switching method, system, device and the storage medium of front end engineering |
| CN110502238A (en) * | 2019-07-29 | 2019-11-26 | 贝壳技术有限公司 | A kind of method and device of front and back end joint debugging |
| CN111049889A (en) * | 2019-12-04 | 2020-04-21 | 车智互联（北京）科技有限公司 | Static resource uploading method and device, integrated server and system |
| CN112637235A (en) * | 2020-12-30 | 2021-04-09 | 绿盟科技集团股份有限公司 | Communication method, device, equipment and medium |
| CN113162998A (en) * | 2021-04-07 | 2021-07-23 | 广州炫视智能科技有限公司 | Intelligent interactive communication method and communication system |
| CN116185825A (en) * | 2022-12-14 | 2023-05-30 | 平安银行股份有限公司 | Front-end self-test method, front-end device, and computer-readable storage medium |
-
2023
- 2023-08-16 CN CN202311030544.8A patent/CN116760811B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108959455A (en) * | 2018-06-15 | 2018-12-07 | 上海陆家嘴国际金融资产交易市场股份有限公司 | Single page Web application implementation method, device, computer equipment and storage medium |
| CN109388425A (en) * | 2018-08-17 | 2019-02-26 | 东莞数汇大数据有限公司 | A kind of interface switching method, system, device and the storage medium of front end engineering |
| CN110502238A (en) * | 2019-07-29 | 2019-11-26 | 贝壳技术有限公司 | A kind of method and device of front and back end joint debugging |
| CN111049889A (en) * | 2019-12-04 | 2020-04-21 | 车智互联（北京）科技有限公司 | Static resource uploading method and device, integrated server and system |
| CN112637235A (en) * | 2020-12-30 | 2021-04-09 | 绿盟科技集团股份有限公司 | Communication method, device, equipment and medium |
| CN113162998A (en) * | 2021-04-07 | 2021-07-23 | 广州炫视智能科技有限公司 | Intelligent interactive communication method and communication system |
| CN116185825A (en) * | 2022-12-14 | 2023-05-30 | 平安银行股份有限公司 | Front-end self-test method, front-end device, and computer-readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116760811A (en) | 2023-09-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102158557B1 (en) | Method and device for determining response time | |
| US7490167B2 (en) | System and method for platform and language-independent development and delivery of page-based content | |
| US9645910B1 (en) | Cross platform mobile HTML debugging | |
| US9652364B1 (en) | Cloud service for mobile testing and debugging | |
| CN107066631A (en) | Display methods, device and the electronic equipment of the page | |
| JP6971292B2 (en) | Methods, devices, servers, computer-readable storage media and computer programs for aligning paragraphs and images | |
| US20040103078A1 (en) | Web server hit multiplier and redirector | |
| JP2014523567A (en) | Live browser tooling in an integrated development environment | |
| CN110955409B (en) | Method and device for creating resources on cloud platform | |
| CN106776318A (en) | A kind of test script method for recording and system | |
| CN111881394B (en) | Request processing method and system for application middle layer | |
| CN114500423B (en) | Message processing method, device, equipment and storage medium | |
| CN113778897B (en) | Automatic test method, device and equipment for interface and storage medium | |
| CN116760811B (en) | HTTP data processing method, device and readable storage medium | |
| US11184687B2 (en) | Wearable device, information processing method, apparatus and system | |
| CN111881043A (en) | Page testing method and device, storage medium and processor | |
| CN114124766B (en) | Test method and device based on simulation data | |
| CN111338928A (en) | Chrome-based browser testing method and device | |
| CN113626099B (en) | Application program starting method and device and electronic equipment | |
| CN114896487A (en) | Method, system and medium for implementing a blockchain browser with front end interacting with blockchain | |
| CN112434233B (en) | Method and device for accelerating first screen rendering of secondary page | |
| CN113760715A (en) | Method and device for testing system | |
| CN112286808A (en) | Application program testing method and device, electronic equipment and medium | |
| CN114328180A (en) | Interface automation test method, system, electronic equipment and storage medium | |
| CN111581556A (en) | Page data processing method and device, electronic equipment and readable 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |