CN106095607B - Defend the method and system of the websites asp.net collapse - Google Patents
Defend the method and system of the websites asp.net collapse Download PDFInfo
- Publication number
- CN106095607B CN106095607B CN201610409674.6A CN201610409674A CN106095607B CN 106095607 B CN106095607 B CN 106095607B CN 201610409674 A CN201610409674 A CN 201610409674A CN 106095607 B CN106095607 B CN 106095607B
- Authority
- CN
- China
- Prior art keywords
- request
- collapse
- doubtful
- website
- asp
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a kind of method and system of websites defence asp.net collapse, including：To it is each be sent to server-side request to generate unique mark；At the end of the event of request, the request marks are terminated according to unique mark；When website collapses, the last one is not labeled as the request terminated before obtaining website collapse time point, and is asked labeled as doubtful collapse；When website collapses again, obtains the last one between collapsing twice and be not labeled as the request terminated, and be compared with doubtful collapse request；Doubtful collapse request is unanimously confirmed to lead to the request of collapse if comparing；If being received again by the above-mentioned request for leading to collapse, the request is not executed.By the above-mentioned means, the case where present invention can improve website stability, and reduction can not be used since program causes the code of collapse that website is caused continuously to collapse.
Description
Technical field
The present invention relates to server technology fields, more particularly, to a kind of method that the websites defence asp.net collapse and are
System.
Background technology
At present using the website of asp.net exploitations, it is possible to can be not rigorous enough due to some programmings, cause website to collapse
It bursts, and can only be arranged at present after collapsing and restart automatically, but excessive collapse, which may result in website, frequently restarts, and can also make
Website can not almost use.
Chinese patent application (CN201210443887.2) disclose it is a kind of make browser collapse network address processing method,
Apparatus and system.But the patent is suitable for mobile terminal browser field, is that can only prevent client browser from collapsing, but can not be from
(i.e. server-side) defense rupture in former process.
Invention content
The technical problem to be solved by the present invention is to：The scheme of defence website collapse is provided, website can be defendd from former process
Collapse prevents load collapse process, to improve stability.
In order to solve the above-mentioned technical problem, the technical solution adopted by the present invention is：A kind of side of defence website collapse is provided
Method, including：
To it is each be sent to server-side request to generate unique mark；
At the end of the event of request, the request marks are terminated according to unique mark；
When website collapses, the last one is not labeled as the request terminated before obtaining website collapse time point, and is labeled as
Doubtful collapse request；
When website collapses again, obtain twice collapse between the last one be not labeled as terminate request, and with doubt
It is compared like collapse request；
Doubtful collapse request is unanimously confirmed to lead to the request of collapse if comparing；
If being received again by the above-mentioned request for leading to collapse, the request is not executed.
To solve the above problems, the present invention also provides a kind of systems of defence website collapse, including：
Send generation module, for it is each be sent to server-side request to generate unique mark；
Terminate confirmation module, at the end of the event of request, terminating the request marks according to unique mark；
Doubtful collapse module is not labeled as the request terminated for obtaining before the collapse time point of website the last one, and
It is asked labeled as doubtful collapse；
First comparing module, for doubtful collapse request to be compared；
Confirmation module is collapsed, if consistent for comparing, confirms doubtful collapse request to lead to the request of collapse；
Defense module is asked, if for being received again by the above-mentioned request for leading to collapse, does not execute the request.
The beneficial effects of the present invention are：It is different from the prior art, the present invention rents the latter time point before obtaining website collapse
It for the request of end, is asked as doubtful collapse, and compare, after confirming unanimously, as the request for leading to collapse, and as follow-up
Request reference, with judge whether execute subsequent request.By the above-mentioned means, the present invention can improve website stabilization
Property, reduce the case where causing the code of collapse to cause website continuously to collapse can not to use due to program.
Description of the drawings
Fig. 1 is the flow diagram of the method for the present invention embodiment one；
Fig. 2 is the structure diagram of present system embodiment two.
Specific implementation mode
To explain the technical content, the achieved purpose and the effect of the present invention in detail, below in conjunction with embodiment and coordinate attached
Figure is explained.
The design of most critical of the present invention is:The last one time point is the request terminated before obtaining website collapse, as doubtful
It asks, and compares like collapse, after confirming unanimously, as the request for leading to collapse, and as the reference of subsequent request, to carry out
Judge whether to execute subsequent request.
Fig. 1 is please referred to, the embodiment of the present invention one provides a kind of method that defence website collapses, including：
To it is each be sent to server-side request to generate unique mark；
At the end of the event of request, the request marks are terminated according to unique mark；
When website collapses, the last one is not labeled as the request terminated before obtaining website collapse time point, and is labeled as
Doubtful collapse request；
When website collapses again, obtain twice collapse between the last one be not labeled as terminate request, and with doubt
It is compared like collapse request；
Doubtful collapse request is unanimously confirmed to lead to the request of collapse if comparing；
If being received again by the above-mentioned request for leading to collapse, the request is not executed.
It is different from the prior art, the last one time point is the request terminated before the present invention obtains website collapse, as doubtful
Collapse request, and compare, after confirming unanimously, as the request for leading to collapse, and as the reference of subsequent request, to be sentenced
It is disconnected whether to execute subsequent request.By the above-mentioned means, the present invention can improve website stability, reduce since program causes to collapse
Code the case where causing website continuously to collapse can not to use.
Wherein, the event of request of the present invention terminates to include normal termination and abnormal ending.It should be noted that abnormal
Terminate the request for not causing website to collapse, the two is different concept, if website collapse would not go to abnormal ending
Code.
Specifically, when transmiting a request to server-side, by the beginning request event of asp.net, request content is remembered
Record, and unique mark is generated, to mark current request.
When website collapses, website is restarted automatically, and is not labeled as the request terminated described in inquiry, and is collapsed labeled as doubtful
It bursts and asks；
When website collapses again, another doubtful collapse request is obtained；
The doubtful collapse request of above-mentioned two is compared, is judged whether consistent；
If inconsistent, above-mentioned all doubtful collapse requests are recorded, and return to step " when website collapses again, obtains another
One doubtful collapse request ".
If " being received again by the above-mentioned request for leading to collapse, do not execute the request " is specially：
All subsequent requests are compared with the request for leading to collapse, are judged whether consistent；
If so, not executing the subsequent request；
Conversely, then executing the subsequent request；
If execute the subsequent request, website collapse is then asked the subsequent request as doubtful collapse, and is doubted with other
It is compared like collapse request.
Accordingly, as shown in Fig. 2, the system that the embodiment of the present invention two also provides a kind of collapse of websites defence asp.net
100, including：
Send generation module 110, for it is each be sent to server-side request to generate unique mark；
End confirmation module 120, at the end of the event of request, being tied the request marks according to unique mark
Beam；
Doubtful collapse module 130 is not labeled as the request terminated for obtaining before the collapse time point of website the last one,
And it is asked labeled as doubtful collapse；
First comparing module 140, for doubtful collapse request to be compared；
Confirmation module 150 is collapsed, if consistent for comparing, confirms doubtful collapse request to lead to the request of collapse；
Defense module 160 is asked, if for being received again by the above-mentioned request for leading to collapse, does not execute the request.
Wherein, the event of the request terminates to include normal termination and abnormal ending.
The transmission generation module is specifically used for：When transmiting a request to server-side, request thing is started by asp.net
Part records request content, and generates unique mark, to mark current request.
The doubtful collapse module is specifically used for：When website collapses, website is restarted automatically, and be not labeled described in inquiry
For the request of end, and labeled as doubtful collapse request.
The collapse confirmation module is additionally operable to：
Doubtful collapse request is compared, is judged whether consistent；
If inconsistent, all doubtful collapse requests are recorded, and return to step " when website collapses again, obtains another
Doubtful collapse request ".
For example, when each request is sent to server-side, by the beginning request event of asp.net, to request
Content is recorded, and generates unique mark label current request；
In request normal termination and abnormal ending event, corresponding request is found according to the unique mark generated, by it
Labeled as end；
When website collapses, website is restarted automatically, the last one unmarked end asks before query web collapse time point
It asks, and is asked labeled as doubtful collapse；
Equal websites occur second after collapsing, the unmarked knot of the last one before being collapsed to second after first time is collapsed
The request of beam is once compared with preceding, is that can lead to the request of collapse by this request marks if completely the same；If differing
It causes, then wouldn't deal with, the doubtful collapse request of record above-mentioned two；
It is collapsed if third time occurs in website, itself and both of the aforesaid are doubted in the doubtful collapse request of corresponding acquisition third
It is compared one by one like collapse request, it is consistent until comparing, it is no until confirming the request there are two identical request to lead to collapse
Then, continue to obtain subsequent doubtful collapse request, and compared one by one with all doubtful collapse requests recorded before；
After confirming the request for leading to collapse, all requests later all be marked as that the request ratio of collapse can be caused
Compared with if unanimously, this request wouldn't be executed, that is, being marked as causing the request of collapse otherwise, to be held to prevent from collapsing
The row request, and judge whether to collapse；If collapsing again, by this request as doubtful collapse request, and with before
Doubtful collapse request compare, return above-mentioned steps, until obtain it is next cause collapse request.
It is required for being compared with all requests for leading to collapse in subsequent all requests, step is same as above, herein no longer
It repeats.
Example the above is only the implementation of the present invention is not intended to limit the scope of the invention, every to utilize this hair
Equivalents made by bright specification and accompanying drawing content are applied directly or indirectly in relevant technical field, include similarly
In the scope of patent protection of the present invention.
Claims (8)
1. a kind of method of websites defence asp.net collapse, which is characterized in that including：
To it is each be sent to server-side request to generate unique mark；
At the end of the event of request, the request marks are terminated according to unique mark；
When website collapses, the last one is not labeled as the request terminated before obtaining website collapse time point, and labeled as doubtful
Collapse request；
When website collapses again, obtains the last one between collapsing twice and be not labeled as the request terminated, and collapsed with doubtful
Routed request is compared；
Doubtful collapse request is unanimously confirmed to lead to the request of collapse if comparing；
If being received again by the above-mentioned request for leading to collapse, the request is not executed；
Wherein, when website collapses, website is restarted automatically, and is not labeled as the request terminated described in inquiry, and labeled as doubtful
Collapse request；
When website collapses again, another doubtful collapse request is obtained；
The doubtful collapse request of above-mentioned two is compared, is judged whether consistent；
If inconsistent, above-mentioned all doubtful collapse requests are recorded, and return to step " when website collapses again, obtains another
Doubtful collapse request ".
2. the method for the websites defence asp.net collapse according to claim 1, which is characterized in that the event knot of the request
Beam includes normal termination and abnormal ending.
3. the method for the websites defence asp.net collapse according to claim 1, which is characterized in that transmit a request to server-side
When, by the beginning request event of asp.net, request content is recorded, and generate unique mark, is currently asked with label
It asks.
4. the method for the websites defence asp.net collapse according to claim 1, which is characterized in that " if being received again by above-mentioned lead
The request for causing collapse, then do not execute the request " be specially：
All subsequent requests are compared with the request for leading to collapse, are judged whether consistent；
If so, not executing the subsequent request；
Conversely, then executing the subsequent request；
If execute the subsequent request, website collapse is then asked the subsequent request as doubtful collapse, and doubtful is collapsed with other
Routed request is compared.
5. a kind of system of websites defence asp.net collapse, which is characterized in that including：
Send generation module, for it is each be sent to server-side request to generate unique mark；
Terminate confirmation module, at the end of the event of request, terminating the request marks according to unique mark；
Doubtful collapse module is not labeled as the request terminated for obtaining before the collapse time point of website the last one, and marks
It is asked for doubtful collapse；
First comparing module, for doubtful collapse request to be compared；
Confirmation module is collapsed, if consistent for comparing, confirms doubtful collapse request to lead to the request of collapse；
Defense module is asked, if for being received again by the above-mentioned request for leading to collapse, does not execute the request；
Wherein, collapse confirmation module is additionally operable to：
Doubtful collapse request is compared, is judged whether consistent；
If inconsistent, all doubtful collapse requests are recorded.
6. the system of the websites defence asp.net collapse according to claim 5, which is characterized in that the event knot of the request
Beam includes normal termination and abnormal ending.
7. the system of the websites defence asp.net collapse according to claim 5, which is characterized in that the transmission generation module
It is specifically used for：When transmiting a request to server-side, by the beginning request event of asp.net, request content is recorded, and raw
At unique mark, to mark current request.
8. the system of the websites defence asp.net collapse according to claim 5, which is characterized in that the doubtful collapse module
It is specifically used for：When website collapses, website is restarted automatically, and is not labeled as the request terminated described in inquiry, and labeled as doubtful
It is asked like collapse.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610409674.6A CN106095607B (en) | 2016-06-12 | 2016-06-12 | Defend the method and system of the websites asp.net collapse |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610409674.6A CN106095607B (en) | 2016-06-12 | 2016-06-12 | Defend the method and system of the websites asp.net collapse |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106095607A CN106095607A (en) | 2016-11-09 |
| CN106095607B true CN106095607B (en) | 2018-11-13 |
Family
ID=57227932
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610409674.6A Active CN106095607B (en) | 2016-06-12 | 2016-06-12 | Defend the method and system of the websites asp.net collapse |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106095607B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103810086A (en) * | 2012-11-08 | 2014-05-21 | 腾讯科技（深圳）有限公司 | Method, device and system for processing website causing browser breakdown |
| CN104537005A (en) * | 2014-12-15 | 2015-04-22 | 北京国双科技有限公司 | Data processing method and device for webpage crawling |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7870418B2 (en) * | 2008-02-27 | 2011-01-11 | Microsoft Corporation | Enhanced presence routing and roster fidelity by proactive crashed endpoint detection |
| US9262250B2 (en) * | 2011-12-12 | 2016-02-16 | Crashlytics, Inc. | System and method for data collection and analysis of information relating to mobile applications |
-
2016
- 2016-06-12 CN CN201610409674.6A patent/CN106095607B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103810086A (en) * | 2012-11-08 | 2014-05-21 | 腾讯科技（深圳）有限公司 | Method, device and system for processing website causing browser breakdown |
| CN104537005A (en) * | 2014-12-15 | 2015-04-22 | 北京国双科技有限公司 | Data processing method and device for webpage crawling |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106095607A (en) | 2016-11-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102166589B1 (en) | Method and apparatus for realizing communication between web page and native application, and electronic device | |
| US11184465B2 (en) | Network communication for establishing a QUIC connection | |
| CN108810896B (en) | Connection authentication method and device of wireless access point | |
| CN104539682A (en) | Debug method, device, mobile terminal, server and system for mobile webpage | |
| WO2017036059A1 (en) | Method, apparatus, terminal device and system for monitoring user access behaviors | |
| US20160112492A1 (en) | Method and apparatus for providing network resources at intermediary server | |
| CN102662737A (en) | Calling method and device of extension program | |
| CN104618388A (en) | Quick registration and login method and corresponding reset server and information server | |
| CN104932910A (en) | Method and system for application program interface extension | |
| US20160191633A1 (en) | Method and apparatus for implementing communication from web page to client | |
| CN103544039A (en) | Plug-in loading processing method and device | |
| CN106095607B (en) | Defend the method and system of the websites asp.net collapse | |
| CN114189559B (en) | Axios-based interface repeated request processing method and system | |
| US9762627B2 (en) | Method of searching for and registering network device using HTTP and network registration service apparatus | |
| EP2760178B1 (en) | Method, apparatus and system for obtaining object | |
| CN113691520A (en) | Method, device, storage medium and electronic device for acquiring streaming media information | |
| CN110888892B (en) | Block synchronization method, device and storage medium | |
| JP4420399B2 (en) | Download optimization in the presence of multicast data | |
| CN108170493B (en) | System module loading method, system and device | |
| CN109446462B (en) | Page-based data monitoring processing method, device, equipment and storage medium | |
| US20170286440A1 (en) | Method, business processing server and data processing server for storing and searching transaction history data | |
| CN104639666A (en) | Domain name access method and device | |
| CN106126361B (en) | Defend the method and system of the websites Spring MVC collapse | |
| CN108595274B (en) | Program synchronization control method, device, system, computer device and storage medium | |
| KR101404764B1 (en) | Single Sign On Method at Mobile Device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |