CN109634756A - Page events processing method, device, computer equipment and storage medium - Google Patents
Page events processing method, device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN109634756A CN109634756A CN201811417812.0A CN201811417812A CN109634756A CN 109634756 A CN109634756 A CN 109634756A CN 201811417812 A CN201811417812 A CN 201811417812A CN 109634756 A CN109634756 A CN 109634756A
- Authority
- CN
- China
- Prior art keywords
- request
- target widget
- event request
- preset
- control
- 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.)
- Granted
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 31
- 238000012545 processing Methods 0.000 claims abstract description 55
- 230000009471 action Effects 0.000 claims abstract description 50
- 238000000034 method Methods 0.000 claims abstract description 11
- 238000004590 computer program Methods 0.000 claims description 17
- 230000001186 cumulative effect Effects 0.000 claims description 5
- 230000002159 abnormal effect Effects 0.000 claims description 4
- 230000006870 function Effects 0.000 description 7
- 238000012790 confirmation Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 4
- 230000006399 behavior Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000002123 temporal effect Effects 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 1
- 230000010485 coping Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 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 kind of page events processing method, device, computer equipment and storage mediums.The described method includes: generating the event request of target widget；Obtain the historical operation number for allowing the identification information and each control of the control of user's operation within preset period operating time；If allowing to have identification information identical with the identification information of target widget in the identification information of the control of user's operation, event request is requested labeled as validity event；Obtain the control action type of target widget；According to the corresponding historical operation number of the control action type and target widget of target widget, the request attribute of validity event request is determined；If the request attribute of validity event request is frequent requests, validity event is requested to carry out shielding processing.Technical solution of the present invention can be avoided to background server and send a large amount of duplicate event requests, reduces system loading and improves treatment effeciency；Meanwhile, it is capable to improve the safety to page events processing.
Description
Technical field
The present invention relates to field of computer technology more particularly to a kind of page events processing methods, device, computer equipment
And storage medium.
Background technique
In daily Internet application, web page browsing and web page operation are essential, and many Internet applications are all in the page
It is upper offer with user carry out information exchange page control, user can by click these page controls and Internet application into
Row interaction.
But in current Internet application, it is not directed to the effective monitoring of page control clicking operation, when using
When the attacks such as maloperation or malice double hit that family is repeatedly clicked, a large amount of identical event requests, these events can be generated
Request is almost sent to background server in the same time again and is handled, and leads to the increase of system loading, influences at system
Manage efficiency.
Summary of the invention
The embodiment of the present invention provides a kind of page events processing method, device, computer equipment and storage medium, to solve
Currently without the effective monitoring for being directed to page control clicking operation, so that page control generates a large amount of identical event requests, into
And system loading is caused to increase the problem of reducing with treatment effeciency.
A kind of page events processing method, comprising:
If detecting user to the clicking operation of the target widget in the page, the event for generating the target widget is asked
It asks, wherein the event request includes the identity information of the user and the identification information of the target widget；
According to the identity information of the user, obtaining in preset user right tables of data allows the user's operation
The historical operation number of the identification information of control and each control within preset period operating time；
If there is the identification information phase with the target widget in the identification information of the control for allowing the user's operation
Same identification information then requests the event request labeled as validity event；
The control action type of the target widget is obtained from preset control property table；
According to the corresponding historical operation number of the control action type of the target widget and the target widget, really
The request attribute of the fixed validity event request；
If the request attribute of the validity event request is frequent requests, validity event request is carried out at shielding
Reason；
If the request attribute of the validity event request is normal request, send validity event request to default
Port is executed to be handled.
A kind of page events processing unit, comprising:
Event request module, if for detecting user to the clicking operation of the target widget in the page, generate described in
The event request of target widget, wherein the event request includes the identity information of the user and the mark of the target widget
Know information；
Authority acquiring module obtains in preset user right tables of data for the identity information according to the user
Allow the history of the identification information and each control of the control of the user's operation within preset period operating time
Number of operations；
Effective module is requested, if having and the target in the identification information for the control for allowing the user's operation
The identical identification information of the identification information of control then requests the event request labeled as validity event；
Type acquisition module, for obtaining the control action type of the target widget from preset control property table；
Attribute determination module, for according to the control action type of the target widget and the corresponding institute of the target widget
Historical operation number is stated, determines the request attribute of the validity event request；
Abnormal shroud module, if the request attribute for validity event request is frequent requests, to described effective
Event request carries out shielding processing；
Normal processing module will be described effective if the request attribute for validity event request is normal request
Event request is sent to the default port that executes and is handled.
A kind of computer equipment, including memory, processor and storage are in the memory and can be in the processing
The computer program run on device, the processor realize above-mentioned page events processing method when executing the computer program
Step.
A kind of computer readable storage medium, the computer-readable recording medium storage have computer program, the meter
The step of calculation machine program realizes above-mentioned page events processing method when being executed by processor.
In above-mentioned page events processing method, device, computer equipment and storage medium, client is detecting user couple
The clicking operation of target widget in the page and after generating the event request of target widget, firstly, including according to event request
The identity information of user determines the identification information for allowing the control of user's operation and each control in the preset operating time
Historical operation number in period, if there is the identification information phase with target widget in the identification information of the control of permission user's operation
Same identification information then requests event request labeled as validity event；Then, target is obtained from preset control property table
The control action type of control, and according to the control action type and the corresponding historical operation number of target widget, it determines effective
The request attribute of event request shields validity event request if the request attribute of validity event request is frequent requests
Processing is covered, if the request attribute of validity event request is normal request, sends default execution port for validity event request
It is handled.Judged by the combination for whether belonging to repeatable type and historical operation number to target widget, is determined effective
Whether event request is frequent requests, and then carries out shielding processing to frequent requests, enables and identifies in time in client
The attacks such as maloperation or malice double hit that user repeatedly clicks target widget avoid sending to background server a large amount of
Duplicate event request, to reduce system loading and improve treatment effeciency；Meanwhile it being determined according to the control operating right of user
Whether user, which has permission, operates target widget, can be improved the safety to page events processing.
Detailed description of the invention
In order to illustrate the technical solution of the embodiments of the present invention more clearly, below by institute in the description to the embodiment of the present invention
Attached drawing to be used is needed to be briefly described, it should be apparent that, the accompanying drawings in the following description is only some implementations of the invention
Example, for those of ordinary skill in the art, without any creative labor, can also be according to these attached drawings
Obtain other attached drawings.
Fig. 1 is an application environment schematic diagram of page events processing method in one embodiment of the invention；
Fig. 2 is a flow chart of page events processing method in one embodiment of the invention；
Fig. 3 is the event request time point pair in one embodiment of the invention in page events processing method according to target widget
The flow chart that the historical operation number of target widget is updated；
Fig. 4 is a flow chart of step S5 in page events processing method in one embodiment of the invention；
Fig. 5 is to carry out recalling the one of processing to invalid event request in page events processing method in one embodiment of the invention
Flow chart；
Fig. 6 is asked according to shielding number to the frequent of target widget in page events processing method in one embodiment of the invention
Seek the flow chart being monitored；
Fig. 7 is a schematic diagram of page events processing unit in one embodiment of the invention；
Fig. 8 is a schematic diagram of computer equipment in one embodiment of the invention.
Specific embodiment
Following will be combined with the drawings in the embodiments of the present invention, and technical solution in the embodiment of the present invention carries out clear, complete
Site preparation description, it is clear that described embodiments are some of the embodiments of the present invention, instead of all the embodiments.Based on this hair
Embodiment in bright, every other implementation obtained by those of ordinary skill in the art without making creative efforts
Example, shall fall within the protection scope of the present invention.
Page events processing method provided by the present application, can be applicable in application environment as shown in Figure 1, the application environment
Including server-side and client, wherein be attached between server-side and client by network, which can be wired network
Network or wireless network, client are specifically including but not limited to various personal computers, laptop, smart phone and plate
Computer and portable wearable device, the server that server-side can specifically be formed with independent server or multiple servers
Cluster is realized.Client generates page request, is analyzed page events request to determine whether it is frequent requests, and root
Corresponding processing is executed according to analysis result.
In one embodiment, it as shown in Fig. 2, providing a kind of page events processing method, applies in Fig. 1 in this way
It is illustrated for client, details are as follows:
S1: if detecting user to the clicking operation of the target widget in the page, the event for generating the target widget is asked
It asks, wherein event request includes the identity information of user and the identification information of target widget.
Specifically, when client detects clicking operation of the user to the target widget in the page, the body of user is obtained
The identification information of part information and target widget, and the identity information and the identification information are encapsulated as the thing for the target widget
Part request.
Wherein, target widget is the control that application software and user carry out information exchange, specifically can be button, such as mentions
Button, select button etc. are handed over, can also be menu etc., herein with no restrictions.
The identity information of user is used for the unique identification user, can be the use that user succeeds in registration in application software
Name in an account book etc., the identification information of target widget is for the unique identification target widget in application software.
Event request is used to handle the response of the clicking operation of target widget to server-side request.
S2: according to the identity information of user, the control for allowing user's operation is obtained in preset user right tables of data
Historical operation number within preset period operating time of identification information and each control.
Specifically, legitimate user is previously stored in preset user rights database to the behaviour of the control in application software
Make permission and operation data, i.e. control operation permission information, which can specifically include permission user's operation
Control historical operation number within preset period operating time of identification information and each control.
Wherein, operating right can be come into force after server-side is identified through by the pre- first to file of user, and be stored in user's power
It limits in database, if user does not carry out pre- first to file, using the default basic permission of default as the operating right of user.
It should be noted that preset period operating time can be configured according to the needs of practical application, herein not
It is limited, for example, period operating time can be set to 1 minute.
S3: if thering is mark identical with the identification information of target widget to believe in the identification information of the control of permission user's operation
Breath then requests event request labeled as validity event.
Specifically, the control operation permission information obtained according to step S2, the mark of the target widget in judgment step S1
Whether information belongs in control operation permission information the identification information for allowing the control of user's operation, that is, judges whether user has the right
Limit operates target widget, if belonging to, confirmation exists in the identification information of control for allowing user's operation and target
The identical identification information of the identification information of control, i.e. confirmation user have permission and operate to target widget, and client is by step
The event request that S1 is generated is requested labeled as validity event.
If the identification information of target widget is not belonging in control operation permission information allow the mark of the control of user's operation
Information then confirms that user does not have permission to operate target widget, then client abandons the event request that step S1 is generated, no
Server-side can be sent by event request carry out response processing.
S4: the control action type of target widget is obtained from preset control property table.
Specifically, target widget is operated if client end determines that user has permission according to step S3, from default
Control property table in obtain target widget control action type.
Wherein, the control action type of each control, control action type are pre-saved in preset control property table
For identifying the operational attribute of control.
Further, control action type can specifically include repeatable type and not reproducible type.Repeatable type
Refer to that control can be repeated click within the preset time cycle, not reproducible type refers to control in the preset time cycle
It is interior to be repeated click.
S5: according to the corresponding historical operation number of the control action type and target widget of target widget, effective thing is determined
The request attribute of part request.
Specifically, the target control got according to the operational attribute of the obtained target widget of step S4 and step S2
Whether historical operation number of the part within preset period operating time, judgement belong to for the validity event request of the target widget
In frequent requests.
Wherein, frequent requests were repeatedly carried out clicking operation, and current click for identifying target widget
Operation cannot continue to be processed, and normal request can be normally processed for identifying the current clicking operation of target widget.
If the control action type of target widget is repeatable type, further grasped according to the corresponding history of target widget
Determine whether user has carried out multiple clicking operation to the target widget within preset period operating time as number, if
User has carried out multiple clicking operation to the target widget within preset period operating time, then confirms the validity event and ask
The request attribute asked is frequent requests, if user not yet carries out click behaviour to the target widget within preset period operating time
Make or user has carried out a small amount of clicking operation to the target widget within preset period operating time, then confirms the validity thing
The request attribute of part request is normal request.
If the control action type of target widget is not reproducible type, further according to the corresponding history of target widget
Number of operations determines whether user had carried out clicking operation to the target widget within preset period operating time, if with
Family had carried out clicking operation to the target widget within preset period operating time, then confirmed the validity asking for event request
Seeking attribute is frequent requests, if user not yet carries out clicking operation to the target widget within preset period operating time,
The request attribute for confirming the validity event request is normal request.
S6: if the request attribute of validity event request is frequent requests, validity event is requested to carry out shielding processing.
Specifically, the request attribute determined according to step S5, if the request attribute is frequent requests, client has this
It imitates event request and carries out shielding processing, the mode of shielding processing specifically can be discard processing.
S7: if the request attribute of validity event request is normal request, default execution is sent by validity event request
Port is handled.
Specifically, the request attribute determined according to step S5, if the request attribute is normal request, client has this
Effect event request is sent to the default port that executes and is handled, which sends service for validity event request
End, so that server-side responds validity event request.
In the present embodiment, client is detecting user to the clicking operation of the target widget in the page and is generating target control
After the event request of part, firstly, the identity information for the user for including according to event request, determines the control for allowing user's operation
The historical operation number of identification information and each control within preset period operating time, if allowing the control of user's operation
There is identification information identical with the identification information of target widget in the identification information of part, then event request is labeled as validity event
Request；Then, the control action type of target widget is obtained from preset control property table, and according to the control action type
Historical operation number corresponding with target widget determines the request attribute of validity event request, if the request of validity event request
Attribute is frequent requests, then requests validity event to carry out shielding processing, if the request attribute of validity event request is normally to ask
It asks, then sends the default port that executes for validity event request and handle.By whether belonging to repeatable class to target widget
The combination of type and historical operation number judges determine whether validity event request is frequent requests, so to frequent requests into
Row shielding processing enables and identifies that the maloperation that user repeatedly clicks target widget or malice connect in time in client
Equal attacks are hit, avoid sending a large amount of duplicate event requests to background server, to reduce at system loading and raising
Manage efficiency；Meanwhile determining whether user has permission according to the control operating right of user and target widget is operated, Neng Gouti
The safety that height handles page events.
It in one embodiment, can also be according to target control as shown in figure 3, after step s 3, and before step S 4
The event request time point of part is updated the historical operation number of target widget, specifically comprises the following steps:
S91: the event request time point of target widget is recorded.
Specifically, event request time point can be the generation time point of the event request of target widget, and client should
Generation time point is saved in preset tables of data in the identification information of user and the corresponding record of the identification information of target widget.
It should be noted that equal corresponding record has in preset tables of data to the event request each time of target widget
The generation time point of the event request, i.e. event request time point.
S92: if between the event request time point of target widget and a preceding event request time point for the target widget
Time interval be less than preset first interval threshold, then to the corresponding historical operation number of the target widget carry out it is cumulative more
Newly.
Specifically, according to the event request time point each time recorded in preset tables of data, event twice is calculated recently
Time interval between request time point, it is if the time interval is less than preset first interval threshold, target widget is corresponding
Historical operation number carry out plus one processing, obtain the updated historical operation number that adds up.
It should be understood that preset first interval threshold is less than preset period operating time.
S93: if between the event request time point of target widget and a preceding event request time point for the target widget
Time interval be greater than preset second interval threshold, then by the corresponding historical operation number of the target widget carry out zero lay equal stress on
New count.
Specifically, if the time interval between event request time point twice recently is greater than preset second interval threshold,
Then the corresponding historical operation number of client objectives control is zeroed, and New count of laying equal stress on is 1 time.
It should be understood that preset second interval threshold is greater than preset period operating time.
In the present embodiment, by recording the event request time point of target widget, when calculating the event request of target widget
Between put and a preceding event request time point for the target widget between time interval, and according to the time interval determine to mesh
The corresponding historical operation number of mark control is added up or is zeroed, so that it is guaranteed that the corresponding historical operation number of target widget is real-time
Effectively, accurate data basis is provided to judge whether validity event request belongs to frequent requests.
In one embodiment, control action type includes repeatable type and not reproducible type.Wherein, type is repeated
Refer to that control can be repeated click within the preset time cycle, not reproducible type refers to control in the preset time cycle
It is interior to be repeated click.
Further, as shown in figure 4, in step s 5, according to the control action type and target widget pair of target widget
The historical operation number answered determines the request attribute of validity event request, specifically comprises the following steps:
S51: if the control action type of target widget is repeatable type, and the corresponding historical operation of target widget is secondary
Number is greater than or equal to preset frequency threshold value, then the request attribute for confirming the validity event request is frequent requests.
Specifically, when the control action type of target widget is repeatable type, then confirm the target widget default
Period operating time in allow repeatedly to be clicked, if the corresponding historical operation number of target widget be greater than or equal to it is preset time
Number threshold value then illustrates that number of clicks of the target widget within preset period operating time has been over maximum allowable time
Number, it is thus identified that the request attribute of validity event request is frequent requests.
It should be noted that preset frequency threshold value can be configured according to the needs of practical application, do not limit herein
System.For example, frequency threshold value can be set to 5 times.
S52: if the control action type of target widget is not reproducible type, and the corresponding historical operation of target widget
Number is greater than zero, then the request attribute for confirming the validity event request is frequent requests.
Specifically, when the control action type of target widget is not reproducible type, then confirm the target widget pre-
If period operating time in only allow to be clicked primary, if the corresponding historical operation number of target widget is greater than zero, illustrate
The target widget had carried out clicking operation within preset period operating time, it is thus identified that validity event request is asked
Seeking attribute is frequent requests.
S53: if the control action type of target widget is repeatable type, and the corresponding historical operation of target widget is secondary
Number is less than preset frequency threshold value, then the request attribute for confirming the validity event request is normal request.
Specifically, when the control action type of target widget is repeatable type, if the corresponding history behaviour of target widget
Make number less than preset frequency threshold value, then illustrates number of clicks of the target widget within preset period operating time not yet
More than maximum allowable number, it is thus identified that the request attribute of validity event request is normal request.
S54: if the control action type of target widget is not reproducible type, and the corresponding historical operation of target widget
Number is equal to zero, then the request attribute for confirming the validity event request is normal request.
Specifically, when the control action type of target widget is not reproducible type, if the corresponding history of target widget
Number of operations is equal to zero, then illustrates that the target widget not yet carried out clicking operation within preset period operating time, therefore,
The request attribute for confirming the validity event request is normal request.
In the present embodiment, sentenced by the combination for whether belonging to repeatable type and historical operation number to target widget
It is disconnected, determine whether validity event request is frequent requests, enables and identifies that user is more to target widget in time in client
The attacks such as the maloperation or malice double hit of secondary click avoid sending a large amount of duplicate event requests to background server,
To reduce system loading and improve treatment effeciency.
In one embodiment, as shown in figure 5, upon step s 2, can also request to carry out recalling processing to invalid event,
Specifically comprise the following steps:
S21: if allowing mark not identical with the identification information of target widget in the identification information of the control of user's operation
Know information, then requests event request labeled as invalid event.
Specifically, the control operation permission information obtained according to step S2, the mark of the target widget in judgment step S1
Whether information belongs in control operation permission information the identification information for allowing the control of user's operation, that is, judges whether user has the right
Limit target widget is operated, if being not belonging to, confirm allow user's operation control identification information in there is no with
The identical identification information of the identification information of target widget, i.e. confirmation user do not have permission to operate target widget, client
The event request that step S1 is generated is requested labeled as invalid event.
S22: invalid event request is carried out recalling processing.
Specifically, the invalid event request that step S21 is determined is carried out recalling processing.This is recalled processing and specifically can be pair
The discard processing of invalid event request, and recycle the invalid event and request corresponding related resource.
S23: invalid prompt information is requested in preset display window outgoing event according to preset display mode.
Specifically, client exports prompt information in preset display window, and the prompt information is for prompting user to mesh
The clicking operation for marking control is invalid.
Wherein, preset display mode specifically can be text display manner, can also be multimedia display mode, preset
Display window can be pop-up window, be also possible to the default display area of client display interface, display mode and display
Window can be configured according to the needs of practical application, herein with no restrictions.
In the present embodiment, when allow user's operation control identification information in not with the identification information phase of target widget
With identification information when, client confirmation user does not have permission to operate target widget, by event request labeled as invalid
Event request, and invalid event request is carried out to recall processing, while returning to the invalid prompt information of event request to user.
It realizes when user is not to the operating right of target widget, the processing to event request can be terminated in time, to improve
Safety to page events processing.
It in one embodiment, can also be according to shielding number to the frequency of target widget as shown in fig. 6, after step S6
Numerous request is monitored, and is specifically comprised the following steps:
S81: the shielding time point of record validity event request.
Specifically, after requesting to carry out shielding processing to validity event, the shielding time point of validity event request is recorded.
For example, if client has carried out at shielding validity event request 30 minutes and 25 seconds 13 points of on October 30th, 2018
Reason, the then when shielding that client requests " on October 30th, 2,018 25 seconds 30 minutes " this temporal information at 13 points as validity event
Between point, and by the identification information of the identification information and target widget of the shielding time point and user, corresponding record is to preset
In tables of data.
S82: statistics belongs to the quantity at the shielding time point in the preset shielding time cycle, and using the quantity as shielding
Number.
Specifically, according to the shielding time of the corresponding validity event request of the target widget recorded in preset tables of data
Point, according to the temporal information in shielding time point, statistics belongs to the quantity at the shielding time point in the preset shielding time cycle,
Shield number.
For example, current point in time is " 2018 if the preset shielding time cycle is one minute before current point in time
00 minute and 00 second 14 points of October 30 ", the shielding time point packet of the corresponding validity event request of target widget recorded in tables of data
It includes: " on October 30th, 2,018 13: 25 30: ", " on October 30th, 2,018 13: 05 59: ", " on October 30th, 2018
13 points 09 second 59 minutes " and " on October 30th, 2,018 13: 15 59: ", then the shielding number counted be 3 times.
S83: if shielding number is greater than preset shielding frequency threshold value, the screen in the preset shielding time cycle will be belonged to
It covers time point and shielding number is encapsulated as frequent requests data, and send prison for the frequent requests data and validity event request
Control platform.
Specifically, if the shielding number that step S82 is counted is greater than preset shielding frequency threshold value, will belong to default
The shielding time cycle in shielding time point and shielding number be encapsulated as frequent requests data.
Wherein, preset shielding frequency threshold value is for judging whether current shielding number reaches the requirement of monitoring and early warning.
When shielding number is greater than preset shielding frequency threshold value, then it is necessary to the frequent requests to target widget to supervise for client confirmation
Control early warning.
Continuation is illustrated with the example in step S82, if preset shielding frequency threshold value is 2 times, it is big to shield number
In shielding frequency threshold value, the frequent requests data that client generates include " 59 minutes 13 points of on October 30th, 2018 at shielding time point
05 second ", " on October 30th, 2,018 13: 09 59: " and " on October 30th, 2,018 13: 15 59: ", and shielding number
2 times.
The frequent requests data and validity event request are sent monitor supervision platform, the management user of monitor supervision platform by client
It can be requested according to the frequent requests data and validity event that monitor supervision platform receives, target widget and its frequent operation are carried out
The problems such as analyzing, checking for system exception or malicious attack, and corresponding maintenance measure is taken to the problem of discovery.
In the present embodiment, after requesting to carry out shielding processing to validity event, by the screen for recording validity event request
It covers time point, and counts the shielding number at the shielding time point belonged in the preset shielding time cycle, when the shielding number is big
When preset shielding frequency threshold value, by the frequent requests number comprising shielding time point and shielding number in the shielding time cycle
According to and validity event request be sent to monitor supervision platform and be monitored early warning analysis, it is that may be present so as to check in time
System exception or malicious attack, and corresponding maintenance measure is taken in time, it improves maintainable.
It should be understood that the size of the serial number of each step is not meant that the order of the execution order in above-described embodiment, each process
Execution sequence should be determined by its function and internal logic, the implementation process without coping with the embodiment of the present invention constitutes any limit
It is fixed.
In one embodiment, a kind of page events processing unit is provided, the page events processing unit and above-described embodiment
Middle page events processing method corresponds.As shown in fig. 7, the page events processing unit includes: event request module 10, power
Limit obtains module 20, the effective module 30 of request, type acquisition module 40, attribute determination module 50, abnormal shroud module 60 and just
Normal processing module 70.Detailed description are as follows for each functional module:
Event request module 10, if generating should for detecting user to the clicking operation of the target widget in the page
The event request of target widget, wherein event request includes the identity information of user and the identification information of target widget；
Authority acquiring module 20 obtains in preset user right tables of data and permits for the identity information according to user
Perhaps the historical operation number of the identification information of the control of user's operation and each control within preset period operating time；
Effective module 30 is requested, if there is the mark with target widget in the identification information of the control for allowing user's operation
The identical identification information of information then requests event request labeled as validity event；
Type acquisition module 40, for obtaining the control action type of target widget from preset control property table；
Attribute determination module 50, for the corresponding historical operation of control action type and target widget according to target widget
Number determines the request attribute of validity event request；
Abnormal shroud module 60 asks validity event if the request attribute for validity event request is frequent requests
Seek carry out shielding processing；
Normal processing module 70 asks validity event if the request attribute for validity event request is normal request
It asks and is sent to the default port that executes and is handled.
Further, the page events processing unit further include:
Request time logging modle 91, for recording the event request time point of target widget；
Cumulative update module 92, if for the event request time point of target widget and a preceding event for the target widget
Time interval between request time point is less than preset first interval threshold, then to the target widget corresponding historical operation time
Number carries out cumulative update；
Counting module 93 is reset, if for the event request time point of target widget and a preceding event for the target widget
Time interval between request time point is greater than preset second interval threshold, then by the corresponding historical operation time of the target widget
Number carries out the New count of laying equal stress on that is zeroed.
Further, control action type includes repeatable type and not reproducible type, attribute determination module 50 include:
First judging submodule 501, if the control action type for target widget is repeatable type, and target control
The corresponding historical operation number of part is greater than or equal to preset frequency threshold value, then confirms the validity the request attribute of event request as frequency
Numerous request.
Second judgment submodule 502, if the control action type for target widget is not reproducible type, and target
The corresponding historical operation number of control is greater than zero, then the request attribute for confirming the validity event request is frequent requests；
Third judging submodule 503, if the control action type for target widget is repeatable type, and target control
The corresponding historical operation number of part is less than preset frequency threshold value, then the request attribute for confirming the validity event request is normally to ask
It asks；
4th judging submodule 504, if the control action type for target widget is not reproducible type, and target
The corresponding historical operation number of control is equal to zero, then the request attribute for confirming the validity event request is normal request.
Further, the page events processing unit further include:
Request invalid module 21, if in the identification information of the control for allowing user's operation not with the mark of target widget
Know the identical identification information of information, then requests event request labeled as invalid event；
Module 22 is recalled, for carrying out recalling processing to invalid event request；
Cue module 23, for requesting invalid mention in preset display window outgoing event according to preset display mode
Show information.
Further, the page events processing unit further include:
Time recording module 81 is shielded, for recording the shielding time point of validity event request；
Statistical module 82, for counting the quantity at the shielding time point belonged in the preset shielding time cycle, and should
Quantity is as shielding number；
Warning module 83, if being greater than preset shielding frequency threshold value for shielding number, when will belong to preset shielding
Between shielding time point in the period and shielding number be encapsulated as frequent requests data, and by the frequent requests data and validity event
Request is sent to monitor supervision platform.
Specific about page events processing unit limits the limit that may refer to above for page events processing method
Fixed, details are not described herein.Modules in above-mentioned page events processing unit can fully or partially through software, hardware and its
Combination is to realize.Above-mentioned each module can be embedded in the form of hardware or independently of in the processor in computer equipment, can also be with
It is stored in the memory in computer equipment in a software form, in order to which processor calls the above modules of execution corresponding
Operation.
In one embodiment, a kind of computer equipment is provided, which can be terminal, internal structure
Figure can be as shown in Figure 8.The computer equipment includes processor, the memory, network interface, display connected by system bus
Screen and input unit.Wherein, the processor of the computer equipment is for providing calculating and control ability.The computer equipment is deposited
Reservoir includes non-volatile memory medium, built-in storage.The non-volatile memory medium is stored with operating system and computer journey
Sequence.The built-in storage provides environment for the operation of operating system and computer program in non-volatile memory medium.The calculating
The network interface of machine equipment is used to communicate with external server by network connection.When the computer program is executed by processor with
Realize a kind of page events processing method.
In one embodiment, a kind of computer equipment is provided, including memory, processor and storage are on a memory simultaneously
The computer program that can be run on a processor, processor are realized in above-described embodiment at page events when executing computer program
The step of reason method, such as step S1 shown in Fig. 2 to step S7.Alternatively, being realized when processor execution computer program above-mentioned
The function of each module/unit of page events processing unit in embodiment, such as module 10 shown in Fig. 7 is to the function of module 70.
To avoid repeating, details are not described herein again.
In one embodiment, a kind of computer readable storage medium is provided, computer program, computer are stored thereon with
Page events processing method in above method embodiment is realized when program is executed by processor, alternatively, the computer program is located
Manage the function that each module/unit in page events processing unit in above-mentioned apparatus embodiment is realized when device executes.To avoid repeating,
Details are not described herein again.
Those of ordinary skill in the art will appreciate that realizing all or part of the process in above-described embodiment method, being can be with
Relevant hardware is instructed to complete by computer program, the computer program can be stored in a non-volatile computer
In read/write memory medium, the computer program is when being executed, it may include such as the process of the embodiment of above-mentioned each method.Wherein,
To any reference of memory, storage, database or other media used in each embodiment provided herein,
Including non-volatile and/or volatile memory.Nonvolatile memory may include read-only memory (ROM), programming ROM
(PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM) or flash memory.Volatile memory may include
Random access memory (RAM) or external cache.By way of illustration and not limitation, RAM is available in many forms,
Such as static state RAM (SRAM), dynamic ram (DRAM), synchronous dram (SDRAM), double data rate sdram (DDRSDRAM), enhancing
Type SDRAM (ESDRAM), synchronization link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM
(RDRAM), direct memory bus dynamic ram (DRDRAM) and memory bus dynamic ram (RDRAM) etc..
It is apparent to those skilled in the art that for convenience of description and succinctly, only with above-mentioned each function
Can unit, module division progress for example, in practical application, can according to need and by above-mentioned function distribution by different
Functional unit, module are completed, i.e., the internal structure of described device is divided into different functional unit or module, more than completing
The all or part of function of description.
Embodiment described above is merely illustrative of the technical solution of the present invention, rather than its limitations；Although referring to aforementioned reality
Applying example, invention is explained in detail, those skilled in the art should understand that: it still can be to aforementioned each
Technical solution documented by embodiment is modified or equivalent replacement of some of the technical features；And these are modified
Or replacement, the spirit and scope for technical solution of various embodiments of the present invention that it does not separate the essence of the corresponding technical solution should all
It is included within protection scope of the present invention.
Claims (10)
1. a kind of page events processing method, which is characterized in that the page events processing method includes:
If detecting, user to the clicking operation of the target widget in the page, generates the event request of the target widget,
In, the event request includes the identity information of the user and the identification information of the target widget；
According to the identity information of the user, the control for allowing the user's operation is obtained in preset user right tables of data
Historical operation number within preset period operating time of identification information and each control；
If having in the identification information of the control for allowing the user's operation identical with the identification information of the target widget
Identification information then requests the event request labeled as validity event；
The control action type of the target widget is obtained from preset control property table；
According to the corresponding historical operation number of the control action type of the target widget and the target widget, institute is determined
State the request attribute of validity event request；
If the request attribute of the validity event request is frequent requests, the validity event is requested to carry out shielding processing；
If the request attribute of the validity event request is normal request, default execution is sent by validity event request
Port is handled.
2. page events processing method as described in claim 1, which is characterized in that if described allow the user's operation
Control identification information in have identification information identical with the identification information of the target widget, then by the event request mark
It is denoted as after validity event request, and the control operation class that the target widget is obtained from preset control property table
Before type, the page events processing method further include:
Record the event request time point of the target widget；
If between the event request time point of the target widget and a preceding event request time point for the target widget
Time interval is less than preset first interval threshold, then the historical operation number corresponding to the target widget adds up
It updates；
If the time interval is greater than preset second interval threshold, by the corresponding historical operation time of the target widget
Number carries out the New count of laying equal stress on that is zeroed.
3. page events processing method as claimed in claim 2, which is characterized in that the control action type includes repeatable
Type and not reproducible type, it is described corresponding described according to the control action type of the target widget and the target widget
Historical operation number determines that the request attribute of the validity event request includes:
If the control action type of the target widget is the repeatable type, and the target widget is corresponding described goes through
History number of operations is greater than or equal to preset frequency threshold value, then confirms that the request attribute of the validity event request is described frequent
Request；
If the control action type of the target widget is the not reproducible type, and the target widget is corresponding described
Historical operation number is greater than zero, then confirms that the request attribute of the validity event request is the frequent requests；
If the control action type of the target widget is the repeatable type, and the target widget is corresponding described goes through
History number of operations is less than preset frequency threshold value, then confirms that the request attribute of the validity event request is the normal request；
If the control action type of the target widget is the not reproducible type, and the target widget is corresponding described
Historical operation number is equal to zero, then confirms that the request attribute of the validity event request is the normal request.
4. page events processing method as described in any one of claims 1 to 3, which is characterized in that described according to the user
Identity information, the identification information for allowing the control of the user's operation is obtained in preset user right tables of data, and
Each control after the historical operation number in preset period operating time, also wrap by the page events processing method
It includes:
If not identical as the identification information of the target widget in the identification information of the control for allowing the user's operation
Identification information, then by the event request labeled as invalid event request；
Invalid event request is carried out recalling processing；
Invalid prompt information is requested in preset display window outgoing event according to preset display mode.
5. page events processing method as described in any one of claims 1 to 3, which is characterized in that if effective thing
The request attribute of part request is frequent requests, then requests after carrying out shielding processing the validity event, the page events
Processing method further include:
Record the shielding time point of the validity event request；
Statistics belongs to the quantity at the shielding time point in the preset shielding time cycle, and using the quantity as shielding time
Number；
If the shielding number is greater than preset shielding frequency threshold value, the institute in the preset shielding time cycle will be belonged to
It states shielding time point and the shielding number is encapsulated as frequent requests data, and by the frequent requests data and effective thing
Part request is sent to monitor supervision platform.
6. a kind of page events processing unit, which is characterized in that the page events processing unit includes:
Event request module, if for detecting that user to the clicking operation of the target widget in the page, generates the target
The event request of control, wherein the event request includes the identity information of the user and the mark letter of the target widget
Breath；
Authority acquiring module, for the identity information according to the user, obtaining in preset user right tables of data allows
The historical operation of the identification information of the control of the user's operation and each control within preset period operating time
Number；
Effective module is requested, if having and the target widget in the identification information for the control for allowing the user's operation
The identical identification information of identification information, then by the event request labeled as validity event request；
Type acquisition module, for obtaining the control action type of the target widget from preset control property table；
Attribute determination module, for described being gone through according to the control action type of the target widget and the target widget are corresponding
History number of operations determines the request attribute of the validity event request；
Abnormal shroud module, if the request attribute for validity event request is frequent requests, to the validity event
Request carries out shielding processing；
Normal processing module, if the request attribute for validity event request is normal request, by the validity event
Request is sent to the default port that executes and is handled.
7. page events processing unit as claimed in claim 6, which is characterized in that the page events processing unit is also wrapped
It includes:
Request time logging modle, for recording the event request time point of the target widget；
Cumulative update module, if for the event request time point of the target widget and a preceding event for the target widget
Time interval between request time point is less than preset first interval threshold, then the history corresponding to the target widget
Number of operations carries out cumulative update；
Counting module is reset, if being greater than preset second interval threshold for the time interval, by the target widget pair
The historical operation number answered carries out the New count of laying equal stress on that is zeroed.
8. page events processing unit as claimed in claim 7, which is characterized in that the control action type includes repeatable
Type and not reproducible type, the attribute determination module include:
First judging submodule, if the control action type for the target widget is the repeatable type, and described
The corresponding historical operation number of target widget is greater than or equal to preset frequency threshold value, then confirms the validity event request
Request attribute be the frequent requests；
Second judgment submodule, if the control action type for the target widget is the not reproducible type, and institute
The corresponding historical operation number of target widget is stated greater than zero, then confirms that the request attribute of the validity event request is described
Frequent requests；
Third judging submodule, if the control action type for the target widget is the repeatable type, and described
The corresponding historical operation number of target widget is less than preset frequency threshold value, then confirms the request of the validity event request
Attribute is the normal request；
4th judging submodule, if the control action type for the target widget is the not reproducible type, and institute
The corresponding historical operation number of target widget is stated equal to zero, then confirms that the request attribute of the validity event request is described
Normal request.
9. a kind of computer equipment, including memory, processor and storage are in the memory and can be in the processor
The computer program of upper operation, which is characterized in that the processor realized when executing the computer program as claim 1 to
5 described in any item page events processing methods.
10. a kind of computer readable storage medium, the computer-readable recording medium storage has computer program, and feature exists
In realization such as page events processing side described in any one of claim 1 to 5 when the computer program is executed by processor
Method.
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 true CN109634756A (en) | 2019-04-16 |
| CN109634756B 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) |
Cited By (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 |
| CN111224939A (en) * | 2019-11-15 | 2020-06-02 | 上海钧正网络科技有限公司 | Task request intercepting 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 |
| CN113961110A (en) * | 2020-07-01 | 2022-01-21 | 腾讯科技（深圳）有限公司 | User operation response method and device, computer equipment and storage medium |
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 |
Cited By (7)
| 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 |
| WO2020248384A1 (en) * | 2019-06-14 | 2020-12-17 | 平安科技（深圳）有限公司 | Repeated request access prevention method and apparatus, computer device, and storage medium |
| CN110442466B (en) * | 2019-06-14 | 2024-05-07 | 平安科技（深圳）有限公司 | Method, device, computer equipment and storage medium for preventing repeated access request |
| CN111224939A (en) * | 2019-11-15 | 2020-06-02 | 上海钧正网络科技有限公司 | 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109634756B (en) | 2024-03-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109634756A (en) | Page events processing method, device, computer equipment and storage medium | |
| CN110287660A (en) | Access right control method, device, equipment and storage medium | |
| CN105283852A (en) | Obfuscating trace data | |
| CN110609937A (en) | Crawler identification method and device | |
| CN109327439B (en) | Risk identification method and device for service request data, storage medium and equipment | |
| CN105283849A (en) | Parallel tracing for performance and detail | |
| WO2008041915A2 (en) | Security system and method for detecting intrusion in a computerized system | |
| CN104935609A (en) | Network attack detection method and detection apparatus | |
| CN110213199A (en) | Method, device and system for monitoring database collision attack and computer storage medium | |
| CN108449237B (en) | Network performance monitoring method and device, computer equipment and storage medium | |
| CN104320446A (en) | Distributed multi-Agent website monitoring method and system | |
| CN110457612B (en) | Terminal page access method and system | |
| AU2014364348A1 (en) | Communications security | |
| CN111460404A (en) | Double-recording data processing method and device, computer equipment and storage medium | |
| CN109313676A (en) | IP address access based on security level and access history | |
| CN108280346A (en) | A kind of application protecting, monitoring method, apparatus and system | |
| CN110400080A (en) | Examination data monitoring method, device, computer equipment and storage medium | |
| CN104639387B (en) | A kind of user network behavior tracking method and apparatus | |
| CN106210050A (en) | It is a kind of that intelligence is counter shields network crawler system | |
| CN101242314B (en) | A method and device for pre-alarming exception | |
| CN109542764A (en) | Webpage automated testing method, device, computer equipment and storage medium | |
| CN110460620B (en) | Website defense method, device, equipment and storage medium | |
| CN112104671A (en) | Interface authorization monitoring method and device, computer equipment and storage medium | |
| CN112084152A (en) | Full life cycle management system of electronic measuring instrument | |
| CN110378120A (en) | Application programming interfaces attack detection method, device and readable storage medium storing program for executing |
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 |