Since I’ve had 1390 hits where the page couldn’t be found, I’ve decided to add a custom 404 page. Now, when the page doesn’t exist, you’ll see this friendly error page, instead of the standard Apache one. A post on the LG Help forums lets you know how to do it – as long as you have an Apache web server you’re set.
Though for some reason the first time I added it, all the pages returned a 500 Internal Server error. I don’t quite know why, but removing a couple of 301/302 redirect lines from the .htaccess file seemed to do the trick.
Related Posts:
This work, unless otherwise expressly stated, is licensed under a Creative Commons Attribution-ShareAlike 2.0 UK: England & Wales License.
December 29, 2002 at 19:31
Most of my 404 errors seem to be for the “bookmark” icon favicon.ico (which I will probably have to create at some point in the near future).
The “code red” attacks are filtered out at the “server configuration” level with bits like:
# For Code Red
SetEnvIf Request_URI “^/default.ida” attacks nocommonlog
SetEnvIf Request_URI “\.ida$” attacks nocommonlog
# For Nimda
SetEnvIf Request_URI “^/scripts” attacks nocommonlog
SetEnvIf Request_URI “^/_mem_bin” attacks nocommonlog
SetEnvIf Request_URI “^/_vti_bin” attacks nocommonlog
SetEnvIfNoCase Request_URI “^/MSADC” attacks nocommonlog
SetEnvIf Request_URI “^/c/winnt” attacks nocommonlog
SetEnvIf Request_URI “^/d/winnt” attacks nocommonlog
SetEnvIf Request_URI “\.exe$” attacks nocommonlog
ErrorLog /error.log
CustomLog /access.log combined env=!nocommonlog
CustomLog /attacks.log combined env=attacks
You may be able to find some use for that information
December 30, 2002 at 09:25
let me know if you ever find out how to do it on an asp site (without getting the sysadmin guys involved!)