A Web site stops accessing the problem resolution process that causes a crash

Recently to the company's website has been revised, the test server in the local and testing for a long time there is no problem, so today deployed to the server online. At the same time, the. NET Framework version is upgraded from 2.0 to 4.0. After the deployment of the test, no problem, put it out. Once announced, we have clicked. In a moment, it was reported that the visit could not be made. A try, sure enough. Everyone hurried to the server to view, did not find anything unusual. It's going to be fine after a while. Just as everyone is inexplicable wonderful, and can not visit, we first determine whether the program pool is full, but soon found that the same server on the other sites also can not open, these sites are not the same program pool. Then you can access it on the server and open it. and use other IP computers to try it, you can also open.

It seems that only one of our IP access is not, so the suspicion is that the firewall is to prohibit our IP. Check the firewall, really, because there is a network attack. IP is forbidden for 5 minutes.

What kind of place is that? It can be opened at first, and will not open after a while. Should not be a hacker problem, because only one of our IP computers can not access, we certainly do not have a hacker intranet. At this time someone did not intend to refresh the page, found constantly refreshed, and soon appeared the same problem. It seems that the same IP access is too frequent problem.

At this time know only will affect our one IP, everyone also relieved, began to rest assured testing. Start refreshing different pages and find that there are problems in addition to the simple search page.

Everyone started to wonder if it was a. NET program problem, I suspect it was not a problem using the template engine, so I used the template engine to generate only a simple Web page, no problem. That must be the wrong program, some people suspect that there are too many connections to the database, but I would like to connect the database should not be identified as an attack. Again the problem of the page generated static page, unexpectedly will also appear problems.

Static page The only danger is the JS file. Sure enough, I have JS all deleted, the problem does not appear. Sure it's JS. But quoted a lot of JS, began to exclude, but feel most of the problem. And then began to check JS inside is not a dangerous code, or illegal characters, because JS is mostly looking for others, see a head is big. Everyone began to change a way of thinking, add something to JS, who knows just the beginning of the file is empty when there will be problems, so the problem of excluding JS file itself.

There's no room for anyone to get here. I think of the current JS inside there are two previously used JS file. If there is a problem with the JS file, then the original page will not be a problem, testing a bit, will not.

Then use the current page to refer to the original JS will there be problems? After testing, no! Simply put all the JS moved to the original JS folder, and crazy test a bit, unexpectedly also can not problem. It seems that this is the folder to put the JS file problem, because I gave him a JavaScript name! It seems that the name was misunderstood by the firewall. So changed the folder name, the problem finally solved. This is really quirks, I originally did not use this name, is deployed to the server to change to this name, is really a cheap hand, but did not think it is the folder name of the problem. Although there is no test, there is a problem if the JS file name contains JavaScript.

It was a trivial matter, but it was quite a hassle to solve. Solving the problem is simple, and finding the problem is the hardest. When a broken programmer is not easy, there will always be unexpected problems, and a small problem to solve it is a waste of a long day.

This article is from the "through The Jungle" blog, please be sure to keep this source http://luqyu.blog.51cto.com/1663183/1791743

A Web site stops accessing the problem resolution process that causes a crash