CN109634756B - Page event processing method, device, computer equipment and storage medium - Google Patents
Page event processing method, device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN109634756B CN109634756B CN201811417812.0A CN201811417812A CN109634756B CN 109634756 B CN109634756 B CN 109634756B CN 201811417812 A CN201811417812 A CN 201811417812A CN 109634756 B CN109634756 B CN 109634756B
- Authority
- CN
- China
- Prior art keywords
- request
- target control
- control
- event
- preset
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 18
- 238000012545 processing Methods 0.000 claims abstract description 63
- 238000000034 method Methods 0.000 claims abstract description 31
- 230000000873 masking effect Effects 0.000 claims description 43
- 238000004590 computer program Methods 0.000 claims description 17
- 238000012544 monitoring process Methods 0.000 claims description 11
- 238000009825 accumulation Methods 0.000 claims description 3
- 230000002159 abnormal effect Effects 0.000 claims 1
- 238000004806 packaging method and process Methods 0.000 claims 1
- 230000008569 process Effects 0.000 description 10
- 230000006870 function Effects 0.000 description 5
- 230000006399 behavior Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000005856 abnormality Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
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/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
Abstract
The invention discloses a page event processing method, a page event processing device, computer equipment and a storage medium. The method comprises the following steps: generating an event request of a target control; acquiring identification information of controls which allow a user to operate and historical operation times of each control in a preset operation time period; if the identification information of the control which allows the user to operate has the same identification information as the identification information of the target control, marking the event request as an effective event request; acquiring a control operation type of a target control; determining request attributes of the effective event requests according to the control operation types of the target controls and the historical operation times corresponding to the target controls; and if the request attribute of the effective event request is a frequent request, carrying out shielding processing on the effective event request. The technical scheme of the invention can avoid sending a large number of repeated event requests to the background server, reduce the system load and improve the processing efficiency; meanwhile, the safety of page event processing can be improved.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and apparatus for processing a page event, a computer device, and a storage medium.
Background
In daily internet applications, web browsing and web operations are indispensable, and many internet applications provide page controls on pages for information interaction with users, and users can interact with the internet applications by clicking the page controls.
However, in the current internet application, effective monitoring of clicking operation of a page control is not available, when misoperation of multiple clicks of a user or malicious continuous clicking and other attack behaviors occur, a large number of identical event requests are generated, and the event requests are sent to a background server for processing at almost the same time, so that the system load is increased, and the system processing efficiency is affected.
Disclosure of Invention
The embodiment of the invention provides a page event processing method, a device, computer equipment and a storage medium, which are used for solving the problems that the effective monitoring of the clicking operation of a page control is not available at present, so that a large number of identical event requests are generated by the page control, and further the system load is increased and the processing efficiency is reduced.
A method of processing a page event, comprising:
if the clicking operation of a user on a target control in a page is detected, generating an event request of the target control, wherein the event request comprises identity information of the user and identification information of the target control;
acquiring identification information of controls allowing the user to operate and historical operation times of each control in a preset operation time period from a preset user permission data table according to the identity information of the user;
if the identification information of the control allowing the user to operate has the same identification information as the identification information of the target control, marking the event request as an effective event request;
acquiring a control operation type of the target control from a preset control attribute table;
determining a request attribute of the effective event request according to the control operation type of the target control and the historical operation times corresponding to the target control;
if the request attribute of the effective event request is a frequent request, shielding the effective event request;
and if the request attribute of the effective event request is a normal request, sending the effective event request to a preset execution port for processing.
A page event processing apparatus, comprising:
the event request module is used for generating an event request of a target control if the click operation of a user on the target control in a page is detected, wherein the event request comprises the identity information of the user and the identification information of the target control;
the permission acquisition module is used for acquiring identification information of controls which are allowed to be operated by the user from a preset user permission data table according to the identity information of the user, and historical operation times of each control in a preset operation time period;
the request valid module is used for marking the event request as a valid event request if the identification information of the control allowing the user to operate has the same identification information as the identification information of the target control;
the type acquisition module is used for acquiring the control operation type of the target control from a preset control attribute table;
the attribute determining module is used for determining the request attribute of the effective event request according to the control operation type of the target control and the historical operation times corresponding to the target control;
the exception shielding module is used for shielding the effective event request if the request attribute of the effective event request is a frequent request;
And the normal processing module is used for sending the effective event request to a preset execution port for processing if the request attribute of the effective event request is a normal request.
A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the page event processing method described above when the computer program is executed.
A computer readable storage medium storing a computer program which when executed by a processor implements the steps of the page event processing method described above.
In the method, the device, the computer equipment and the storage medium for processing the page event, after detecting the click operation of a user on a target control in a page and generating an event request of the target control, a client determines identification information of the control which allows the user to operate according to identity information of the user contained in the event request and historical operation times of each control in a preset operation time period, and marks the event request as an effective event request if the identification information of the control which allows the user to operate has the same identification information as the identification information of the target control; and then, acquiring a control operation type of the target control from a preset control attribute table, determining a request attribute of an effective event request according to the control operation type and the historical operation times corresponding to the target control, shielding the effective event request if the request attribute of the effective event request is a frequent request, and transmitting the effective event request to a preset execution port for processing if the request attribute of the effective event request is a normal request. Whether the target control belongs to a repeatable type and the combination of historical operation times are judged, whether an effective event request is a frequent request is determined, and then the frequent request is shielded, so that the client can timely identify the misoperation or malicious continuous attack and other attack behaviors of a user on the target control, and a large number of repeated event requests are prevented from being sent to a background server, thereby reducing the system load and improving the processing efficiency; meanwhile, whether the user has permission to operate the target control or not is determined according to the control operation permission of the user, so that the safety of processing the page event can be improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the description of the embodiments of the present invention will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of an application environment of a page event processing method according to an embodiment of the present invention;
FIG. 2 is a flow chart of a method for processing a page event according to an embodiment of the invention;
FIG. 3 is a flowchart of updating the historical operation times of a target control according to the event request time point of the target control in a page event processing method according to an embodiment of the present invention;
FIG. 4 is a flowchart of step S5 in a page event processing method according to an embodiment of the present invention;
FIG. 5 is a flow chart of a method for processing a page event to retire an invalid event request according to one embodiment of the present invention;
FIG. 6 is a flowchart of a method for processing a page event according to an embodiment of the present invention, wherein frequent requests of a target control are monitored according to a masking number;
FIG. 7 is a schematic diagram of a page event processing apparatus according to an embodiment of the invention;
FIG. 8 is a schematic diagram of a computer device in accordance with an embodiment of the invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The page event processing method provided by the application can be applied to an application environment shown in fig. 1, wherein the application environment comprises a server and a client, the server and the client are connected through a network, the network can be a wired network or a wireless network, the client specifically comprises but is not limited to various personal computers, notebook computers, smart phones, tablet computers and portable wearable devices, and the server can be specifically realized by a server cluster formed by independent servers or a plurality of servers. The client generates a page request, analyzes the page event request to determine whether the page event request is a frequent request, and executes corresponding processing according to the analysis result.
In an embodiment, as shown in fig. 2, a method for processing a page event is provided, and the method is applied to the client in fig. 1 as an example, and is described in detail as follows:
s1: if the clicking operation of the user on the target control in the page is detected, generating an event request of the target control, wherein the event request comprises the identity information of the user and the identification information of the target control.
Specifically, when the client detects the click operation of a user on a target control in a page, the identity information of the user and the identification information of the target control are obtained, and the identity information and the identification information are packaged into an event request aiming at the target control.
The target control is a control that the application software performs information interaction with the user, and may specifically be a button, such as a submit button, a select button, etc., or may be a menu, etc., which is not limited herein.
The identity information of the user is used for uniquely identifying the user, which may be a user name or the like where the user is successfully registered in the application software, and the identification information of the target control is used for uniquely identifying the target control in the application software.
The event request is used for requesting response processing of clicking operation of the target control from the server.
S2: according to the identity information of the user, the identification information of the controls which are allowed to be operated by the user and the historical operation times of each control in a preset operation time period are obtained in a preset user permission data table.
Specifically, the preset user permission database stores operation permission and operation data of legal users on the controls in the application software, namely control operation permission information, wherein the control operation permission information specifically can include identification information of the controls which are allowed to be operated by the users and historical operation times of each control in a preset operation time period.
The operation authority can be applied in advance by the user, validated after being confirmed by the server, and stored in the user authority database, and if the user does not apply in advance, the default preset basic authority is used as the operation authority of the user.
It should be noted that the preset operation time period may be set according to the needs of practical applications, and is not limited herein, and for example, the operation time period may be set to 1 minute.
S3: and if the identification information of the control which allows the user to operate has the same identification information as the identification information of the target control, marking the event request as a valid event request.
Specifically, according to the control operation authority information obtained in the step S2, whether the identification information of the target control in the step S1 belongs to the identification information of the control which allows the user to operate in the control operation authority information is judged, namely, whether the user has authority to operate the target control is judged, if so, it is confirmed that the identification information which is the same as the identification information of the target control exists in the identification information of the control which allows the user to operate, namely, it is confirmed that the user has authority to operate the target control, and the event request generated in the step S1 is marked as an effective event request by the client.
If the identification information of the target control does not belong to the identification information of the control which allows the user to operate in the control operation authority information, the user is confirmed to have no authority to operate the target control, and the client discards the event request generated in the step S1 and does not send the event request to the server for response processing.
S4: and acquiring the control operation type of the target control from a preset control attribute table.
Specifically, if the client determines that the user has permission to operate the target control according to step S3, the control operation type of the target control is obtained from a preset control attribute table.
The control operation type of each control is stored in a preset control attribute table in advance, and the control operation type is used for identifying the operation attribute of the control.
Further, the control operation types may include repeatable types and non-repeatable types, in particular. The repeatable type refers to that the control piece can be repeatedly clicked within a preset time period, and the non-repeatable type refers to that the control piece cannot be repeatedly clicked within the preset time period.
S5: and determining the request attribute of the effective event request according to the control operation type of the target control and the historical operation times corresponding to the target control.
Specifically, according to the operation attribute of the target control obtained in the step S4 and the historical operation times of the target control in the preset operation time period obtained in the step S2, whether the effective event request for the target control belongs to a frequent request is judged.
Wherein, frequent request is used for identifying that the target control has been clicked many times, and the current clicking operation can not be processed continuously, and normal request is used for identifying that the current clicking operation of the target control can be processed normally.
If the control operation type of the target control is a repeatable type, whether the user performs multiple clicking operations on the target control within a preset operation time period is further determined according to the historical operation times corresponding to the target control, if the user performs multiple clicking operations on the target control within the preset operation time period, the request attribute of the effective event request is confirmed to be a frequent request, and if the user does not perform clicking operations on the target control within the preset operation time period or performs a small number of clicking operations on the target control within the preset operation time period, the request attribute of the effective event request is confirmed to be a normal request.
If the control operation type of the target control is a non-repeatable type, further determining whether the user has performed clicking operation on the target control within a preset operation time period according to the historical operation times corresponding to the target control, if the user has performed clicking operation on the target control within the preset operation time period, confirming that the request attribute of the effective event request is a frequent request, and if the user has not performed clicking operation on the target control within the preset operation time period, confirming that the request attribute of the effective event request is a normal request.
S6: and if the request attribute of the effective event request is a frequent request, carrying out shielding processing on the effective event request.
Specifically, according to the request attribute determined in step S5, if the request attribute is a frequent request, the client performs a masking process on the valid event request, where the masking process may specifically be a discarding process.
S7: and if the request attribute of the effective event request is a normal request, sending the effective event request to a preset execution port for processing.
Specifically, according to the request attribute determined in step S5, if the request attribute is a normal request, the client sends the valid event request to a preset execution port for processing, and the preset execution port sends the valid event request to the server, so that the server responds to the valid event request.
In this embodiment, after detecting a click operation of a user on a target control in a page and generating an event request of the target control, a client determines, according to identity information of the user included in the event request, identification information of a control that allows the user to operate and historical operation times of each control in a preset operation time period, and if identification information identical to the identification information of the target control is included in the identification information of the control that allows the user to operate, marks the event request as an effective event request; and then, acquiring a control operation type of the target control from a preset control attribute table, determining a request attribute of an effective event request according to the control operation type and the historical operation times corresponding to the target control, shielding the effective event request if the request attribute of the effective event request is a frequent request, and transmitting the effective event request to a preset execution port for processing if the request attribute of the effective event request is a normal request. Whether the target control belongs to a repeatable type and the combination of historical operation times are judged, whether an effective event request is a frequent request is determined, and then the frequent request is shielded, so that the client can timely identify the misoperation or malicious continuous attack and other attack behaviors of a user on the target control, and a large number of repeated event requests are prevented from being sent to a background server, thereby reducing the system load and improving the processing efficiency; meanwhile, whether the user has permission to operate the target control or not is determined according to the control operation permission of the user, so that the safety of processing the page event can be improved.
In an embodiment, as shown in fig. 3, after step S3 and before step S4, the historical operation times of the target control may be updated according to the event request time point of the target control, which specifically includes the following steps:
s91: recording the event request time point of the target control.
Specifically, the event request time point may be a generation time point of an event request of the target control, and the client saves the generation time point in a record corresponding to the identification information of the user and the identification information of the target control in a preset data table.
It should be noted that, for each event request of the target control, a generation time point of the event request, that is, an event request time point, is recorded in a preset data table correspondingly.
S92: and if the time interval between the event request time point of the target control and the previous event request time point of the target control is smaller than a preset first interval threshold value, accumulating and updating the historical operation times corresponding to the target control.
Specifically, according to each event request time point recorded in a preset data table, calculating a time interval between the last two event request time points, and if the time interval is smaller than a preset first interval threshold value, adding one to the historical operation times corresponding to the target control to obtain the accumulated and updated historical operation times.
It is understood that the preset first interval threshold is less than the preset operating time period.
S93: and if the time interval between the event request time point of the target control and the previous event request time point of the target control is larger than a preset second interval threshold value, resetting the historical operation times corresponding to the target control and re-counting.
Specifically, if the time interval between the last two event request time points is greater than a preset second interval threshold, the historical operation times corresponding to the target control of the client are zeroed, and the recounting is 1 time.
It is understood that the predetermined second interval threshold is greater than the predetermined operating time period.
In this embodiment, by recording the event request time point of the target control, calculating the time interval between the event request time point of the target control and the previous event request time point of the target control, and determining to accumulate or zero the historical operation times corresponding to the target control according to the time interval, thereby ensuring that the historical operation times corresponding to the target control are effective in real time, and providing an accurate data basis for judging whether the effective event request belongs to the frequent request.
In one embodiment, the control operation types include repeatable types and nonrepeatable types. Wherein, the repeatable type refers to that the control piece can be repeatedly clicked within a preset time period, and the unrepeatable type refers to that the control piece cannot be repeatedly clicked within the preset time period.
Further, as shown in fig. 4, in step S5, a request attribute of the valid event request is determined according to a control operation type of the target control and a history operation number corresponding to the target control, and specifically includes the following steps:
s51: and if the control operation type of the target control is a repeatable type and the historical operation times corresponding to the target control are greater than or equal to a preset time threshold, confirming that the request attribute of the effective event request is a frequent request.
Specifically, when the control operation type of the target control is a repeatable type, the target control is confirmed to be allowed to be clicked for multiple times in a preset operation time period, if the historical operation times corresponding to the target control is greater than or equal to a preset time threshold, the fact that the clicking times of the target control in the preset operation time period exceeds the maximum allowed times is indicated, and therefore the request attribute of the effective event request is confirmed to be a frequent request.
It should be noted that the preset frequency threshold may be set according to the needs of practical applications, which is not limited herein. For example, the number of times threshold may be set to 5 times.
S52: and if the control operation type of the target control is a non-repeatable type and the historical operation times corresponding to the target control are greater than zero, confirming that the request attribute of the effective event request is a frequent request.
Specifically, when the control operation type of the target control is a non-repeatable type, the target control is confirmed to be only allowed to be clicked once within a preset operation time period, if the historical operation times corresponding to the target control are greater than zero, the target control is indicated to have performed clicking operation within the preset operation time period, and therefore the request attribute of the valid event request is confirmed to be a frequent request.
S53: if the control operation type of the target control is repeatable and the historical operation times corresponding to the target control are smaller than a preset time threshold, confirming that the request attribute of the effective event request is a normal request.
Specifically, when the control operation type of the target control is a repeatable type, if the historical operation frequency corresponding to the target control is smaller than a preset frequency threshold, it is indicated that the click frequency of the target control in a preset operation time period does not exceed the maximum allowable frequency, so that the request attribute of the effective event request is confirmed to be a normal request.
S54: and if the control operation type of the target control is a non-repeatable type and the historical operation times corresponding to the target control are equal to zero, confirming that the request attribute of the effective event request is a normal request.
Specifically, when the control operation type of the target control is a non-repeatable type, if the historical operation times corresponding to the target control is equal to zero, the target control is indicated that clicking operation is not performed in a preset operation time period, so that the request attribute of the effective event request is confirmed to be a normal request.
In this embodiment, whether the target control is of a repeatable type and the combination of historical operation times is determined, so that the client can timely identify the misoperation or malicious continuous attack and other attack behaviors of the user on the target control, and avoid sending a large number of repeated event requests to the background server, thereby reducing the system load and improving the processing efficiency.
In one embodiment, as shown in fig. 5, after step S2, the invalidation event request may be further processed for revocation, which specifically includes the following steps:
s21: and if the identification information of the control which allows the user to operate does not have the same identification information as the identification information of the target control, marking the event request as an invalid event request.
Specifically, according to the control operation authority information obtained in the step S2, whether the identification information of the target control in the step S1 belongs to the identification information of the control which allows the user to operate in the control operation authority information is judged, namely, whether the user has authority to operate the target control is judged, if not, it is confirmed that the identification information which is the same as the identification information of the target control does not exist in the identification information of the control which allows the user to operate, namely, it is confirmed that the user does not have authority to operate the target control, and the event request generated in the step S1 is marked as an invalid event request by the client.
S22: and carrying out withdrawal processing on the invalid event request.
Specifically, the revocation process is performed on the invalidation event request determined in step S21. The withdrawal process may specifically be a discard process for the invalid event request, and reclaim the relevant resource corresponding to the invalid event request.
S23: and outputting prompt information of invalid event request in a preset display window according to a preset display mode.
Specifically, the client outputs prompt information in a preset display window, wherein the prompt information is used for prompting a user to invalidate the click operation of the target control.
The preset display mode can be a text display mode or a multimedia display mode, the preset display window can be a popup window or a preset display area of a client display interface, and the display mode and the display window can be set according to the actual application requirement without limitation.
In this embodiment, when the identification information of the control that allows the user to operate is not the same as the identification information of the target control, the client confirms that the user has no authority to operate the target control, marks the event request as an invalid event request, withdraws the invalid event request, and returns prompt information that the event request is invalid to the user. When the user does not have the operation right to the target control, the processing of the event request can be timely terminated, so that the safety of processing the page event is improved.
In an embodiment, as shown in fig. 6, after step S6, frequent requests of the target control may be monitored according to the number of shielding times, which specifically includes the following steps:
s81: the masked point in time of the valid event request is recorded.
Specifically, after the valid event request is subjected to the masking process, the masking time point of the valid event request is recorded.
For example, if the client performs the masking process on the valid event request at 13:30 min 25 s in 10:30:10:13:30:25 s, the client uses the time information of "2018:10:13:30 min 25 s" as the masking time point of the valid event request, and correspondingly recording the shielding time point, the identification information of the user and the identification information of the target control into a preset data table.
S82: counting the number of masking time points belonging to a preset masking time period, and taking the number as the masking times.
Specifically, according to the shielding time points of the effective event requests corresponding to the target controls recorded in the preset data table, according to the time information in the shielding time points, the number of shielding time points, namely the shielding times, in the preset shielding time period is counted.
For example, if the preset masking time period is one minute before the current time point, the current time point is "2018, 10, 30, 14, 00 minutes, 00 seconds", and the masking time point of the valid event request corresponding to the target control recorded in the data table includes: the number of shielding times counted is 3 times for "2018 10 month 30 day 13 point 30 minutes 25 seconds", "2018 10 month 30 day 13 point 59 minutes 05 seconds", "2018 10 month 30 day 13 point 59 minutes 09 seconds", and "2018 10 month 30 day 13 point 59 minutes 15 seconds".
S83: if the shielding times are larger than a preset shielding times threshold, the shielding time points and the shielding times which belong to a preset shielding time period are packaged into frequent request data, and the frequent request data and the effective event request are sent to a monitoring platform.
Specifically, if the number of masking times counted in step S82 is greater than the preset masking times threshold, the masking time points and the masking times within the preset masking time period are encapsulated into frequent request data.
The preset shielding times threshold is used for judging whether the current shielding times meet the requirements of monitoring and early warning. When the shielding times are larger than a preset shielding times threshold, the client confirms that the frequent request of the target control is necessary to be monitored and early-warned.
Continuing with the example in step S82, if the preset masking number threshold is 2, the masking number is greater than the masking number threshold, and the frequent request data generated by the client includes masking time points "2018, 10, 30, 13, 59 minutes and 05 seconds", "2018, 10, 30, 13, 59 minutes and 09 seconds", and "2018, 10, 30, 13, 59 minutes and 15 seconds", and masking number 2 times.
The client sends the frequent request data and the effective event request to the monitoring platform, and a management user of the monitoring platform can analyze the target control and the frequent operation thereof according to the frequent request data and the effective event request received by the monitoring platform, check whether the problems such as system abnormality or malicious attack exist or not, and take corresponding maintenance measures for the found problems.
In this embodiment, after the effective event request is masked, the masking time point of the effective event request is recorded, and the masking times of the masking time points in the preset masking time period are counted, and when the masking times are greater than the preset masking times threshold, frequent request data including the masking time point and the masking times in the masking time period and the effective event request are sent to the monitoring platform for monitoring and early warning analysis, so that possible system abnormality or malicious attack can be checked in time, corresponding maintenance measures can be taken in time, and maintainability is improved.
It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not limit the implementation process of the embodiment of the present invention.
In an embodiment, a page event processing device is provided, where the page event processing device corresponds to the page event processing method in the above embodiment one by one. As shown in fig. 7, the page event processing apparatus includes: an event request module 10, a rights acquisition module 20, a request validity module 30, a type acquisition module 40, an attribute determination module 50, an exception mask module 60, and a normal processing module 70. The functional modules are described in detail as follows:
The event request module 10 is configured to generate an event request of a target control if a click operation of a user on the target control in a page is detected, where the event request includes identity information of the user and identification information of the target control;
the permission acquisition module 20 is configured to acquire, according to identity information of a user, identification information of a control that allows the user to operate in a preset user permission data table, and historical operation times of each control in a preset operation time period;
the request valid module 30 is configured to mark the event request as a valid event request if the identification information of the control that allows the user to operate has the same identification information as the identification information of the target control;
the type obtaining module 40 is configured to obtain a control operation type of the target control from a preset control attribute table;
the attribute determining module 50 is configured to determine a request attribute of the valid event request according to a control operation type of the target control and a historical operation number corresponding to the target control;
the exception masking module 60 is configured to mask the valid event request if the request attribute of the valid event request is a frequent request;
the normal processing module 70 is configured to send the valid event request to the preset execution port for processing if the request attribute of the valid event request is a normal request.
Further, the page event processing apparatus further includes:
a request time recording module 91, configured to record an event request time point of the target control;
the accumulation updating module 92 is configured to perform accumulation updating on the historical operation times corresponding to the target control if the time interval between the event request time point of the target control and the previous event request time point of the target control is smaller than a preset first interval threshold;
and the zero clearing and counting module 93 is configured to zero and re-count the historical operation times corresponding to the target control if the time interval between the event request time point of the target control and the previous event request time point of the target control is greater than a preset second interval threshold.
Further, the control operation types include repeatable types and nonrepeatable types, and the attribute determination module 50 includes:
the first judging sub-module 501 is configured to confirm that the request attribute of the valid event request is a frequent request if the control operation type of the target control is a repeatable type and the number of times of historical operations corresponding to the target control is greater than or equal to a preset number of times threshold.
The second judging sub-module 502 is configured to confirm that the request attribute of the valid event request is a frequent request if the control operation type of the target control is a non-repeatable type and the historical operation number corresponding to the target control is greater than zero;
A third judging sub-module 503, configured to confirm that the request attribute of the valid event request is a normal request if the control operation type of the target control is a repeatable type and the number of times of historical operations corresponding to the target control is less than a preset number of times threshold;
and a fourth judging sub-module 504, configured to confirm that the request attribute of the valid event request is a normal request if the control operation type of the target control is a non-repeatable type and the historical operation number corresponding to the target control is equal to zero.
Further, the page event processing apparatus further includes:
a request invalidation module 21, configured to mark the event request as an invalid event request if the identification information of the control that allows the user to operate does not have the same identification information as the identification information of the target control;
a withdrawal module 22, configured to withdraw the invalid event request;
the prompt module 23 is configured to output prompt information that the event request is invalid in a preset display window according to a preset display mode.
Further, the page event processing apparatus further includes:
a mask time recording module 81, configured to record a mask time point of the valid event request;
a statistics module 82, configured to count the number of masking time points in a preset masking time period, and take the number as a masking number;
The early warning module 83 is configured to encapsulate the masking time points and the masking times belonging to the preset masking time period into frequent request data if the masking times are greater than the preset masking times threshold, and send the frequent request data and the valid event request to the monitoring platform.
For specific limitation of the page event processing apparatus, reference may be made to the limitation of the page event processing method hereinabove, and no further description is given here. The respective modules in the above page event processing apparatus may be implemented in whole or in part by software, hardware, and a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
In one embodiment, a computer device is provided, which may be a terminal, and the internal structure thereof may be as shown in fig. 8. The computer device includes a processor, a memory, a network interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface of the computer device is for communicating with an external server via a network connection. The computer program, when executed by a processor, implements a page event processing method.
In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes the computer program to implement steps of the page event processing method in the above embodiment, such as steps S1 to S7 shown in fig. 2. Alternatively, the processor may implement the functions of the modules/units of the page event processing apparatus in the above embodiments, such as the functions of the modules 10 to 70 shown in fig. 7, when executing the computer program. To avoid repetition, no further description is provided here.
In an embodiment, a computer readable storage medium is provided, on which a computer program is stored, where the computer program when executed by a processor implements the method for processing a page event in the above method embodiment, or where the computer program when executed by a processor implements the functions of each module/unit in the page event processing device in the above device embodiment. To avoid repetition, no further description is provided here.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the various embodiments provided herein may include non-volatile and/or volatile memory. The nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), memory bus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions.
The above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention, and are intended to be included in the scope of the present invention.
Claims (10)
1. A page event processing method, characterized in that the page event processing method comprises:
if the clicking operation of a user on a target control in a page is detected, generating an event request of the target control, wherein the event request comprises identity information of the user and identification information of the target control;
Acquiring identification information of controls allowing the user to operate and historical operation times of each control in a preset operation time period from a preset user permission data table according to the identity information of the user;
if the identification information of the control allowing the user to operate has the same identification information as the identification information of the target control, marking the event request as an effective event request;
discarding the event request if the identification information of the target control does not belong to the identification information of the control allowing the user to operate;
acquiring a control operation type of the target control from a preset control attribute table;
determining a request attribute of the effective event request according to the control operation type of the target control and the historical operation times corresponding to the target control;
if the request attribute of the effective event request is a frequent request, masking the effective event request, wherein the frequent request is used for identifying that the target control is frequently clicked for many times, and the current clicking operation cannot be continuously processed;
and if the request attribute of the effective event request is a normal request, sending the effective event request to a preset execution port for processing, wherein the normal request is used for identifying that the current clicking operation of the target control can be processed normally.
2. The method for processing a page event according to claim 1, wherein if the identification information of the control allowing the user to operate has the same identification information as the identification information of the target control, the method for processing a page event further includes, after marking the event request as a valid event request and before acquiring the control operation type of the target control from a preset control attribute table:
recording an event request time point of the target control;
if the time interval between the event request time point of the target control and the previous event request time point of the target control is smaller than a preset first interval threshold value, accumulating and updating the historical operation times corresponding to the target control;
and if the time interval is larger than a preset second interval threshold, resetting the historical operation times corresponding to the target control and re-counting.
3. The method of claim 2, wherein the control operation types include a repeatable type and a non-repeatable type, and the determining the request attribute of the valid event request according to the control operation type of the target control and the historical operation times corresponding to the target control includes:
If the control operation type of the target control is the repeatable type and the historical operation times corresponding to the target control are greater than or equal to a preset time threshold, confirming that the request attribute of the effective event request is the frequent request;
if the control operation type of the target control is the unrepeatable type and the historical operation times corresponding to the target control are greater than zero, confirming that the request attribute of the effective event request is the frequent request;
if the control operation type of the target control is the repeatable type and the historical operation times corresponding to the target control are smaller than a preset time threshold, confirming that the request attribute of the effective event request is the normal request;
and if the control operation type of the target control is the unrepeatable type and the historical operation times corresponding to the target control are equal to zero, confirming that the request attribute of the effective event request is the normal request.
4. The method for processing a page event according to any one of claims 1 to 3, wherein the method for processing a page event further comprises, according to the identity information of the user, acquiring identification information of controls that allow the user to operate in a preset user authority data table, and after a historical operation number of each control in a preset operation time period, the method for processing a page event further comprises:
If the identification information of the control allowing the user to operate does not have the same identification information as the identification information of the target control, marking the event request as an invalid event request;
performing withdrawal processing on the invalid event request;
and outputting prompt information of invalid event request in a preset display window according to a preset display mode.
5. A method according to any one of claims 1 to 3, wherein if the request attribute of the valid event request is a frequent request, after masking the valid event request, the method further comprises:
recording a masking time point of the valid event request;
counting the number of the shielding time points in a preset shielding time period, and taking the number as shielding times;
and if the shielding times are greater than a preset shielding times threshold, packaging the shielding time points and the shielding times in the preset shielding time period into frequent request data, and sending the frequent request data and the effective event request to a monitoring platform.
6. A page event processing apparatus, characterized in that the page event processing apparatus comprises:
The event request module is used for generating an event request of a target control if the click operation of a user on the target control in a page is detected, wherein the event request comprises the identity information of the user and the identification information of the target control;
the permission acquisition module is used for acquiring identification information of controls which are allowed to be operated by the user from a preset user permission data table according to the identity information of the user, and historical operation times of each control in a preset operation time period;
the request valid module is used for marking the event request as a valid event request if the identification information of the control allowing the user to operate has the same identification information as the identification information of the target control;
the request invalidation module is used for marking the event request as an invalid event request if the identification information which is the same as the identification information of the target control is not contained in the identification information of the control which allows the user to operate;
the type acquisition module is used for acquiring the control operation type of the target control from a preset control attribute table;
the attribute determining module is used for determining the request attribute of the effective event request according to the control operation type of the target control and the historical operation times corresponding to the target control;
The abnormal shielding module is used for shielding the effective event request if the request attribute of the effective event request is a frequent request, wherein the frequent request is used for identifying that the target control is subjected to clicking operation for a plurality of times, and the current clicking operation cannot be continuously processed;
and the normal processing module is used for sending the effective event request to a preset execution port for processing if the request attribute of the effective event request is a normal request, wherein the normal request is used for identifying that the current clicking operation of the target control can be processed normally.
7. The page event processing device as recited in claim 6, wherein the page event processing device further comprises:
the request time recording module is used for recording event request time points of the target control;
the accumulation updating module is used for accumulating and updating the historical operation times corresponding to the target control if the time interval between the event request time point of the target control and the previous event request time point of the target control is smaller than a preset first interval threshold;
and the zero clearing counting module is used for resetting and re-counting the historical operation times corresponding to the target control if the time interval is larger than a preset second interval threshold value.
8. The page event processing device of claim 7, wherein the control operation types include a repeatable type and a non-repeatable type, the attribute determination module comprising:
the first judging sub-module is used for confirming that the request attribute of the effective event request is the frequent request if the control operation type of the target control is the repeatable type and the historical operation times corresponding to the target control is greater than or equal to a preset time threshold;
the second judging sub-module is used for confirming that the request attribute of the effective event request is the frequent request if the control operation type of the target control is the unrepeatable type and the historical operation times corresponding to the target control is greater than zero;
a third judging sub-module, configured to confirm that a request attribute of the valid event request is the normal request if a control operation type of the target control is the repeatable type and the historical operation number corresponding to the target control is less than a preset number threshold;
and the fourth judging sub-module is used for confirming that the request attribute of the effective event request is the normal request if the control operation type of the target control is the unrepeatable type and the historical operation times corresponding to the target control is equal to zero.
9. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the page event processing method of any of claims 1 to 5 when the computer program is executed.
10. A computer readable storage medium storing a computer program, wherein the computer program when executed by a processor implements the page event processing method according to any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811417812.0A CN109634756B (en) | 2018-11-26 | 2018-11-26 | Page event processing method, device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811417812.0A CN109634756B (en) | 2018-11-26 | 2018-11-26 | Page event processing method, device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109634756A CN109634756A (en) | 2019-04-16 |
| CN109634756B true CN109634756B (en) | 2024-03-08 |
Family
ID=66068964
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811417812.0A Active CN109634756B (en) | 2018-11-26 | 2018-11-26 | Page event processing method, device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109634756B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110221925A (en) * | 2019-05-13 | 2019-09-10 | 平安科技（深圳）有限公司 | Processing method, device and the computer equipment of data submission request |
| CN110442466A (en) * | 2019-06-14 | 2019-11-12 | 平安科技（深圳）有限公司 | Prevent request repeated accesses method, apparatus, computer equipment and storage medium |
| CN111224939B (en) * | 2019-11-15 | 2022-07-12 | 上海钧正网络科技有限公司 | Task request intercepting method and device, computer equipment and storage medium |
| CN113961110A (en) * | 2020-07-01 | 2022-01-21 | 腾讯科技（深圳）有限公司 | User operation response method and device, computer equipment and storage medium |
| CN112506696A (en) * | 2021-01-22 | 2021-03-16 | 马瑞利汽车电子(广州)有限公司 | Method for preventing request between modules from being lost |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101393629A (en) * | 2007-09-20 | 2009-03-25 | 阿里巴巴集团控股有限公司 | Implementing method and apparatus for network advertisement effect monitoring |
| CN105843599A (en) * | 2016-02-01 | 2016-08-10 | 乐视移动智能信息技术（北京）有限公司 | Method and apparatus for reducing user high-frequency operation influence, and user terminal |
| CN107219988A (en) * | 2017-05-26 | 2017-09-29 | 维沃移动通信有限公司 | A kind of interface operation bootstrap technique and mobile terminal |
| CN107391277A (en) * | 2017-07-17 | 2017-11-24 | 北京京东尚科信息技术有限公司 | Information processing method and device |
| CN107508892A (en) * | 2017-08-29 | 2017-12-22 | 努比亚技术有限公司 | A kind of page access method, server and computer-readable recording medium |
-
2018
- 2018-11-26 CN CN201811417812.0A patent/CN109634756B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101393629A (en) * | 2007-09-20 | 2009-03-25 | 阿里巴巴集团控股有限公司 | Implementing method and apparatus for network advertisement effect monitoring |
| CN105843599A (en) * | 2016-02-01 | 2016-08-10 | 乐视移动智能信息技术（北京）有限公司 | Method and apparatus for reducing user high-frequency operation influence, and user terminal |
| CN107219988A (en) * | 2017-05-26 | 2017-09-29 | 维沃移动通信有限公司 | A kind of interface operation bootstrap technique and mobile terminal |
| CN107391277A (en) * | 2017-07-17 | 2017-11-24 | 北京京东尚科信息技术有限公司 | Information processing method and device |
| CN107508892A (en) * | 2017-08-29 | 2017-12-22 | 努比亚技术有限公司 | A kind of page access method, server and computer-readable recording medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109634756A (en) | 2019-04-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109634756B (en) | Page event processing method, device, computer equipment and storage medium | |
| CN108304704B (en) | Authority control method and device, computer equipment and storage medium | |
| CN109446068B (en) | Interface test method, device, computer equipment and storage medium | |
| CN109871305B (en) | Alarm information processing method and device, computer equipment and storage medium | |
| AU2020264374A1 (en) | Systems and methods for real-time processing of data streams | |
| WO2021174694A1 (en) | Operation and maintenance monitoring method and apparatus based on data center, device, and storage medium | |
| CN113489713B (en) | Network attack detection method, device, equipment and storage medium | |
| CN110138669B (en) | Interface access processing method and device, computer equipment and storage medium | |
| CN110377569B (en) | Log monitoring method, device, computer equipment and storage medium | |
| CN108256322B (en) | Security testing method and device, computer equipment and storage medium | |
| CN108156141B (en) | Real-time data identification method and device and electronic equipment | |
| CN111835737B (en) | WEB attack protection method based on automatic learning and related equipment thereof | |
| CN111756644B (en) | Hot spot current limiting method, system, equipment and storage medium | |
| CN111193609B (en) | Application abnormity feedback method and device and application abnormity monitoring system | |
| CN109684863B (en) | Data leakage prevention method, device, equipment and storage medium | |
| CN112527410A (en) | Full link tracking method, device, equipment and storage medium | |
| CN112613067A (en) | User behavior data acquisition method and device, computer equipment and storage medium | |
| CN111158926B (en) | Service request analysis method, device and equipment | |
| CN111400435B (en) | Mail alarm convergence method, device, computer equipment and storage medium | |
| CN112685774A (en) | Payment data processing method based on big data and block chain finance and cloud server | |
| CN109542764B (en) | Webpage automatic testing method and device, computer equipment and storage medium | |
| CN112181794A (en) | Page monitoring method and device, computer equipment and storage medium | |
| CN111460256A (en) | Webpage data crawling method and device, computer equipment and storage medium | |
| CN115098326A (en) | System anomaly detection method and device, storage medium and electronic equipment | |
| CN111314496B (en) | Registration request intercepting method and device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |