Detailed information about safety dogs

This article mainly introduces the solution to the HTTP error 500.21 when installing the website security dog ​​in win2008 R2. Friends who need it can refer to the WINDOWS 2008 R2 system + IIS7.5. Everything is normal before installing the website security dog. Install the website After SafeDog version 3.3, some PHP websites cannot be accessed. The following error is prompted: HTTP Error 500.21 - Internal Server Error handler "SafedogIISAuditor64" has an error module "IsapiModule" in its module list. Solution: Check whether IIS7.5 adds asp.net extensibility components. If not installed, please install it. Then check whether IIS7.5 is installed with IIS6.0 management compatibility. If not, please install it. After installing the above two items, I visited the relevant website again and everything was normal.

1. Win2008 R2 installation website security dog ​​prompts error 500.21 solution

Introduction: This article mainly introduces the solution to the HTTP error 500.21 when installing website security dog ​​in win2008 R2. Friends in need can refer to

##2. nginx's sbin and conf files are not in the same directory. How to install security dog

##Introduction: nginx's sbin How to install security dog ​​in a directory that is not in the same directory as the conf file: What is the essence of the problem? Generally, we use redhat system such as centos' yum and debian system's apt-get to install nginx. Generally, the sbin directory and conf directory are separated, so the security dog ​​cannot find the nginx directory, and it does not work when we enter the directory manually (as follows) As shown in the figure), because only one directory can be entered at a time, I have encountered this problem once before, on the centos server. At that time, cloud lock was used instead of the security dog. This time I explored the solution myself. So how did I solve it? The following is u

3.

phpmyadmin changes the sql statement to base64 transmission_PHP tutorial

Introduction: phpmyadmin changes the sql statement to base64 transmission. Because the security dog ​​function is installed on the server, our direct sql cannot be used. Let me introduce to the students how phpmyadmin can solve the problem by changing the sql statement to base64 transmission

4.

How to beat a dog with a stick: Cknife (C knife) Custom mode to beat a safe dog in seconds

Introduction: A method of beating a dog with a stick: Cknife (C knife) ) The custom mode surpasses the security dog ​​in seconds

5.

php-cgi takes up 100%, and the related problems are outrageous

Introduction: php-cgi takes up 100%, the problem is outrageous. Server: window2003 Microsoft-IIS/6.0, with server security dog ​​installed. Website: http://www.cits-sz.net. There were many "php-cgi" processes in the Task Manager, which had always been fine before, but the problem was even more outrageous. I let people from other places access it, and the CPU is normally around ten to twenty-thirty percent. From yesterday 2015.3.1

6.

phpmyadmin changed the sql statement to base64 transmission

Introduction: phpmyadmin changed sql The statement is changed to base64 transmission. Because the security dog ​​function is installed on the server, our direct sql cannot be used. Let me introduce to the students how phpmyadmin can solve the problem by changing the sql statement to base64 transmission

[Related Q&A recommendations]:

The above is the detailed content of Detailed information about safety dogs. For more information, please follow other related articles on the PHP Chinese website!