http://www.webweaving.org/ical/
The recently released iCal can publish calendars; either to your .mac
account - or to any DAV enabled webserver. Apache 2.0 will work just
fine
out of the box; for apache 1.3 - from version 1.3.27 you are fine;
earlier versions need a patch (see below) as apache was somewhat too
strict in its Digest authentication parsing.
Apache web servers have the innate ability to issue user tracking cookies through a module called mod_usertrack. In order to utilize these tracking cookies, your Apache installation must have mod_usertrack enabled. Standard Apache installations sometimes come with mod_usertrack either compiled into the Apache httpd binary or built into Apache as a Dynamic Shared Object, also referred to as a DSO. Mod_usertrack must exist in either form for Apache to issue cookies.
NetIQ, the people who now own the Webtrends software, have a knowledge base article on:
How do I configure Apache web servers for user-tracking Cookies. It is quite in depth and I'll report back if/when I get it working.
A Day in the Life of #Apache by Rich Bowen -- Rich Bowen, coauthor of Apache Cookbook, spends a lot of time on IRC fielding Apache questions. In this inaugural article to launch a new series based on his conversations on #apache, the IRC channel that runs on the irc.freenode.net network, Rich chronicles a user's troubles getting his .htaccess file working, and he shows what you can do to solve the problem.
The step-by-step method he displays to solve the .htaccess problem is well thought out and teaches good problem solving techniques.
While CodeRed and Nimda have stopped being majorly annoying, I still get hit by infected computers looking to infect my Apache web server. Ha! Good luck. Not gunna happen. What it does do, however, is clog up my error_log files.
What I've done is take advantage of the strength of apache to set some variables and log these worm attacks elsewhere:
# For Code Red
SetEnvIf Request_URI "^/default.ida" iisworm
# For nimna (or whatever it's called)
SetEnvIf Request_URI "^/scripts" iisworm
# ... ditto all the way down
SetEnvIf Request_URI "^/c/winnt" iisworm
SetEnvIf Request_URI "^/_mem_bin" iisworm
SetEnvIf Request_URI "^/_vti_bin" iisworm
SetEnvIf Request_URI "^/MSADC" iisworm
SetEnvIf Request_URI "^/msadc" iisworm
SetEnvIf Request_URI "^/d/winnt" iisworm
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%v %h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" virt_host_combined
CustomLog /usr/local/apache/var/log/www/access_log combined env=!iisworm
CustomLog /usr/local/apache/var/log/iisworm.log virt_host_combined env=iisworm
So real hits get logged as normal, and any IIS worm related hits get logged elsewhere.
What's great about this method is that it allow me to define the environment variables once, and then use them in an VirtualHosts that I have defined. The virt_host_combined directive tells Apache to log which VirtualHost is getting hit.