CN109117609B - Request intercepting method and device - Google Patents
Request intercepting method and device Download PDFInfo
- Publication number
- CN109117609B CN109117609B CN201811009902.6A CN201811009902A CN109117609B CN 109117609 B CN109117609 B CN 109117609B CN 201811009902 A CN201811009902 A CN 201811009902A CN 109117609 B CN109117609 B CN 109117609B
- Authority
- CN
- China
- Prior art keywords
- user
- verification
- stored
- token information
- processing module
- 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 OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/45—Structures or tools for the administration of authentication
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application discloses a request intercepting method and a device, wherein the method comprises the following steps: receiving a user request; sequentially verifying the verification items corresponding to the user requests; when the verification of any verification item fails, obtaining a failure reason corresponding to the verification item, and storing the failure reason; and calling a unified processing module to enable the unified processing module to acquire the stored failure reason and generate return information containing the failure reason. The method stores the failure reason of any verification project, and utilizes the unified processing module to acquire the stored reason and generate the return message containing the failure reason, thereby reducing the complexity of a development and design mode and reducing the high cost of software development and maintenance.
Description
Technical Field
The present application relates to the field of information data processing technologies, and in particular, to a request intercepting method and apparatus.
Background
When a user operates a certain control on the operation interface, relevant requests, such as query requests, data modification requests and the like, are sent to the server. After receiving a request sent by a user, a server verifies each verification item for the request sent by the user, such as user identity verification, user authority verification, overtime verification and the like, and the request is executed only if the request is legal when each verification item passes; otherwise, the request is intercepted, namely the request is refused to be executed, and a failure reason corresponding to a certain verification item is returned to the user.
Currently, the method for the server to return the failure reason is as follows: when the verification of a certain verification item fails, the server calls a processing module corresponding to the verification item and used for processing the verification failure condition, the processing module adds the failure reason corresponding to the verification item to the return message, and therefore the return message including the failure reason is returned to the user.
For the above request interception method, during software development design, a processing module for processing verification failure needs to be configured for each verification project, that is, a processing module corresponding to each interception reason needs to be configured for each verification project, and each processing module is defined specifically to ensure that each processing module can add the corresponding failure reason to the return message.
Disclosure of Invention
In view of this, the present application provides a request intercepting method and apparatus, so as to solve the problem of high software development and maintenance costs caused by a complicated development and design manner in the prior art.
In order to achieve the above object, the following solutions are proposed:
a method of request interception, the method comprising:
receiving a user request;
sequentially verifying the verification items corresponding to the user requests;
when the verification of any verification item fails, obtaining a failure reason corresponding to the verification item, and storing the failure reason;
and calling a unified processing module to enable the unified processing module to acquire the stored failure reason and generate return information containing the failure reason.
A request intercepting apparatus, the apparatus comprising:
the receiving module is used for receiving a user request;
the verification module is used for sequentially verifying the verification projects corresponding to the user requests, obtaining failure reasons corresponding to the verification projects when the verification of any verification project fails, and storing the failure reasons;
and the unified processing module is used for acquiring the stored failure reason and generating return information containing the failure reason.
In the scheme of the application, for the received user request, all verification projects corresponding to the user request are sequentially verified, when the verification of any verification project fails, failure reasons corresponding to the verification projects are obtained and stored, and then the unified processing module is called to obtain the stored failure reasons and generate a return message containing the failure reasons. Therefore, in the application, the failure reason is stored when the verification of a certain verification project fails, and a unified processing module is subsequently called to uniformly execute the operation of acquiring the storage failure reason and generating the return message according to the failure reason. For software development design, as failure reasons are stored, only one unified processing module is needed to be set and defined, the unified processing module can acquire the failure reasons corresponding to any stored verification project and can generate a return message including the failure reasons according to the failure reasons; compared with the traditional request intercepting method, the scheme does not need to configure the corresponding processing module for each failure reason, and specifically defines each processing module, so that the development design mode is simple, the cost of software development and maintenance is reduced, and the quality of software is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a flowchart of a request intercepting method disclosed in an embodiment of the present application;
FIG. 2 is a flow chart of a method for invoking a unified processing module as disclosed in another embodiment of the present application;
FIG. 3 is a flow chart of a verification method for a verified item as disclosed in an embodiment of the present application;
fig. 4 is a block diagram illustrating a request intercepting apparatus according to an embodiment of the present disclosure.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. 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 application.
An embodiment of the present application provides a request intercepting method, as shown in fig. 1, the method includes:
and S100, receiving a user request.
Specifically, after receiving a user request, the server checks a configuration file struts to determine whether an interception mechanism is configured in the server, that is, whether an interceptor is configured in the server, and when it is determined that the interceptor is configured, the server calls the interceptors to perform verification and interception processing according to an interceptor execution sequence defined in an interceptor stack. Generally, two interceptors are arranged in a server, including a custom interceptor and a system default interceptor.
And S101, sequentially verifying the verification items corresponding to the user requests.
The verification items are sequentially verified according to the verification sequence of the verification items, and the verification items include but are not limited to: the user authority verification item, the Token information Token verification item, the overtime verification item and the like, when all verification items pass verification, the user request is released, and an execution result specific to the user request content is returned to the user.
S102, when the verification of any verification item fails, obtaining a failure reason corresponding to the verification item, and storing the failure reason.
When the verification of any verification item fails, the user request is intercepted, the reason of the failure of the verification item is firstly obtained, and the failure reason is stored. Wherein each verification item has its respective corresponding failure reason.
Preferably, the storing the failure reason specifically includes: and storing the failure reason into a preset multiplexing interface, wherein for the Struts2 open source framework, the preset multiplexing interface is in ActionContext corresponding to the user request, namely storing the failure reason into the ActionContext corresponding to the user request. Since ActionContext is valid in a thread created based on a user request, when the server denies access (or passes an execution request), a reason for denial of interception (or returns an execution result of the request) is returned, and the server automatically fails.
S103, calling a unified processing module to enable the unified processing module to acquire the stored failure reason and generate return information containing the failure reason.
In order to invoke the unified processing module, in the embodiment of the present application, preferably, the unified processing module is invoked by jumping to the unified processing module in a chain jump manner, that is, the unified processing module is invoked, where a specific process is as shown in fig. 2, and includes:
and S1031, obtaining the unified interception identification.
Specifically, take the timeout verification item corresponding to the user request as an example, as shown in the first code segment.
Wherein, the 2 nd row represents the expiration time of obtaining the Token information Token, the 4 th row represents whether the Token time is expired or not, if yes, the interception is executed. First, the reason of the verification failure is obtained, and the failure reason is stored in the multiplexing interface, as shown in line 5, a Map class member is added to the Action Context corresponding to the user request, the Key of the Map is "DataResult", the Value of the Map is "timeout connection", please re-login! "," timeout connection, please re-login! The' is the failure reason corresponding to the overtime verification item. It can be understood that the interception reasons corresponding to other verification items are also stored in the Action Context corresponding to the user request by adopting the above method, so that the multiplexing of the same interface is realized. Line 6 shows that the unified interception identifier "APPResult" is obtained, which is used for different interception reasons.
S1032, determining a unified processing module corresponding to the unified interception identification.
Specifically, a unified interception identifier is configured in a configuration file struts.xml as a chain jump mode, and a jump processing module is configured as a unified processing module, as shown in a code segment two. It can be understood that the request interception method of the present invention is a method implemented by a server executing code segments in each program module, the first code segment is used as a part of a verification module for verifying a verification item, the server calls the verification module to execute first, and when the verification of a certain verification item fails, the obtained unified interception identifier jumps to another program module and executes another program module, and the unified processing module is called to execute the first code segment.
Wherein, line 2 shows that "chain" is adopted to perform Action chain jump configuration on the unified interception identifier "APPResult". Line 3 shows that the unified processing module that jumps to is "AuthProcessAction".
S1033, calling the unified processing module to enable the unified processing module to obtain the stored interception reason and generate return information according to the interception reason and a preset return message format, wherein the return information comprises the interception reason.
The unified processing module comprises the following code segment III.
Wherein, the first row to the seventh row represent the statement variable "json DataResult", the tenth row represents the acquisition of "DataResult" from the multiplexing interface ActionContext, which contains the failure reason, the eleventh row represents the assignment of "DataResult" to the variable "json DataResult" of the foregoing statement, and subsequently, the failure reason is returned to the user through the variable "json DataResult". Specifically, when the return message is generated, the return message is generated according to a preset return message format. The "logjson" flag on line 12 indicates that the process of generating the return message is started, and the preset format of the return message is configured in the configuration file Struts-common.
The fourth line represents that the format configured for the return message is the JSON format, and the generated return message in the JSON format is a set of contents included in the "JSON dataresult" configured for the fifth line. And finally, the server returns the returned message in the JSON format to the user to finish the interception, and the specific reason of the interception is returned to the user.
In the embodiment, the failure reason corresponding to any verification project is stored in the multiplexing interface corresponding to the user request, the skipping is performed in a chain skipping mode, the unified processing module is called to obtain the failure reason stored in the multiplexing interface and generate the return message including the failure reason to be returned to the user, therefore, the same interface is reused for different failure reasons to transmit information, the processing module does not need to be configured separately for each verification failure condition, the development and maintenance cost is reduced, the program system is clearer, the software quality is improved, and the method has higher application value.
In another embodiment of the present application, after receiving the user request, determining the source of the user request to determine whether the source of the user request is a mobile terminal or a web page. The method comprises the steps of determining that a source of a user request is a mobile terminal, carrying out verification interception processing corresponding to the mobile terminal on the user request, and carrying out verification interception processing corresponding to a webpage on the user request when the source of the user request is determined to be the webpage. It can be understood that the hardware environments of the mobile terminal and the computer are different, for example, for a bank, the program development architecture of a bank client running in the mobile terminal and the program development architecture of an online bank based on a computer browser are different, so that the server needs to respectively develop a set of verification interception programs corresponding to their respective program architectures for the mobile terminal and the web page, but the verification interception processes of the two sets of verification interception programs are the same in terms of essential processing modes.
Wherein determining the source of the user request to determine whether the source of the user request is a mobile terminal or a web page comprises: specifically, the action class requested by the user is obtained through code invocation.
Specifically, determining that the source of the user request is a mobile terminal, and invoking the unified processing module to obtain the stored interception reason includes:
the method comprises the steps of obtaining a uniform interception identifier corresponding to a mobile terminal, determining a uniform processing module corresponding to the uniform interception identifier corresponding to the mobile terminal, calling the uniform processing module corresponding to the uniform interception identifier corresponding to the mobile terminal, enabling the uniform processing module corresponding to the uniform interception identifier corresponding to the mobile terminal to obtain stored interception reasons, and generating return information according to the interception reasons and a preset return message format corresponding to the mobile terminal.
The unified interception identifier corresponding to the mobile terminal is "APPResult" recorded in the above embodiment, and the preset return message format corresponding to the mobile terminal is the JSON format recorded in the above embodiment.
Determining that the source of the user request is a webpage, and invoking the unified processing module to obtain the stored interception reason includes:
the method comprises the steps of obtaining a uniform interception identifier corresponding to a webpage, determining a uniform processing module corresponding to the uniform interception identifier corresponding to the webpage, calling the uniform processing module corresponding to the uniform interception identifier corresponding to the webpage so that the uniform processing module corresponding to the uniform interception identifier corresponding to the webpage can obtain the stored interception reason, and generating a return message according to the interception reason and a preset return message format corresponding to the webpage.
The unified interception identifier corresponding to the web page is set to "computerrresult", for example, and the format of the return message corresponding to the preset web page may be set to the format of the web page.
In the embodiment, the source of the received user request is judged so as to perform differentiated processing on the user requests from different sources, so that the user requests from different sources are processed on the same server, the server is multiplexed, and the utilization rate of the server is improved.
In another embodiment of the present application, a manner that a server cache is combined with a database is adopted to check a verification item, where the verification item includes a token information verification item and a timeout verification item, and as shown in fig. 3, verifying the token information verification item and the timeout verification item includes:
s300, judging whether the token information corresponding to the user is stored in the server cache, if the token information corresponding to the user is not stored in the server cache, executing the step S301, and if the token information corresponding to the user is stored in the server cache, executing the step S302.
S301, inquiring whether the token information corresponding to the user is stored in the database, if the token information corresponding to the user is not stored in the database, determining that the verification of the token information verification item fails, and if the token information corresponding to the user is stored in the database, executing the step S303.
S302, judging whether the token information corresponding to the user stored in the server cache is expired or not according to the expiration time of the token information corresponding to the user stored in the server cache, if so, executing a step S303, and if not, executing a step S304.
S303, inquiring expiration time of the token information corresponding to the user stored in the database, judging whether the token information corresponding to the user stored in the database is expired or not, if the token information corresponding to the user stored in the database is expired, determining that the verification of the overtime verification item fails, and if the token information corresponding to the user stored in the database is not expired, executing a step S307.
S304, counting the times of the user request sent by the user, and judging whether the times are less than the preset times.
The counted times are counted aiming at the requests sent by the same user.
S305, if the times are less than the preset times, prolonging the expiration time of the token information corresponding to the user stored in the server cache by the preset time.
S306, if the times are equal to preset times, updating the expiration time of the latest token information corresponding to the user stored in the cache of the server into the database, and clearing the counted times of the user request sent by the user.
S307, prolonging the expiration time of the token information corresponding to the user stored in the database by the preset time, and updating the prolonged expiration time into a server cache.
In the above embodiment, the server cache and the database store the verification information corresponding to each verification item, where the verification information includes token information token of the user and expiration time of the token. When verification is carried out, whether the token of the user exists in the cache of the server is firstly inquired, and if the token does not exist in the cache, whether the token of the user exists in the database is inquired, so that the speed of verifying information inquiry is improved, the inquiry rate of the database is reduced, and the IO times of the database are reduced.
After the token of the user is inquired and stored, whether the token is invalid is further verified, because the user request may come from a mobile terminal such as a mobile phone and the like, the user may move when using an application program, so that a mobile signal base station providing a signal for the user may be changed, and the change of the mobile signal base station may cause a service node corresponding to a background server cluster to change, that is, a server providing a service for the user is changed, and the expiration time of the token of the user stored in the cache in the current server after the change may not be the latest expiration time, so that in order to ensure that the legal request of the user is not intercepted, after the token in the cache is judged to be expired, whether the token of the user in the database is further judged, if the token in the database is also expired, the verification of the overtime verification item is determined to be failed, and the user request is intercepted, otherwise, the execution user request is released. The double expiration time verification mechanism combining the cache and the database further reduces the possibility of error interception and improves the identification accuracy of verification.
Further, when the user request is authenticated as a legal request through verification every time, counting the request times of the user, and when the request times of the user are less than a preset time, such as 5 times, prolonging the token failure time of the user in the cache backwards by a preset time, such as 15 minutes each time; and when the request times of the user are accumulated to 5 times, updating the latest token failure time of the user in the cache into the database, clearing the request times of the user, and restarting counting when the request of the user is received again, so that the consistency of the cache and the database is further improved, and the verification identification is more accurate.
An embodiment of the present application further provides a request intercepting apparatus, as shown in fig. 4, the apparatus includes:
a receiving module 400, configured to receive a user request;
the verification module 401 is configured to sequentially verify the verification items corresponding to the user request, obtain a failure reason corresponding to each verification item when the verification of any verification item fails, and store the failure reason;
a unified processing module 402, configured to obtain the stored failure reason and generate a return message including the failure reason.
The storing, by the verification module 401, the failure reason specifically includes: and storing the failure reason into a preset multiplexing interface. For the Struts2 open source framework, the preset multiplexing interface is ActionContext corresponding to the request.
The verification module 401 obtains a uniform interception identifier corresponding to the verification failure when the verification fails, the server determines a jump mode corresponding to the uniform interception identifier and a jump unified processing module by querying the configuration file, so that the server calls the determined unified processing module 402 to enable the unified processing module 402 to obtain the stored failure reason and generate return information according to the failure reason and a preset return message format, wherein the return information includes the failure reason.
Optionally, the embodiment of the present application further includes a request source determining unit, configured to determine a source of the user request. And when the source of the user request is determined to be the mobile terminal, calling a verification and processing module corresponding to the mobile terminal to verify the user request. And when the source of the user request is determined to be the webpage, calling a verification and processing module corresponding to the webpage to verify the user request.
The principle of the verification module 401 verifying the verification item by combining the server cache and the database is the same as that of the above embodiment, and is not described herein again.
Finally, it should also be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (9)
1. A method for intercepting a request, the method comprising:
receiving a user request;
sequentially verifying the verification items corresponding to the user requests;
when the verification of any verification item fails, obtaining a failure reason corresponding to the verification item, and storing the failure reason;
calling a unified processing module to enable the unified processing module to acquire the stored failure reason and generate return information containing the failure reason;
the verification items comprise token information verification items and overtime verification items;
sequentially verifying the token information verification item and the overtime verification item comprises the following steps:
judging whether token information corresponding to the user is stored in a server cache;
if the token information corresponding to the user is not stored in the server cache, inquiring whether the token information corresponding to the user is stored in a database;
if the token information corresponding to the user is not stored in the database, determining that the verification of the token information verification item fails;
if the token information corresponding to the user is stored in the server cache, judging whether the token information corresponding to the user stored in the server cache is expired according to the expiration time of the token information corresponding to the user stored in the server cache;
if the token information corresponding to the user stored in the server cache is expired, inquiring the expiration time of the token information corresponding to the user stored in the database, and judging whether the token information corresponding to the user stored in the database is expired;
and if the token information corresponding to the user stored in the database is expired, determining that the verification of the overtime verification item fails.
2. The method of claim 1, wherein the storing the cause of failure comprises: and storing the failure reason into a preset multiplexing interface.
3. The method of claim 2, wherein the predetermined multiplexing interface is an ActionContext corresponding to the request.
4. The method of any of claims 1-3, wherein said invoking the unified processing module to obtain the stored reason for the failure comprises:
acquiring a uniform interception identifier;
determining a unified processing module corresponding to the unified interception identification;
and calling the unified processing module to enable the unified processing module to acquire the stored failure reason and generate return information according to the failure reason and a preset return message format, wherein the return information comprises the failure reason.
5. The method according to any one of claims 1-3, wherein before sequentially verifying the verification items corresponding to the user request, the method further comprises: determining that the source of the user request is a mobile terminal;
the calling the unified processing module to acquire the stored failure reason comprises:
the method comprises the steps of obtaining a uniform interception identification corresponding to a mobile terminal, determining a uniform processing module corresponding to the uniform interception identification corresponding to the mobile terminal, and calling the uniform processing module corresponding to the uniform interception identification corresponding to the mobile terminal, so that the uniform processing module corresponding to the uniform interception identification corresponding to the mobile terminal obtains a stored failure reason and generates return information according to the failure reason and a preset return message format corresponding to the mobile terminal.
6. The method according to any one of claims 1-3, wherein before sequentially verifying the verification items corresponding to the user request, the method further comprises: determining that the source of the user request is a webpage;
the calling the unified processing module to acquire the stored failure reason comprises:
the method comprises the steps of obtaining a uniform interception identification corresponding to a webpage, determining a uniform processing module corresponding to the uniform interception identification corresponding to the webpage, and calling the uniform processing module corresponding to the uniform interception identification corresponding to the webpage, so that the uniform processing module corresponding to the uniform interception identification corresponding to the webpage obtains a stored failure reason and generates a return message according to the failure reason and a preset return message format corresponding to the webpage.
7. The method of claim 1, wherein the method further comprises:
if the token information corresponding to the user stored in the server cache is not overdue, counting the times of user requests sent by the user, and judging whether the times are less than preset times or not;
if the times are less than the preset times, prolonging the expiration time of the token information corresponding to the user stored in the server cache by preset time;
if the number of times is equal to a preset number of times, updating the expiration time of the latest token information corresponding to the user stored in the server cache into the database, and clearing the counted number of times of the user request sent by the user;
if the token information corresponding to the user stored in the database is not expired, prolonging the expiration time of the token information corresponding to the user stored in the database by the preset time, and updating the prolonged expiration time into the server cache.
8. A request intercepting apparatus, characterized in that the apparatus comprises:
the receiving module is used for receiving a user request;
the verification module is used for sequentially verifying the verification projects corresponding to the user requests, obtaining failure reasons corresponding to the verification projects when the verification of any verification project fails, and storing the failure reasons;
the unified processing module is used for acquiring the stored failure reason and generating return information containing the failure reason;
the verification items comprise token information verification items and overtime verification items;
the verifying module sequentially verifies the token information verification item and the overtime verification item, and comprises the following steps:
judging whether token information corresponding to the user is stored in a server cache;
if the token information corresponding to the user is not stored in the server cache, inquiring whether the token information corresponding to the user is stored in a database;
if the token information corresponding to the user is not stored in the database, determining that the verification of the token information verification item fails;
if the token information corresponding to the user is stored in the server cache, judging whether the token information corresponding to the user stored in the server cache is expired according to the expiration time of the token information corresponding to the user stored in the server cache;
if the token information corresponding to the user stored in the server cache is expired, inquiring the expiration time of the token information corresponding to the user stored in the database, and judging whether the token information corresponding to the user stored in the database is expired;
and if the token information corresponding to the user stored in the database is expired, determining that the verification of the overtime verification item fails.
9. The apparatus of claim 8, wherein the verifying module storing the failure cause specifically comprises: and storing the failure reason into a preset multiplexing interface.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811009902.6A CN109117609B (en) | 2018-08-31 | 2018-08-31 | Request intercepting method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811009902.6A CN109117609B (en) | 2018-08-31 | 2018-08-31 | Request intercepting method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109117609A CN109117609A (en) | 2019-01-01 |
| CN109117609B true CN109117609B (en) | 2021-01-29 |
Family
ID=64860376
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811009902.6A Active CN109117609B (en) | 2018-08-31 | 2018-08-31 | Request intercepting method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109117609B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110855672A (en) * | 2019-11-15 | 2020-02-28 | 无锡家校邦网络科技有限公司 | JWT-based authorization method capable of being manually cancelled |
| CN112511316B (en) * | 2020-12-08 | 2023-04-07 | 深圳依时货拉拉科技有限公司 | Single sign-on access method and device, computer equipment and readable storage medium |
| CN113610539A (en) * | 2021-08-24 | 2021-11-05 | 上海点融信息科技有限责任公司 | Information notification method, device, system, equipment and storage medium |
| CN114301862B (en) * | 2021-12-31 | 2023-08-22 | 北京字跳网络技术有限公司 | Message expediting method, device, system and storage medium |
| CN116112558A (en) * | 2022-11-21 | 2023-05-12 | 上海浦东发展银行股份有限公司 | Interface interception method and system based on axios |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101754127A (en) * | 2009-12-22 | 2010-06-23 | 中兴通讯股份有限公司 | Message acquiring and processing method, client, server and communication system |
| CN103744680A (en) * | 2014-01-16 | 2014-04-23 | 北京邮电大学 | Method and device for business process processing |
| CN106899969A (en) * | 2017-01-18 | 2017-06-27 | 东南大学常州研究院 | Specific secrecy terminal system implementation method based on iOS system |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8572710B2 (en) * | 2010-03-18 | 2013-10-29 | Microsoft Corporation | Pluggable token provider model to implement authentication across multiple web services |
| US9342672B2 (en) * | 2014-01-29 | 2016-05-17 | Dspace Digital Signal Processing And Control Engineering Gmbh | Computer-implemented method for managing at least one data element in control unit development |
| CN104519069A (en) * | 2014-12-27 | 2015-04-15 | 广州华多网络科技有限公司 | Method and device for intercepting resource requests |
| GB2538518B (en) * | 2015-05-19 | 2017-12-27 | Avecto Ltd | Computer device and method for controlling access to a resource via a security system |
| CN107426181B (en) * | 2017-06-20 | 2019-09-17 | 竞技世界（北京）网络技术有限公司 | The hold-up interception method and device of malice web access request |
| CN108038213A (en) * | 2017-12-21 | 2018-05-15 | 中国农业银行股份有限公司 | A kind of method of data processing, client, server and system |
-
2018
- 2018-08-31 CN CN201811009902.6A patent/CN109117609B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101754127A (en) * | 2009-12-22 | 2010-06-23 | 中兴通讯股份有限公司 | Message acquiring and processing method, client, server and communication system |
| CN103744680A (en) * | 2014-01-16 | 2014-04-23 | 北京邮电大学 | Method and device for business process processing |
| CN106899969A (en) * | 2017-01-18 | 2017-06-27 | 东南大学常州研究院 | Specific secrecy terminal system implementation method based on iOS system |
Non-Patent Citations (2)
| Title |
|---|
| interposed request routing for scalable network storage;Anderson, DC 等;《ACM TRANSACTIONS ON COMPUTER SYSTEMS》;20021231;第20卷(第1期);全文 * |
| 基于Struts2框架的Web应用开发研究;余银山 等;《软件开发设计》;20090805;第5卷(第16期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109117609A (en) | 2019-01-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109117609B (en) | Request intercepting method and device | |
| US7796742B1 (en) | Systems and methods for simplified provisioning | |
| CN110602056B (en) | Service parameter transmission method and device | |
| US20040073661A1 (en) | Counting and billing mechanism for web-services based on a soap-communication protocol | |
| CN111726370B (en) | Method, system and device for automatically switching block chain consensus protocol | |
| WO2018052914A1 (en) | Deployment of applications conforming to application data sharing and decision service platform schema | |
| US7996840B2 (en) | Method, system, and apparatus for scheduling pattern based web services | |
| US7533383B2 (en) | Method, system, and apparatus for scheduling pattern based web services | |
| CN115525677A (en) | Data caching method and device, computer equipment and storage medium | |
| WO2007054129A1 (en) | A system for maintaining data | |
| CN111538483B (en) | Data processing method, device, server and readable storage medium | |
| CN115098528B (en) | Service processing method, device, electronic equipment and computer readable storage medium | |
| CN112733001A (en) | Method and device for acquiring subscription information and electronic equipment | |
| CN113467891A (en) | Service processing method, device and storage medium | |
| CN115811481B (en) | Interactive service testing method and device, computer equipment and storage medium | |
| CN118353628A (en) | Block chain data processing method, device, computer equipment, medium and product | |
| CN105141586A (en) | Method and system for verifying user | |
| CN113239297A (en) | Message pushing method, system and storage medium | |
| CN115277263A (en) | Data processing system, method and device for authority authentication | |
| CN112434242B (en) | Statistical method, device, server and storage medium of application program downloading channel | |
| KR101385608B1 (en) | Transaction pursuit system and control method thereof | |
| US8407346B2 (en) | Service facade design and implementation | |
| CN111338969A (en) | Method and system for dynamically matching and modifying request parameters based on regular pattern | |
| CN111651469A (en) | Method and device for managing block chain system contract | |
| CN111666165B (en) | Method, device, equipment and storage medium for calling functions between applications |
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 | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20221110 Address after: 100005 No. 69, inner main street, Dongcheng District, Beijing, Jianguomen Patentee after: AGRICULTURAL BANK OF CHINA Patentee after: Agricultural Bank of China Financial Technology Co.,Ltd. Address before: 100005 No. 69, inner main street, Dongcheng District, Beijing, Jianguomen Patentee before: AGRICULTURAL BANK OF CHINA |
|
| TR01 | Transfer of patent right |