CN112015483B - POST request parameter automatic processing method and device and readable storage medium - Google Patents
POST request parameter automatic processing method and device and readable storage medium Download PDFInfo
- Publication number
- CN112015483B CN112015483B CN202010790354.6A CN202010790354A CN112015483B CN 112015483 B CN112015483 B CN 112015483B CN 202010790354 A CN202010790354 A CN 202010790354A CN 112015483 B CN112015483 B CN 112015483B
- Authority
- CN
- China
- Prior art keywords
- request
- post
- parameter
- processed
- configuration file
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- 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]
- G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
-
- 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)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Storage Device Security (AREA)
Abstract
The application discloses a POST request parameter automatic processing method and device and a computer readable storage medium. The method comprises the steps of storing a POST request configuration file generated according to a corresponding request configuration file format based on a request type in a preset directory in a project compiling and packaging stage, and reading the POST request configuration file in the directory into a memory. When a to-be-processed POST request sent by a client is received, whether the to-be-processed POST request is a sensitive request or a non-sensitive request is identified based on a POST request configuration file, a request type of the to-be-processed POST request is matched with a corresponding copying original request parameter reading mode so as to read a required parameter value from a request body or a uniform positioning resource character of the POST request, and a data parameter of the sensitive request is only obtained from the request body of the to-be-processed POST request. Therefore, the expandability of the service interface is effectively improved, different practical requirements of different users on sensitive requests can be met, and the requirements of URL (uniform resource locator) with parameters in POST (POST position response) requests of different users can also be met.
Description
Technical Field
The present application relates to the field of network technologies, and in particular, to a method and an apparatus for automatically processing POST request parameters, and a computer-readable storage medium.
Background
Under the current mainstream technology, HTTP (HyperText Transfer Protocol) is a simple request-response Protocol, which specifies what messages a client may send to a server and what responses the client may obtain, i.e. a communication transmission Protocol for defining a response mode of the client requesting a server. In one embodiment, the web browser may be a client and the web application on the computer may be a server, the client browser submitting an HTTP request to the server, and the server returning a response to the client, the response containing state information about the request and content that may be requested.
HTTP, a widely used network application layer Protocol, generally operates on TCP (Transmission Control Protocol), and is based on TCP/IP (Internet Protocol). When a request-response is performed between a client and a server based on the HTTP protocol, two most commonly used request methods are a GET request and a POST request. Where a GET request is to request data from a specified resource and a POST request is to submit data to be processed to the specified resource. The bottom layer of HTTP is TCP/IP, so the bottom layer of GET request and POST request is also TCP/IP, that is, GET/POST request are both TCP links. The functional requests that GET requests and POST requests can complete are the same, but differ in the manner in which the request parameters are passed. The GET request generally places parameter data to be requested in a URL (Uniform Resource Locator), the server interface obtains request parameters by instructing queryString (), and the POST request generally places parameters in a request body without specific addition on the URL, but no matter which request method, the POST must have a URL, such as bringing a URL parameter to the POST, which is completely feasible in technical implementation.
In the related art, in a general scenario, a POST request is generally applicable to a request with sensitive data, and is used for a request without adding a parameter to a URL, where the sensitive data is data that a user wants to protect or data that an unauthorized user cannot obtain. However, when providing a service interface to a user, different users may not have exactly the same requirements for sensitive data, and an individual user may add parameters to a URL in order to prevent their own code from changing on an individual POST request, and also want to obtain the same data returned by the service interface.
In view of this, how to improve the expandability of the service interface can not only meet different practical requirements of different users on the sensitive request, but also meet the requirements of different users on the URL band parameters in the POST request, which is a technical problem to be solved by technical personnel in the field.
Disclosure of Invention
The application provides a POST request parameter automatic processing method, a POST request parameter automatic processing device and a computer readable storage medium, which effectively improve the expandability of a service interface, not only can meet different practical requirements of different users on sensitive requests, but also can meet the requirements of URL (uniform resource locator) band parameters in the POST requests of different users.
In order to solve the above technical problems, embodiments of the present invention provide the following technical solutions:
one aspect of the embodiments of the present invention provides a method for automatically processing POST request parameters, including:
reading a POST request configuration file stored in a preset directory in a project compiling and packaging stage into a memory in advance; the POST request configuration file is generated according to a corresponding request configuration file format based on a request type, the request type comprises a sensitive request and an insensitive request, and the sensitive request is a POST request carrying data parameters which cannot be stolen by an unauthorized user;
when a to-be-processed POST request sent by a client is received, identifying the request type of the to-be-processed POST request based on the POST request configuration file;
reading a required parameter value from a request body or a uniform positioning resource character of the POST request to be processed based on the matching of the request type of the POST request to be processed and a corresponding copying original request parameter reading mode; and the data parameter value of the sensitive request is only obtained from the request body of the POST request to be processed.
Optionally, the reading, from the request body or the uniform locator resource identifier of the POST request to be processed, a required parameter value based on the matching of the request type of the POST request to be processed and the corresponding copying original request parameter reading manner includes:
acquiring all parameters and corresponding parameter values in a request body and a uniform resource locator of the POST request to be processed and parameter data carried in the uniform resource locator;
the POST request to be processed is the sensitive request, and corresponding parameter values are read from the request body based on the received target parameter name;
the POST request to be processed is the non-sensitive request, and if a request body of the POST request to be processed contains target parameters, corresponding parameter values are read from the request body based on the target parameter names; and if the request body of the POST request to be processed does not contain the target parameter and the uniform resource locator contains the target parameter, reading a corresponding parameter value from the uniform resource locator based on the target parameter name.
Optionally, after acquiring all parameters and corresponding parameter values in the request body and the uniform resource locator of the POST request to be processed and parameter data carried in the uniform resource locator, the method further includes:
counting a first frequency of the target parameter appearing in the POST request to be processed and a second frequency of the target parameter appearing in the uniform resource locator;
if the first number of times is the same as the second number of times, the target parameter only exists in the uniform resource locator;
if the first number is greater than the second number, the target parameter is present in both the uniform resource locator and the request body.
Optionally, when receiving a to-be-processed POST request sent by a client, identifying a request type of the to-be-processed POST request based on the POST request configuration file includes:
monitoring each web request of the client in real time;
when the fact that the client side sends the POST request to be processed is detected, an interceptor is used for intercepting the POST request to be processed;
detecting whether the POST request to be processed is the sensitive request or the non-sensitive request according to the security request set in the memory; the safety request set is data which is obtained by writing the POST request configuration file into the memory according to a preset data storage format.
Optionally, before reading the POST request configuration file stored in the preset directory in the project compiling and packaging stage in advance into the memory, the method further includes:
providing request configuration file formats of a service interface for different request types for a user, wherein the request configuration file formats comprise a sensitive request configuration file format and a request configuration file default format;
in the project compiling and packaging stage, if a POST self-defining request configuration file generated by a user based on the sensitive request configuration file format is received, reading the POST self-defining request configuration file, and overwriting the POST self-defining request configuration file to the preset directory; and if the POST self-defining request configuration file of the user is not received, automatically generating a corresponding POST default request configuration file under the preset directory according to the default format of the request configuration file.
Another aspect of the embodiments of the present invention provides an automated POST request parameter processing apparatus, including:
the project compiling module is used for storing the POST request configuration file generated according to the corresponding request configuration file format based on the request type in a preset directory; the request type comprises a sensitive request and an insensitive request, wherein the sensitive request is a POST request carrying data parameters which cannot be stolen by an unauthorized user;
the Web starting module is used for reading the POST request configuration file stored in the preset directory into the memory;
the request identification module is used for identifying the request type of the POST request to be processed based on the POST request configuration file when the POST request to be processed sent by the client is received;
a request parameter reading module, configured to read a required parameter value from a request body or a uniform positioning resource identifier of the POST request to be processed based on a request type of the POST request to be processed matching a corresponding carbon-copy original request parameter reading manner; and the data parameter value of the sensitive request is only obtained from the request body of the POST request to be processed.
Optionally, the request parameter reading module includes:
the parameter acquisition submodule is used for acquiring all parameters and corresponding parameter values in the request body and the uniform resource locator of the POST request to be processed and parameter data carried in the uniform resource locator;
the sensitive parameter reading sub-module is used for reading a corresponding parameter value from the request body based on the received target parameter name, wherein the POST request to be processed is the sensitive request;
a non-sensitive parameter reading sub-module, configured to read a corresponding parameter value from a request body of the POST request to be processed based on a name of a target parameter if the POST request to be processed is the non-sensitive request; and if the request body of the POST request to be processed does not contain the target parameter and the uniform resource locator contains the target parameter, reading a corresponding parameter value from the uniform resource locator based on the target parameter name.
Optionally, the request parameter reading module may further include a parameter positioning sub-module, where the parameter positioning sub-module includes:
the counting unit is used for counting a first frequency of the target parameter appearing in the POST request to be processed and a second frequency of the target parameter appearing in the uniform resource locator;
a positioning unit, configured to, if the first number of times is the same as the second number of times, only exist the target parameter in the uniform resource locator; if the first number is greater than the second number, the target parameter is present in both the uniform resource locator and the request body.
The embodiment of the invention also provides a device for automatically processing the POST request parameters, which comprises a processor, wherein the processor is used for realizing the steps of the method for automatically processing the POST request parameters when executing the computer program stored in the memory.
Finally, an embodiment of the present invention provides a computer-readable storage medium, where a POST request parameter automation processing program is stored on the computer-readable storage medium, and when executed by a processor, the POST request parameter automation processing program implements the steps of the POST request parameter automation processing method according to any one of the previous items.
The technical scheme provided by the application has the advantages that when different users are in butt joint or integrated to provide services or interface calling, different degrees of safety requests of different users are identified and marked into the configuration file, and a set of service interface code system can be realized by writing data into a project specified directory in a mode of reading a request configuration file which is required to contain sensitive data in a POST (POST position indication) request of the user at a project compiling and packaging stage. Meanwhile, the method adapts to scenes with different security requirements of different users, carries out security judgment on the initiated web request according to the memory data, and obtains parameter values from a request body in a secure mode for requests with different security degrees, such as the request containing sensitive data, so as to meet the requirement of parameter obtaining processing under different scenes of the POST request, thereby not only increasing the security processing of the service interface on the sensitive request method, but also increasing the security of the service interface and simultaneously increasing the expansibility of the service interface processing method. The method is suitable for calling the service interface under various conditions of different parameter transmission, meets the expandability of calling the service interface, maximally meets different calling forms of different users on the premise of ensuring the safety of data transmission, can meet different actual requirements of different users on sensitive requests, and can also meet the requirement of URL with parameters in POST requests of different users.
In addition, the embodiment of the invention also provides a corresponding implementation device and a computer readable storage medium for the POST request parameter automatic processing method, so that the method has higher practicability, and the device and the computer readable storage medium have corresponding advantages.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions of the related art, the drawings required to be used in the description of the embodiments or the related art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a schematic flow chart of a method for automatically processing POST request parameters according to an embodiment of the present invention;
FIG. 2 is a schematic flow chart illustrating another automated POST request parameter processing method according to an embodiment of the present invention;
FIG. 3 is a schematic flow chart illustrating a further method for automated processing of POST request parameters according to an embodiment of the present invention;
FIG. 4 is a block diagram of an embodiment of an automated POST request parameter processing apparatus according to an embodiment of the present invention;
fig. 5 is a block diagram of another specific embodiment of an automated POST request parameter processing apparatus according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the disclosure, the invention will be described in further detail with reference to the accompanying drawings and specific embodiments. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terms "first," "second," "third," "fourth," and the like in the description and claims of this application and in the above-described drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "comprising" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements but may include other steps or elements not expressly listed.
Having described the technical solutions of the embodiments of the present invention, various non-limiting embodiments of the present application are described in detail below.
Referring to fig. 1, fig. 1 is a schematic flow chart of an automated POST request parameter processing method according to an embodiment of the present invention, where the embodiment of the present invention may include the following:
s101: and storing the POST request configuration file generated according to the corresponding request configuration file format based on the request type in a preset directory.
The method is suitable for the POST request in the web request, and for the POST request sent by the client, the POST request is divided into two request types of a sensitive request and an insensitive request, the sensitive request is the POST request carrying data parameters which cannot be stolen by an unauthorized user, namely the POST request carrying sensitive data is the sensitive request, and the sensitive data is data which the user wants to protect or data which the user does not want to allow the unauthorized user to steal in the network transmission process. The non-sensitive requests are all POST requests except the sensitive requests, and may include POST requests with parameters in the URL and POST requests without parameters in the URL. In order to solve the problems that requirements of different partners on sensitive data are not completely the same in the related technology, and the individual partners on individual POST requests are required to add parameters on URLs in order to prevent the code change of the individual partners, and simultaneously the service interfaces are required to be expected to return the same data, the method can provide all POST request methods of the service interfaces for users or the partners at the project compiling and constructing stage, provide request configuration files corresponding to the request methods containing the sensitive data in the POST methods by default, namely have corresponding request configuration file formats based on different request types, and generate corresponding POST request configuration files based on the request types according to the corresponding request configuration file formats. For example, during the user login process or when the user password is modified, the user name and the password may be sensitive data, for the configuration file requested by the sensitive data, a form such as [ "login" ] may be added in the configuration file in a key-value form, and during the compiling and packaging process, the configuration file is read, and the contents of the configuration file are written into the project designation directory. In addition, keyword recognition extraction can be carried out on each POST request method provided so as to ensure the identification uniqueness of the method. If the login request comprises a user name and a password as sensitive data, the user name and the password are organized into [/login ] in a configuration file, and the data element set is the specific request content. The method comprises the steps of identifying a POST request method containing security sensitive parameters, configuring a request configuration file according to a certain format, and if the default system contains the request containing the sensitive parameters and no other request method containing the sensitive parameters exists, the default system can not provide the configuration file format. In the project compiling and packaging stage, file reading operation is carried out on the provided request configuration file containing the POST request of the sensitive data, meanwhile, the read data is subjected to writing operation and output to a given catalog of the project, if no corresponding request configuration file is provided, the reading and writing operation of the file is not required to be executed, and a default configuration file is provided under the project.
S102: and reading the POST request configuration file stored in the preset directory into the memory.
And after the project is compiled and packaged, carrying out system installation and deployment, wherein the step is a general step of system installation, deploying the project to equipment for providing services, and simultaneously starting Web container services to complete the system to provide related services. When the service is started, a new thread can be established for searching the POST request configuration file under the given directory of the project, the reading operation of the file is carried out, and the initialization file data of the POST request configuration file can be sent to the memory of the service end. When the POST requests the configuration file to be output to the memory through write operation, the content of the configuration file can be initialized to the memory through a conventional data structure. For example, a set of sequential storage structure security requests may be defined, such as, [/logic,/createUser ]. That is, the memory may include multiple sets of security requests, each set of security requests identifying whether a currently received POST request is a sensitive request or a non-sensitive request.
S103: and when a to-be-processed POST request sent by the client is received, identifying the request type of the to-be-processed POST request based on the POST request configuration file.
In this step, the server may monitor each web request of the client in real time, and when it is detected that the client sends a POST request to be processed to the service interface, intercept the POST request to be processed by using an interceptor, as shown in fig. 2; detecting whether the POST request to be processed is a sensitive request or a non-sensitive request according to a security request set in a memory; the security request set writes the POST request configuration file of S102 into data in the memory according to a preset data storage format, where the preset data storage format is a data structure form of the POST request configuration file in the memory, and a person skilled in the art can customize the POST request configuration file according to actual conditions, which is not limited in this application.
S104: and reading a required parameter value from a request body or a uniform positioning resource character of the POST request to be processed based on the request type of the POST request to be processed and matching with a corresponding copying original request parameter reading mode.
When the service interface provides service for the client, the security judgment is carried out on the initiated request according to the memory data in each Web request, and for the requests with different security degrees, the acquisition processing of parameters under different scenes of the POST request can be met through a duplicated parameter value request algorithm, so that the security processing of the service interface on a sensitive request method is increased, and the expansibility of the service interface processing method is increased. The duplicated parameter value request algorithm is a duplicated original request parameter reading mode corresponding to different request types. In this embodiment, the parameter reading modes corresponding to different requests are different, whether the user' S POST request is a sensitive request is identified by the request configuration file written in the memory in S103, and if the request is a sensitive request, the main parameter data in the URL is not read, but the data in the body of the read request is adopted, so that the data acquisition from the URL is strictly limited. For non-sensitive requests or request methods with parameters in URLs under certain scenes, required parameter values can be read from a request body or the URL according to actual conditions, the requirements of different partners on safe transmission of different sensitive data are met, meanwhile, the expandability of a service interface is increased, and normal request calling in the transmission process of different parameters of POST methods of different partners is met.
In the technical scheme provided by the embodiment of the invention, when different users are docked or integrated to provide services or interface calls, safety requests of different degrees of the different users are identified and marked into configuration files, and data is written into a project specified directory in a mode of reading the request configuration files which are required to contain sensitive data in the POST requests of the users in a project compiling and packaging stage, so that a set of service interface code systems can be realized. Meanwhile, the method adapts to scenes with different security requirements of different users, carries out security judgment on the initiated web request according to the memory data, and obtains parameter values from a request body in a secure mode for requests with different security degrees, such as the request containing sensitive data, so as to meet the requirement of parameter obtaining processing under different scenes of the POST request, thereby not only increasing the security processing of the service interface on the sensitive request method, but also increasing the security of the service interface and simultaneously increasing the expansibility of the service interface processing method. The method is suitable for calling the service interface under various conditions of different parameter transmission, meets the expandability of calling the service interface, maximally meets different calling forms of different users on the premise of ensuring the safety of data transmission, can meet different actual requirements of different users on sensitive requests, and can also meet the requirement of URL with parameters in POST requests of different users.
In the above embodiment, how to execute step S104 is not limited, that is, the method for reading the original Request parameter of the carbon monoxide copy is not limited, and this embodiment provides a method for reading the Request parameter, which can compile a carbon monoxide copy parameter value Request algorithm in advance and then encapsulate the carbon monoxide copy parameter value Request algorithm, for example, a new Class can be developed in a Servlet Class, an Http Servlet Request Class is inherited, a new parameter Request method, that is, a carbon monoxide copy parameter value Request algorithm is developed, and after the Servlet is executed, a subclass object is transferred when a chain transfer Request is requested, and the encapsulated subclass is transferred as a requested Class; and finally, calling a parameter value request algorithm to obtain an effective parameter value in a specific application scene through the transmission parameter in the specific service logic method body of each request. And at the service logic for specifically processing the request, when the specific parameters and the parameter values are acquired, calling a duplicated parameter value request algorithm to directly acquire the parameter values corresponding to the parameters, and then carrying out subsequent logic processing. The method can comprise the following steps:
and acquiring all parameters and corresponding parameter values in a request body and a uniform resource locator of the POST request to be processed and parameter data carried in the uniform resource locator. In this step, for example, a request _ getparameter () method may be used to obtain all parameters and parameter values in the URL and the body, and simultaneously obtain parameter data in the URL, and obtain the number of occurrences of each parameter in the URL and the total number of occurrences in the request.
The POST request to be processed is a sensitive request, and corresponding parameter values are read from a request body based on the received target parameter names.
The POST request to be processed is a non-sensitive request, and if a request body of the POST request to be processed contains target parameters, corresponding parameter values are read from the request body based on the target parameter names; and if the request body of the POST request to be processed does not contain the target parameter and the uniform resource locator contains the target parameter, reading a corresponding parameter value from the uniform resource locator based on the target parameter name.
In this embodiment, the request type, such as a POST request or a GET type request, may be obtained first, and then, for the type of the POST request, it is determined whether the request is a sensitive request or a non-sensitive request. According to the parameter name key of the required data parameter, the sensitive request is strictly limited to obtain data from the URL, and the data in the body of the read request is adopted. For a non-sensitive request or a request method with parameters in a URL under a certain scene, if the parameters are contained in both a body of a request body and the URL, the parameters in the body are used as the standard, and if the parameters are not contained, the parameters obtained in the URL are used as the standard. By the method, the requirements of different partners on the safe transmission of different sensitive data are met, the expandability of the service interface is increased, and the normal request calling in the transmission process of different parameters of the POST method of different partners is met.
In other embodiments of the embodiment of the present invention, the position of the parameter in the POST request may also be located according to the number of times of occurrence of the parameter, so as to save the time for searching the parameter and facilitate improvement of the parameter feedback efficiency, as shown in fig. 3, the method may include:
and counting a first number of times that the target parameter appears in the POST request to be processed and a second number of times that the target parameter appears in the uniform resource locator.
If the first number of times is the same as the second number of times, the target parameter only exists in the uniform resource locator; if the first number is greater than the second number, the target parameter is present in both the uniform resource locator and the requestor.
In this embodiment, if the POST request to be processed is a sensitive request and the required parameters only exist in the URL, the NULL is directly fed back; if the needed parameter exists in the URL and the request body at the same time, the corresponding parameter value is obtained from the request body according to the transmitted parameter name. If the POST request to be processed is not a sensitive request and the required parameter only exists in the URL, the last element of the array of the data stored corresponding to the URL can be fed back, the element is the parameter value of the required parameter, and if the required parameter exists in the URL and the request body at the same time, the corresponding parameter value is obtained from the request body according to the transmitted parameter name.
As another optional implementation manner, flexibility of using the system by the user is improved, a document occupied space is saved, the request configuration file format includes only a sensitive request configuration file format and a request configuration file default format, and one implementation manner of S101 may be:
the service interface is provided for users, and for request configuration file formats of different request types, the default format of the request configuration file may not be provided for users, that is, for a POST request without sensitive data or a POST request without sensitive requirements, the user does not need to provide the corresponding configuration file, and the system automatically generates the configuration file in the default format. In the project compiling and packaging stage, if a POST self-defining request configuration file generated by a user based on a sensitive request configuration file format is received, reading the POST self-defining request configuration file, and overwriting the POST self-defining request configuration file to a preset directory; and if the POST self-defined request configuration file of the user is not received, automatically generating a corresponding POST default request configuration file under a preset directory according to the default format of the request configuration file.
In this embodiment, for a default configuration of a request containing sensitive data, the project system first adopts a default operation security request configuration, such as a request with a username and password operation, and adopts a default value for a request without additional interface security requirement configuration. And in the project compiling and packaging stage, the configuration file is not read by default, if the configuration file is selected, the configuration file is read firstly, and the read content of the POST self-defining request configuration file is output to a project given directory.
It should be noted that, in the present application, there is no strict sequential execution order among the steps, and as long as a logical order is met, the steps may be executed simultaneously or according to a certain preset order, and fig. 1 to fig. 3 are only schematic manners, and do not represent only such an execution order.
The embodiment of the invention also provides a corresponding device for the POST request parameter automatic processing method, thereby further ensuring that the method has higher practicability. Wherein the means can be described separately from the functional module point of view and the hardware point of view. In the following, the POST request parameter automation processing apparatus provided by the embodiment of the present invention is introduced, and the POST request parameter automation processing apparatus described below and the POST request parameter automation processing method described above may be referred to in correspondence with each other.
Based on the angle of the functional module, referring to fig. 4, fig. 4 is a structural diagram of an automatic POST request parameter processing apparatus according to an embodiment of the present invention, in a specific implementation manner, the apparatus may include:
the project compiling module 401 is configured to store a POST request configuration file generated according to a corresponding request configuration file format based on the request type in a preset directory; the request type comprises a sensitive request and an insensitive request, wherein the sensitive request is a POST request carrying data parameters which cannot be stolen by an unauthorized user.
The Web start module 402 is configured to read a POST request configuration file stored in a preset directory into a memory.
And a request identification module 403, configured to, when receiving a to-be-processed POST request sent by a client, identify a request type of the to-be-processed POST request based on a POST request configuration file.
A request parameter reading module 404, configured to read a required parameter value from a request body or a uniform locator resource identifier of the POST request to be processed based on a request type of the POST request to be processed matching a corresponding carbon-copy original request parameter reading manner; the data parameter values of the sensitive requests are only obtained from the request body of the POST request to be processed.
Optionally, in some implementations of this embodiment, the request parameter reading module 404 may include:
the parameter acquisition submodule is used for acquiring all parameters in a request body and a uniform resource locator of the POST request to be processed, corresponding parameter values and parameter data carried in the uniform resource locator;
the sensitive parameter reading sub-module is used for reading a corresponding parameter value from a request body based on a received target parameter name when the POST request to be processed is a sensitive request;
the non-sensitive parameter reading sub-module is used for reading corresponding parameter values from a request body based on a target parameter name if the POST request to be processed is a non-sensitive request and the request body of the POST request to be processed contains the target parameters; and if the request body of the POST request to be processed does not contain the target parameter and the uniform resource locator contains the target parameter, reading a corresponding parameter value from the uniform resource locator based on the target parameter name.
In some implementations of the embodiment of the present invention, the request parameter reading module 404 may further include a parameter positioning sub-module, where the parameter positioning sub-module includes:
the system comprises a counting unit, a processing unit and a processing unit, wherein the counting unit is used for counting a first frequency of occurrence of a target parameter in a POST request to be processed and a second frequency of occurrence in a uniform resource locator;
the positioning unit is used for only existing the target parameter in the uniform resource locator if the first time number is the same as the second time number; if the first number is greater than the second number, the target parameter is present in both the uniform resource locator and the requestor.
As some optional embodiments in the present application, the request identification module 403 may include:
the monitoring submodule is used for monitoring each web request of the client in real time;
the intercepting submodule is used for intercepting the POST request to be processed by an interceptor when the POST request to be processed is sent by the client side;
the identification submodule is used for detecting whether the POST request to be processed is a sensitive request or a non-sensitive request according to the security request set in the memory; the set of security requests is read from a POST request configuration file.
Optionally, in other embodiments of this embodiment, the apparatus may further include:
the file providing module is used for providing the service interface for the user with the request configuration file formats of different request types, wherein the request configuration file formats comprise a sensitive request configuration file format and a request configuration file default format;
the configuration file overwriting module is used for reading the POST self-defining request configuration file and overwriting the POST self-defining request configuration file to a preset directory if the POST self-defining request configuration file generated by a user based on the sensitive request configuration file format is received in the project compiling and packaging stage;
and the configuration file generation module is used for automatically generating a corresponding POST default request configuration file under a preset directory according to the default format of the request configuration file in the project compiling and packaging stage if the POST self-defined request configuration file of the user is not received.
The functions of each functional module of the POST request parameter automation processing apparatus according to the embodiment of the present invention may be specifically implemented according to the method in the foregoing method embodiment, and the specific implementation process may refer to the related description of the foregoing method embodiment, which is not described herein again.
Therefore, the embodiment of the invention effectively improves the expandability of the service interface, not only can meet different practical requirements of different users on sensitive requests, but also can meet the requirements of URL (uniform resource locator) with parameters in POST (POST position) requests of different users.
The POST request parameter automatic processing device mentioned above is described from the perspective of a functional module, and further, the present application also provides a POST request parameter automatic processing device described from the perspective of hardware. Fig. 5 is a block diagram of another POST request parameter automation processing apparatus according to an embodiment of the present application. As shown in fig. 5, the apparatus comprises a memory 50 for storing a computer program;
and a processor 51, configured to implement the steps of the POST request parameter automation processing method mentioned in any of the above embodiments when executing the computer program.
The processor 51 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and the like. The processor 51 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 51 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 51 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed on the display screen. In some embodiments, the processor 51 may further include an AI (Artificial Intelligence) processor for processing computing operations related to machine learning.
Memory 50 may include one or more computer-readable storage media, which may be non-transitory. Memory 50 may also include high speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In this embodiment, the memory 50 is at least used for storing the following computer program 501, wherein after being loaded and executed by the processor 51, the computer program can implement the relevant steps of the POST request parameter automation processing method disclosed in any of the foregoing embodiments. In addition, the resources stored in the memory 50 may also include an operating system 502, data 503, and the like, and the storage manner may be a transient storage manner or a permanent storage manner. Operating system 502 may include Windows, Unix, Linux, etc. Data 503 may include, but is not limited to, data corresponding to test results, and the like.
In some embodiments, the POST request parameter automation device may further include a display screen 52, an input/output interface 53, a communication interface 54, a power supply 55, and a communication bus 56.
Those skilled in the art will appreciate that the configuration shown in FIG. 5 does not constitute a limitation of the POST request parameter automated processing means, and may include more or fewer components than those shown, such as sensors 57.
The functions of each functional module of the POST request parameter automation processing apparatus according to the embodiment of the present invention may be specifically implemented according to the method in the foregoing method embodiment, and the specific implementation process may refer to the related description of the foregoing method embodiment, which is not described herein again.
Therefore, the embodiment of the invention effectively improves the expandability of the service interface, not only can meet different practical requirements of different users on sensitive requests, but also can meet the requirements of URL (uniform resource locator) with parameters in POST (POST position) requests of different users.
It is understood that, if the POST request parameter automation processing method in the above embodiment is implemented in the form of a software functional unit and sold or used as a stand-alone product, it may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application may be substantially or partially implemented in the form of a software product, which is stored in a storage medium and executes all or part of the steps of the methods of the embodiments of the present application, or all or part of the technical solutions. And the aforementioned storage medium includes: a U disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), an electrically erasable programmable ROM, a register, a hard disk, a removable magnetic disk, a CD-ROM, a magnetic or optical disk, and other various media capable of storing program codes.
Based on this, the embodiment of the present invention further provides a computer-readable storage medium, in which a POST request parameter automation processing program is stored, and when the POST request parameter automation processing program is executed by a processor, the steps of the POST request parameter automation processing method according to any one of the above embodiments are provided.
The functions of the functional modules of the computer-readable storage medium according to the embodiment of the present invention may be specifically implemented according to the method in the foregoing method embodiment, and the specific implementation process may refer to the related description of the foregoing method embodiment, which is not described herein again.
Therefore, the embodiment of the invention effectively improves the expandability of the service interface, not only can meet different practical requirements of different users on sensitive requests, but also can meet the requirements of URL (uniform resource locator) with parameters in POST (POST position) requests of different users.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The present application provides a method, an apparatus and a computer-readable storage medium for automated POST request parameter processing. The principles and embodiments of the present invention are explained herein using specific examples, which are presented only to assist in understanding the method and its core concepts. It should be noted that, for those skilled in the art, it is possible to make various improvements and modifications to the present invention without departing from the principle of the present invention, and those improvements and modifications also fall within the scope of the claims of the present application.
Claims (10)
1. A POST request parameter automatic processing method is characterized by comprising the following steps:
reading a POST request configuration file stored in a preset directory in a project compiling and packaging stage into a memory in advance; the POST request configuration file is generated according to a corresponding request configuration file format based on a request type, the request type comprises a sensitive request and an insensitive request, and the sensitive request is a POST request carrying data parameters which cannot be stolen by an unauthorized user;
when a to-be-processed POST request sent by a client is received, identifying the request type of the to-be-processed POST request based on the POST request configuration file;
reading a required parameter value from a request body or a uniform positioning resource character of the POST request to be processed based on the matching of the request type of the POST request to be processed and a corresponding copying original request parameter reading mode; and the data parameter value of the sensitive request is only obtained from the request body of the POST request to be processed.
2. The automated POST request parameter processing method as claimed in claim 1, wherein the step of reading the required parameter values from the request body or the uniform positioning resource identifier of the POST request to be processed based on the request type of the POST request to be processed matching the corresponding carbon copy original request parameter reading manner comprises:
acquiring all parameters and corresponding parameter values in a request body and a uniform resource locator of the POST request to be processed and parameter data carried in the uniform resource locator;
the POST request to be processed is the sensitive request, and corresponding parameter values are read from the request body based on the received target parameter name;
the POST request to be processed is the non-sensitive request, and if a request body of the POST request to be processed contains target parameters, corresponding parameter values are read from the request body based on the target parameter names; and if the request body of the POST request to be processed does not contain the target parameter and the uniform resource locator contains the target parameter, reading a corresponding parameter value from the uniform resource locator based on the target parameter name.
3. The automatic processing method of the POST request parameter according to claim 2, wherein after acquiring all the parameters and corresponding parameter values in the request body and the uniform resource locator of the POST request to be processed, and the parameter data carried in the uniform resource locator, further comprising:
counting a first frequency of the target parameter appearing in the POST request to be processed and a second frequency of the target parameter appearing in the uniform resource locator;
if the first number of times is the same as the second number of times, the target parameter only exists in the uniform resource locator;
if the first number is greater than the second number, the target parameter is present in both the uniform resource locator and the request body.
4. The automated POST request parameter processing method according to claim 3, wherein the identifying the request type of the POST request to be processed based on the POST request configuration file comprises, when receiving the POST request to be processed sent by the client:
monitoring each web request of the client in real time;
when the fact that the client side sends the POST request to be processed is detected, an interceptor is used for intercepting the POST request to be processed;
detecting whether the POST request to be processed is the sensitive request or the non-sensitive request according to the security request set in the memory; the safety request set is data which is obtained by writing the POST request configuration file into the memory according to a preset data storage format.
5. The automated POST request parameter processing method according to any one of claims 1 to 4, wherein before reading the POST request configuration file stored in the preset directory in the item compiling and packaging stage into the memory in advance, the method further comprises:
providing request configuration file formats of a service interface for different request types for a user, wherein the request configuration file formats comprise a sensitive request configuration file format and a request configuration file default format;
in the project compiling and packaging stage, if a POST self-defining request configuration file generated by a user based on the sensitive request configuration file format is received, reading the POST self-defining request configuration file, and overwriting the POST self-defining request configuration file to the preset directory; and if the POST self-defining request configuration file of the user is not received, automatically generating a corresponding POST default request configuration file under the preset directory according to the default format of the request configuration file.
6. An automated POST request parameter processing apparatus, comprising:
the project compiling module is used for storing the POST request configuration file generated according to the corresponding request configuration file format based on the request type in a preset directory; the request type comprises a sensitive request and an insensitive request, wherein the sensitive request is a POST request carrying data parameters which cannot be stolen by an unauthorized user;
the Web starting module is used for reading the POST request configuration file stored in the preset directory into the memory;
the request identification module is used for identifying the request type of the POST request to be processed based on the POST request configuration file when the POST request to be processed sent by the client is received;
a request parameter reading module, configured to read a required parameter value from a request body or a uniform positioning resource identifier of the POST request to be processed based on a request type of the POST request to be processed matching a corresponding carbon-copy original request parameter reading manner; and the data parameter value of the sensitive request is only obtained from the request body of the POST request to be processed.
7. The POST request parameter automation processing device of claim 6, wherein the request parameter reading module comprises:
the parameter acquisition submodule is used for acquiring all parameters and corresponding parameter values in the request body and the uniform resource locator of the POST request to be processed and parameter data carried in the uniform resource locator;
the sensitive parameter reading sub-module is used for reading a corresponding parameter value from the request body based on the received target parameter name, wherein the POST request to be processed is the sensitive request;
a non-sensitive parameter reading sub-module, configured to read a corresponding parameter value from a request body of the POST request to be processed based on a name of a target parameter if the POST request to be processed is the non-sensitive request; and if the request body of the POST request to be processed does not contain the target parameter and the uniform resource locator contains the target parameter, reading a corresponding parameter value from the uniform resource locator based on the target parameter name.
8. The POST request parameter automated processing unit of claim 7, wherein the request parameter reading module further comprises a parameter positioning sub-module, the parameter positioning sub-module comprising:
the counting unit is used for counting a first frequency of the target parameter appearing in the POST request to be processed and a second frequency of the target parameter appearing in the uniform resource locator;
a positioning unit, configured to, if the first number of times is the same as the second number of times, only exist the target parameter in the uniform resource locator; if the first number is greater than the second number, the target parameter is present in both the uniform resource locator and the request body.
9. An automated POST request parameter processing apparatus, comprising a processor configured to implement the steps of the automated POST request parameter processing method according to any one of claims 1 to 5 when executing a computer program stored in a memory.
10. A computer-readable storage medium, wherein the computer-readable storage medium has stored thereon a POST request parameter automation processing program, which when executed by a processor implements the steps of the POST request parameter automation processing method as recited in any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010790354.6A CN112015483B (en) | 2020-08-07 | 2020-08-07 | POST request parameter automatic processing method and device and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010790354.6A CN112015483B (en) | 2020-08-07 | 2020-08-07 | POST request parameter automatic processing method and device and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112015483A CN112015483A (en) | 2020-12-01 |
| CN112015483B true CN112015483B (en) | 2021-12-03 |
Family
ID=73499402
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010790354.6A Active CN112015483B (en) | 2020-08-07 | 2020-08-07 | POST request parameter automatic processing method and device and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112015483B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113660307B (en) * | 2021-07-19 | 2024-01-19 | 中国电子科技集团公司第十五研究所 | Algorithm comprehensive integrated service system |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102246489A (en) * | 2008-10-08 | 2011-11-16 | 思杰系统有限公司 | Systems and methods for connection management for asynchronous messaging over http |
| CN102971712A (en) * | 2010-05-19 | 2013-03-13 | 阿卡麦科技公司 | Edge server HTTP POST message processing |
| CN103501304A (en) * | 2013-10-12 | 2014-01-08 | 深信服网络科技（深圳）有限公司 | Method and device for controlling unauthorized access of web system |
| CN104199725A (en) * | 2014-09-27 | 2014-12-10 | 上海瀚之友信息技术服务有限公司 | Service interface data simulation method and system |
| CN104883357A (en) * | 2015-04-28 | 2015-09-02 | 深信服网络科技（深圳）有限公司 | Method and firewall for preventing HTTP POST flooding attacks |
| CN104967630A (en) * | 2014-04-10 | 2015-10-07 | 腾讯科技（深圳）有限公司 | Method and apparatus for processing webpage access request |
| CN106161521A (en) * | 2015-04-01 | 2016-11-23 | 阿里巴巴集团控股有限公司 | The processing method and processing device of hypertext transfer protocol requests |
| CN106489145A (en) * | 2015-12-28 | 2017-03-08 | 华为技术有限公司 | The access method of web site, device and Web site system |
| CN107797911A (en) * | 2016-09-02 | 2018-03-13 | 北京京东尚科信息技术有限公司 | Method and apparatus for testing HTTP interface |
| CN108762955A (en) * | 2018-05-30 | 2018-11-06 | 平安普惠企业管理有限公司 | Interface call method, device, computer equipment and storage medium |
| CN109359250A (en) * | 2018-08-31 | 2019-02-19 | 阿里巴巴集团控股有限公司 | Uniform resource locator processing method, device, server and readable storage medium storing program for executing |
| CN109688202A (en) * | 2018-12-04 | 2019-04-26 | 北京腾云天下科技有限公司 | A kind of processing method of interface data, calculates equipment and storage medium at device |
| CN110209888A (en) * | 2019-05-08 | 2019-09-06 | 无线生活（杭州）信息科技有限公司 | The storage method and device of interface requests |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090089278A1 (en) * | 2007-09-27 | 2009-04-02 | Krishna Leela Poola | Techniques for keyword extraction from urls using statistical analysis |
| US8612966B2 (en) * | 2007-11-29 | 2013-12-17 | Red Hat, Inc. | Method and system for preparing software offerings having software application code and post-install configuration information |
| US8260637B2 (en) * | 2008-10-03 | 2012-09-04 | The Curators Of The University Of Missouri | System and method for linking a web-based resource with an electronic medical record |
-
2020
- 2020-08-07 CN CN202010790354.6A patent/CN112015483B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102246489A (en) * | 2008-10-08 | 2011-11-16 | 思杰系统有限公司 | Systems and methods for connection management for asynchronous messaging over http |
| CN102971712A (en) * | 2010-05-19 | 2013-03-13 | 阿卡麦科技公司 | Edge server HTTP POST message processing |
| CN103501304A (en) * | 2013-10-12 | 2014-01-08 | 深信服网络科技（深圳）有限公司 | Method and device for controlling unauthorized access of web system |
| CN104967630A (en) * | 2014-04-10 | 2015-10-07 | 腾讯科技（深圳）有限公司 | Method and apparatus for processing webpage access request |
| CN104199725A (en) * | 2014-09-27 | 2014-12-10 | 上海瀚之友信息技术服务有限公司 | Service interface data simulation method and system |
| CN106161521A (en) * | 2015-04-01 | 2016-11-23 | 阿里巴巴集团控股有限公司 | The processing method and processing device of hypertext transfer protocol requests |
| CN104883357A (en) * | 2015-04-28 | 2015-09-02 | 深信服网络科技（深圳）有限公司 | Method and firewall for preventing HTTP POST flooding attacks |
| CN106489145A (en) * | 2015-12-28 | 2017-03-08 | 华为技术有限公司 | The access method of web site, device and Web site system |
| CN107797911A (en) * | 2016-09-02 | 2018-03-13 | 北京京东尚科信息技术有限公司 | Method and apparatus for testing HTTP interface |
| CN108762955A (en) * | 2018-05-30 | 2018-11-06 | 平安普惠企业管理有限公司 | Interface call method, device, computer equipment and storage medium |
| CN109359250A (en) * | 2018-08-31 | 2019-02-19 | 阿里巴巴集团控股有限公司 | Uniform resource locator processing method, device, server and readable storage medium storing program for executing |
| CN109688202A (en) * | 2018-12-04 | 2019-04-26 | 北京腾云天下科技有限公司 | A kind of processing method of interface data, calculates equipment and storage medium at device |
| CN110209888A (en) * | 2019-05-08 | 2019-09-06 | 无线生活（杭州）信息科技有限公司 | The storage method and device of interface requests |
Non-Patent Citations (1)
| Title |
|---|
| 基于SQL注入攻击的Web结构分析;苏丽;《电子技术与软件工程》;20180710;第2018卷(第13期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112015483A (en) | 2020-12-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10409711B2 (en) | Automatically running tests against WEB APIs based on specifications | |
| US10601866B2 (en) | Discovering website phishing attacks | |
| US10636084B2 (en) | Methods and systems for implementing on-line financial institution services via a single platform | |
| IL275042A (en) | Self-adaptive application programming interface level security monitoring | |
| CN113489713B (en) | Network attack detection method, device, equipment and storage medium | |
| EP3712764B1 (en) | Fpga cloud host development method and system | |
| CN109165514B (en) | A kind of risk checking method | |
| CN108696490A (en) | The recognition methods of account permission and device | |
| CA2397849A1 (en) | System and method for computer network uploading | |
| EP1669833B1 (en) | Method of validating a trusted computer system | |
| CN108388802A (en) | A kind of alarm method and warning system of script injection attacks | |
| AU2013357047A1 (en) | Web page variation | |
| EP1875349A1 (en) | Configurable functionality chaining | |
| CN112015483B (en) | POST request parameter automatic processing method and device and readable storage medium | |
| CN108600377A (en) | A kind of pause method of file download, device, terminal and storage medium | |
| CN114978752A (en) | Weak password detection method and device, electronic equipment and computer readable storage medium | |
| CN111314355B (en) | Authentication method, device, equipment and medium of VPN (virtual private network) server | |
| CN110609666B (en) | Printer configuration method and device, electronic equipment and readable storage medium | |
| CN116910336A (en) | Dynamic encrypted data acquisition method, system, computer equipment and storage medium | |
| CN115344889A (en) | Console access method, device, equipment and medium for virtual machine | |
| CN115412345A (en) | Weak password prompt modification method, device, equipment and medium | |
| CN116628696A (en) | Vulnerability detection method based on proxy client and related equipment | |
| CN114253632A (en) | Function call request processing method and device and server | |
| CN113420288A (en) | Container mirror image sensitive information detection system and method | |
| GB2599522A (en) | Server device, server device control method, program, official article determination system, and official article determination system control method |
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 |