A PHP Error was encountered

Severity: 8192

Message: Methods with the same name as their class will not be constructors in a future version of PHP; Waterfall_Cache has a deprecated constructor

Filename: _common/waterfall_cache.php

Line Number: 47

A PHP Error was encountered

Severity: 8192

Message: Methods with the same name as their class will not be constructors in a future version of PHP; Cache_System has a deprecated constructor

Filename: _common/waterfall_cache.php

Line Number: 194

A PHP Error was encountered

Severity: 8192

Message: Methods with the same name as their class will not be constructors in a future version of PHP; Memcache_Cache_System has a deprecated constructor

Filename: _common/waterfall_cache.php

Line Number: 275

A PHP Error was encountered

Severity: 8192

Message: Methods with the same name as their class will not be constructors in a future version of PHP; Filesystem_Cache_System has a deprecated constructor

Filename: _common/waterfall_cache.php

Line Number: 440

A PHP Error was encountered

Severity: 8192

Message: Methods with the same name as their class will not be constructors in a future version of PHP; APC_Cache_System has a deprecated constructor

Filename: _common/waterfall_cache.php

Line Number: 628

Screaming-Penguin: Apache CodeRed Countermeasures with PHP: codeRedKiller!

Screaming-Penguin: Apache CodeRed Countermeasures with PHP: codeRedKiller!

By ServerWatch Staff (Send Email)
Posted Aug 20, 2001


"Code Red is a pain even for Apache administrators. Its takes up time and space even to send a 404. Wouldnt it be nice to be able to help alleviate the problem rather than just trying to bear it? Countermeasures? You bet, heres how to do it with PHP and bash (and note that this could easily be adapted to whatever you regularly employ, perl, jsp, etc.) The following is an explanation of the solution with source code and explicit instructions included below (PHP and bash.)"

"First off let me explain the premise. My goals are not to be malicious and to waste even more space and time dealing with the problem (ie, dont kill the offending server and the solution needs to have less overhead than a 404 or it there is no sense in doing it.)" Code Red is a pain even for Apache administrators. Its takes up time and space even to send a 404. Wouldnt it be nice to be able to help alleviate the problem rather than just trying to bear it? Countermeasures? You bet, heres how to do it with PHP and bash (and note that this could easily be adapted to whatever you regularly employ, perl, jsp, etc.).

Related Story:
ONLamp: Apache::CodeRed(Aug 17, 2001)

Page 1 of 1


Comment and Contribute

Your name/nickname

Your email

(Maximum characters: 1200). You have characters left.


 

 


Thanks for your registration, follow us on our social networks to keep up-to-date