CN106878311B - HTTP message rewriting method and device - Google Patents
HTTP message rewriting method and device Download PDFInfo
- Publication number
- CN106878311B CN106878311B CN201710097641.7A CN201710097641A CN106878311B CN 106878311 B CN106878311 B CN 106878311B CN 201710097641 A CN201710097641 A CN 201710097641A CN 106878311 B CN106878311 B CN 106878311B
- Authority
- CN
- China
- Prior art keywords
- rewriting
- content
- header
- header field
- parameter
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- 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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer And Data Communications (AREA)
Abstract
The application provides a method and a device for rewriting HTTP (hyper text transport protocol) messages, wherein the method comprises the following steps: determining a pre-configured rewriting parameter corresponding to a received HTTP message and a header field corresponding to the rewriting parameter in the HTTP message; determining a dynamic value of the rewriting parameter; and executing rewriting operation on the header field according to the dynamic numerical value. By the technical scheme, when the numerical value of the header field needing to be rewritten is dynamically changed, the correctness of the rewriting operation executed by the load balancing equipment is ensured, and the dynamic rewriting of the HTTP message is realized.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for rewriting an HTTP message.
background
in the related art, the load balancing device may modify an HTTP (HyperText Transfer Protocol) packet according to a need of a server or a client, that is, execute a rewrite operation.
however, since in the related art, the load balancing device performs the rewriting operation on the received HTTP message according to the pre-configured fixed session information, the load balancing device cannot perform the correct rewriting operation when the session information changes.
Disclosure of Invention
in view of this, the present application provides a method and an apparatus for rewriting an HTTP message, which can dynamically rewrite the HTTP message according to a change of session information.
in order to achieve the above purpose, the present application provides the following technical solutions:
according to a first aspect of the present application, a method for rewriting an HTTP message is provided, which is applied to a load balancing device, and the method includes:
determining a pre-configured rewriting parameter corresponding to a received HTTP message and a header field corresponding to the rewriting parameter in the HTTP message;
Determining a dynamic value of the rewriting parameter;
and executing rewriting operation on the header field according to the dynamic numerical value.
according to a second aspect of the present application, a rewriting apparatus of an HTTP message is provided, which is applied to a load balancing device, and the apparatus includes:
The device comprises a first determining unit, a second determining unit and a judging unit, wherein the first determining unit determines pre-configured rewriting parameters corresponding to a received HTTP message and header fields corresponding to the rewriting parameters in the HTTP message;
a second determination unit that determines a dynamic value of the overwrite parameter;
And the rewriting unit is used for executing rewriting operation on the header field according to the dynamic numerical value.
as can be seen from the above technical solutions, in the technical solution of the present application, after receiving the HTTP message, the session information corresponding to the rewrite parameter is analyzed to obtain a dynamic value of the rewrite parameter, and then the rewrite operation is performed on the header field corresponding to the rewrite parameter in the HTTP message according to the dynamic value, thereby implementing dynamic rewrite of the HTTP message.
because the rewriting mode in the related technology is based on the mapping relation of 'header field-rewriting content', the rewriting content must be fixed, otherwise, the mapping relation cannot be established; in contrast, the present application is based on "header field-rewriting parameter-rewriting content (dynamic numerical value)", and through the direction of the rewriting parameter to the rewriting content, the mapping relationship between the rewriting content and the header field can be established and maintained no matter how the rewriting content changes, thereby implementing the rewriting operation on the header field.
Drawings
Fig. 1 is a flowchart of a related art load balancing apparatus performing an overwrite operation.
Fig. 2 is a flowchart illustrating a method for rewriting an HTTP message according to an exemplary embodiment of the present application.
Fig. 3 is a flowchart illustrating another HTTP message rewriting method according to an exemplary embodiment of the present application.
Fig. 4 is a schematic structural diagram of an electronic device according to an exemplary embodiment of the present application.
Fig. 5 is a block diagram illustrating an apparatus for rewriting an HTTP message according to an exemplary embodiment of the present application.
Detailed Description
reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
Fig. 1 is a flowchart of a related art load balancing device performing an overwrite operation, and as shown in fig. 1, the overwrite process may include the following steps:
In step 101, the rewritten content is obtained.
The rewriting content (for example, changing the value of any header field, adding or deleting any header field) is configured in advance by an administrator after the load balancing device is started, that is, the content of performing the rewriting operation on the received HTTP message is fixed and unchanged.
Step 102, the location information of the header field is obtained.
the load balancing equipment analyzes the received HTTP message to determine the position information of the header field needing to be rewritten.
And 103, performing rewriting operation on the header field according to the rewriting content.
It can be seen that the rewriting manner in the related art is based on the mapping relationship of "header field — rewritten content", so that the rewritten content must be fixed, otherwise the mapping relationship cannot be established. Because the pre-configured rewriting content is fixed and unchangeable, the load balancing device cannot specifically adjust the rewriting content according to the received HTTP message or the current session. For example, the HOST field in the received HTTP message needs to be replaced with the IP address and port of the server, and when the IP address and port of the server change dynamically, the load balancing device cannot perform correct rewriting operation, that is, cannot replace the HOST field in the HTTP message with the IP address and port of the current server.
accordingly, the present application solves the above-described technical problems in the related art by improving a manner of configuring the rewritten contents. For further explanation of the present application, the following examples are provided:
Fig. 2 is a flowchart illustrating an HTTP message rewriting method according to an exemplary embodiment of the present application, where the rewriting method may be applied to a load balancing device, as shown in fig. 2, where the rewriting method may include the following steps:
Step 201, determining a pre-configured rewrite parameter corresponding to a received HTTP message, and a header field corresponding to the rewrite parameter in the HTTP message.
in the present embodiment, the types of the rewriting parameter include a request to rewrite content and a response to rewrite content; the request rewriting content is rewriting content aiming at an HTTP request message, and the response rewriting content is rewriting content aiming at an HTTP response message; wherein the request to rewrite the content comprises at least one of: inserting a header, deleting a header, rewriting a URI, inserting a certificate; the responsive overwrite content comprises at least one of: insert header, delete header, rewrite payload.
Step 202, determining the dynamic value of the rewriting parameter.
In this embodiment, when the rewrite parameter corresponds to specific session information, the specific session information of the session to which the HTTP message belongs is analyzed, and a dynamic value of the rewrite parameter is determined according to an analysis result. Wherein the session information includes at least one of: URI, HOST name, HOST port, client IP address, client port, physical server IP address, physical server port, virtual server IP address, virtual server port. The dynamic numerical value of the rewriting parameter is determined by analyzing the session information of the HTTP message, so that the determined dynamic numerical value is used for executing the rewriting operation on the header field, and the correctness of the rewriting operation executed by the load balancing equipment can be ensured when the numerical value of the header field needing to be rewritten is dynamically changed.
Step 203, executing rewriting operation to the header field according to the dynamic value.
in this embodiment, the load balancing device first obtains the location information of the header field, and then replaces the original numerical value of the header field with the dynamic numerical value according to the obtained location information.
as can be seen from the above technical solutions, in the technical solution of the present application, after receiving the HTTP message, the session information corresponding to the rewrite parameter is analyzed to obtain a dynamic value of the rewrite parameter, and then the rewrite operation is performed on the header field corresponding to the rewrite parameter in the HTTP message according to the dynamic value, thereby implementing dynamic rewrite of the HTTP message.
In summary, the rewriting manner in the related art is based on the mapping relationship of the "header field-rewriting content", so that the rewriting content must be fixed, otherwise, the mapping relationship cannot be established; in contrast, the present application is based on "header field-rewriting parameter-rewriting content (dynamic numerical value)", and through the direction of the rewriting parameter to the rewriting content, the mapping relationship between the rewriting content and the header field can be established and maintained no matter how the rewriting content changes, thereby implementing the rewriting operation on the header field.
for easy understanding, the technical solution of the present application is described in detail below with reference to fig. 3. Referring to fig. 3, fig. 3 is a flowchart illustrating another HTTP message rewriting method according to an exemplary embodiment of the present application, where the rewriting method may be applied to a load balancing device, and as shown in fig. 3, the rewriting method may include the following steps:
Step 301, determining preconfigured overwrite parameters corresponding to the received HTTP message.
In this embodiment, the content of rewriting the received HTTP message is marked by defining in advance the correspondence between the rewriting parameter and the session information, where each rewriting parameter corresponds to different session information. Wherein the types of rewrite parameters include a request to rewrite content and a response to rewrite content; the request rewriting content is rewriting content aiming at the HTTP request message, and the response rewriting content is rewriting content aiming at the HTTP response message. Specifically, the request for rewriting the content includes at least one of: inserting a header, deleting a header, rewriting a URI, inserting a certificate; the response rewrite includes at least one of: insert header, delete header, rewrite payload.
For example, the correspondence between the rewriting parameters and the session information as shown in table 1 may be defined:
TABLE 1
For example, $ (rs _ ip): and $ (rs _ port), assuming that the type is a request for rewriting content, specifically, a rewriting header, the rewriting parameter indicates that the name and port of the HOST field in the HTTP request message are modified to be a physical server IP address and a physical server port, respectively.
At step 302, a header field is determined.
In this embodiment, after determining the pre-configured rewrite parameter, a header field corresponding to the rewrite parameter in the received HTTP message is determined according to the session information corresponding to the rewrite parameter. For example, assume that the preconfigured rewrite parameter is $ (rs _ ip): and $ (rs _ port), the type is a request to rewrite the content, specifically, rewrite the header. Then, it is determined that the session information corresponding to the rewriting parameter is the IP address and the port of the physical server, and then it is determined that the HOST field in the HTTP request message needs to be modified according to the session information.
step 303, determine the dynamic value.
in this embodiment, when the rewrite parameter corresponds to the specific session information, the specific session information in the session to which the HTTP message belongs is analyzed, and the dynamic value of the rewrite parameter is determined according to the analysis result. For example, in one case, the HOST field in the HTTP request message needs to be rewritten, and the preconfigured rewrite parameter is $ (rs _ ip): and $ (rs _ port), the type is a request to rewrite the content, specifically, rewrite the header. It is assumed that in the HTTP request message sent by the client and received by the load balancing device, the name of the HOST field is 10.20.5.24, and the port is 80. Since the preconfigured rewrite parameter is $ (rs _ ip): and $ rs _ port, so the IP address and port of the currently hit physical server of the session to which the HTTP request message belongs need to be analyzed, and the HOST field needs to be rewritten according to the IP address and port of the currently hit physical server. Assuming that the IP address of the physical server currently hit is 10.30.5.24 and the port is 80, the name of the HOST field in the HTTP request message needs to be modified to 10.30.5.24. After the rewrite operation is performed, the name of the HOST field in the HTTP request message is 10.30.5.24, and the port is 80.
In another case, if a port of the HOST field in the HTTP response message needs to be deleted, the pre-configured rewrite parameter is $ (HOST _ name), and the type is a response rewrite content, specifically, a rewrite header. Assume that in the HTTP response message received by the load balancing device, the HOST field is "10.30.5.97: 80\ r \ n", that is, the name of the HOST field is 10.30.5.97, and the port is 80. Since the pre-configured rewrite parameter is $ (HOST _ name), only the name of the HOST field is included and no port number is included (the content of the original HOST field is modified to the name of the HOST field), after the rewrite operation is performed on the HOST field in the HTTP response message, the HOST field is modified to "10.30.5.97 \ r \ n". When the rewriting parameter is in other cases, the process is similar to the above example, and is not described again here.
as can be seen from the above technical solutions, in the technical solution of the present application, after receiving an HTTP message, the session information corresponding to the rewrite parameter is analyzed to obtain a dynamic value of the rewrite parameter, and then the rewrite operation is performed on the header field corresponding to the rewrite parameter in the HTTP message according to the dynamic value, so that when the value of the header field to be rewritten changes dynamically, the correctness of the rewrite operation performed by the load balancing device is ensured, and the dynamic rewrite of the HTTP message is achieved. In summary, the rewriting manner in the related art is based on the mapping relationship between the "header field and the rewritten content", so that the rewritten content must be fixed, otherwise, the mapping relationship cannot be established; in contrast, the present application is based on "header field-rewriting parameter-rewriting content (dynamic numerical value)", and through the direction of the rewriting parameter to the rewriting content, the mapping relationship between the rewriting content and the header field can be established and maintained no matter how the rewriting content changes, thereby implementing the rewriting operation on the header field.
FIG. 4 shows a schematic block diagram of an electronic device according to an exemplary embodiment of the present application. Referring to fig. 4, at the hardware level, the electronic device includes a processor 402, an internal bus 404, a network interface 406, a memory 408 and a non-volatile memory 410, but may also include hardware required for other services. The processor 402 reads the corresponding computer program from the non-volatile memory 410 into the memory 408 and then runs the computer program to form a rewriting device of the HTTP message on a logical level. Of course, besides the software implementation, the present application does not exclude other implementations, such as logic devices or a combination of software and hardware, and the like, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.
Referring to fig. 5, in a software implementation, the apparatus for rewriting HTTP messages may include a first determining unit 501, a second determining unit 502, and a rewriting unit 503. Wherein:
A first determining unit 501, configured to determine a pre-configured rewrite parameter corresponding to a received HTTP message, and a header field corresponding to the rewrite parameter in the HTTP message;
a second determination unit 502 that determines a dynamic value of the rewriting parameter;
the rewriting unit 503 performs a rewriting operation on the header field according to the dynamic value.
optionally, the second determining unit 502 is specifically configured to:
When the rewriting parameter corresponds to specific session information, analyzing the specific session information of the session to which the HTTP message belongs;
And determining the dynamic numerical value of the rewriting parameter according to the analysis result.
optionally, the session information includes at least one of:
URI, HOST name, HOST port, client IP address, client port, physical server IP address, physical server port, virtual server IP address, virtual server port.
Optionally, the rewriting unit 503 is specifically configured to:
Acquiring the position information of the header field;
And replacing the original numerical value of the header field with the dynamic numerical value according to the acquired position information.
Optionally, the type of the rewriting parameter includes a request to rewrite the content and a response to rewrite the content; the request rewriting content is rewriting content aiming at an HTTP request message, and the response rewriting content is rewriting content aiming at an HTTP response message;
Wherein the request to rewrite the content comprises at least one of: inserting a header, deleting a header, rewriting a URI, inserting a certificate;
the responsive overwrite content comprises at least one of: insert header, delete header, rewrite payload.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
the above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (8)
1. A rewriting method of an HTTP message is applied to a load balancing device, and the method comprises the following steps:
determining a pre-configured rewriting parameter corresponding to a received HTTP message and a header field corresponding to the rewriting parameter in the HTTP message; the pre-configured rewriting parameters correspond to session information, and the session information corresponds to a header field in the HTTP message and is different from the header field corresponding to the rewriting parameters;
Determining a dynamic numerical value of the rewriting parameter according to a header field corresponding to the session information;
executing rewriting operation on the header field of the rewriting parameter according to the dynamic numerical value;
The session information includes at least one of:
URI, HOST name, HOST port, client IP address, client port, physical server IP address, physical server port, virtual server IP address, virtual server port.
2. The method of claim 1, wherein determining the dynamic value of the overwrite parameter comprises:
when the rewriting parameter corresponds to specific session information, analyzing the specific session information of the session to which the HTTP message belongs;
And determining the dynamic numerical value of the rewriting parameter according to the analysis result.
3. The method of claim 1, wherein the performing the rewrite operation on the header field according to the dynamic value comprises:
acquiring the position information of the header field;
And replacing the original numerical value of the header field with the dynamic numerical value according to the acquired position information.
4. the method of claim 1, wherein the type of overwrite parameter comprises a request to overwrite content and a response to overwrite content; the request rewriting content is rewriting content aiming at an HTTP request message, and the response rewriting content is rewriting content aiming at an HTTP response message;
Wherein the request to rewrite the content comprises at least one of: inserting a header, deleting a header, rewriting a URI, inserting a certificate;
The responsive overwrite content comprises at least one of: insert header, delete header, rewrite payload.
5. An apparatus for rewriting HTTP packet, the apparatus being applied to a load balancing device, the apparatus comprising:
the device comprises a first determining unit, a second determining unit and a judging unit, wherein the first determining unit determines pre-configured rewriting parameters corresponding to a received HTTP message and header fields corresponding to the rewriting parameters in the HTTP message; the pre-configured rewriting parameters correspond to session information, and the session information corresponds to a header field in the HTTP message and is different from the header field corresponding to the rewriting parameters; the session information includes at least one of: URI, HOST name, HOST port, client IP address, client port, physical server IP address, physical server port, virtual server IP address, virtual server port;
the second determining unit is used for determining the dynamic numerical value of the rewriting parameter according to the header field corresponding to the session information;
And the rewriting unit is used for executing rewriting operation on the head field of the rewriting parameter according to the dynamic numerical value.
6. The apparatus according to claim 5, wherein the second determining unit is specifically configured to:
When the rewriting parameter corresponds to specific session information, analyzing the specific session information of the session to which the HTTP message belongs;
and determining the dynamic numerical value of the rewriting parameter according to the analysis result.
7. The apparatus according to claim 5, wherein the rewrite unit is specifically configured to:
Acquiring the position information of the header field;
And replacing the original numerical value of the header field with the dynamic numerical value according to the acquired position information.
8. the apparatus of claim 5, wherein the type of overwrite parameter comprises a request to overwrite content and a response to overwrite content; the request rewriting content is rewriting content aiming at an HTTP request message, and the response rewriting content is rewriting content aiming at an HTTP response message;
wherein the request to rewrite the content comprises at least one of: inserting a header, deleting a header, rewriting a URI, inserting a certificate;
The responsive overwrite content comprises at least one of: insert header, delete header, rewrite payload.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710097641.7A CN106878311B (en) | 2017-02-22 | 2017-02-22 | HTTP message rewriting method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710097641.7A CN106878311B (en) | 2017-02-22 | 2017-02-22 | HTTP message rewriting method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106878311A CN106878311A (en) | 2017-06-20 |
| CN106878311B true CN106878311B (en) | 2019-12-06 |
Family
ID=59168516
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710097641.7A Active CN106878311B (en) | 2017-02-22 | 2017-02-22 | HTTP message rewriting method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106878311B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109936624B (en) * | 2019-01-31 | 2022-03-18 | 平安科技（深圳）有限公司 | Adaptation method and device for HTTP request message header and computer equipment |
| CN113179317B (en) * | 2021-04-27 | 2023-02-07 | 杭州迪普科技股份有限公司 | Test system and method for content rewriting device |
| CN114051022A (en) * | 2021-11-17 | 2022-02-15 | 山石网科通信技术股份有限公司 | HTTP request processing method and device |
| CN115190011B (en) * | 2022-07-05 | 2024-02-27 | 中电金信软件有限公司 | Message processing method and device, electronic equipment and storage medium |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4179535B2 (en) * | 2002-09-03 | 2008-11-12 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Network system, reverse proxy, computer apparatus, data processing method and program |
| US8726369B1 (en) * | 2005-08-11 | 2014-05-13 | Aaron T. Emigh | Trusted path, authentication and data security |
| CN101247395B (en) * | 2008-03-13 | 2011-03-16 | 武汉理工大学 | ISAPI access control system for Session ID fully transparent transmission |
| CN101783771A (en) * | 2010-03-24 | 2010-07-21 | 杭州华三通信技术有限公司 | Method and equipment for realizing load balance continuity |
-
2017
- 2017-02-22 CN CN201710097641.7A patent/CN106878311B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN106878311A (en) | 2017-06-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10693734B2 (en) | Traffic pattern detection and presentation in container-based cloud computing architecture | |
| KR102045136B1 (en) | Custom Communication Channels for Application Deployment | |
| CN107948314B (en) | Business processing method and device based on rule file and server | |
| CN106878311B (en) | HTTP message rewriting method and device | |
| US9397901B2 (en) | Methods, systems, and computer readable media for classifying application traffic received at a network traffic emulation device that emulates multiple application servers | |
| EP3557844A1 (en) | Rule-based network-threat detection | |
| US9455888B2 (en) | Application topology based on network traffic | |
| US20180165258A1 (en) | Methods for improved auditing of web sites and devices thereof | |
| US11799849B2 (en) | Secure web application delivery platform | |
| CN105939284B (en) | The matching process and device of message control strategy | |
| JP2009017298A (en) | Data analysis apparatus | |
| CN109446801B (en) | Method, device, server and storage medium for detecting simulator access | |
| CN104683457A (en) | Concurrency control method and device | |
| CN115543479A (en) | Interface calling analysis method and device suitable for dynamic parameters | |
| EP3740869B1 (en) | Automated distribution of models for execution on a non-edge device and an edge device | |
| CN113536168B (en) | Component processing method and device | |
| US20210152525A1 (en) | Generating an application-based proxy auto configuration | |
| US11134117B1 (en) | Network request intercepting framework for compliance monitoring | |
| CN115314319B (en) | Network asset identification method and device, electronic equipment and storage medium | |
| CN113179251A (en) | Front-end file processing method, device, equipment and machine-readable storage medium | |
| US11895177B2 (en) | State extractor for middlebox management system | |
| US20200145379A1 (en) | Efficient matching of feature-rich security policy with dynamic content using incremental precondition changes | |
| KR101305755B1 (en) | Appatatus and method for filtering execution of script based on address | |
| CN115037572B (en) | Application request identification method and device | |
| US11882171B2 (en) | Instanced web servers for displaying custom content in a secure context |
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 |