DevShed: Getting More Out Of Apache (Part 2)

“Last time, I showed you how to configure Apache to service multiple Web sites on
the same physical server, and include server-side information in your Web page.
But that’s just the tip of the iceberg – Apache allows you to do a whole lot more,
and over the next few pages, I’ll be discussing the server’s authentication and logging capabilities,
together with a brief look at its unique URL re-writing module.”

“…Apache’s user authentication mechanism is based on the traditional username-password challenge
mechanism. When the Web server receives a request for a directory or file that it knows to be a protected
resource (aka “realm”), it responds by sending the client browser an authentication challenge. It is only
after receiving a valid username and password back from the client browser that access is granted to the
realm.”
Last time, I showed you how to configure Apache to service multiple Web sites on
the same physical server, and include server-side information in your Web page.
But that’s just the tip of the iceberg – Apache allows you to do a whole lot more,
and over the next few pages, I’ll be discussing the server’s authentication and logging capabilities,
together with a brief look at its unique URL re-writing module.