Reviewer rating:

I picked it up, well, because I buy every O'Reilly book that comes out (seriously) and thought I might be able to find something interesting, useful or that I wasn't aware of or forgot... maybe even a little tip about efficiency, compiling options or just anything of interest.

This is no more useful than the README and INSTALL files that come with Apache's source code. I'm not sure I want to even give this two stars come to think of it. I just don't see the point to this book. A let down coming from O'Reilly.

Reviewer rating:

The book covers pretty much everything you might want to know about running Apache on a *nix or Windows Operating System, but the basic attitude toward Windows users is "If it doesn't work for you - tough luck", which is fine, since Apache really isn't meant to run on Windows as anything more than a test server anyway. Still, I fear that a lot of the Windows folks who are jumping into the Open Source craze may pick this book up and be greatly disappointed.

Another problem I had with the book was the fact that it plays out as more of a step by step manual for setting up specific features of Apache. This makes it fairly difficult to use it for reference later on, but perhaps the idea was that once you got through this book, you could use the web and the manual as a reference instead.

All in all, the book is fairly useful, it just takes some getting used to. If you plan to use it to set up a Windows server, you'd probably be better off braving the various forums and threads out there available to Apache users. However, if you have a good Operating System (BSD, Unix, or Linux), and you want some extra help setting up your Apache server, or setting up specific parts of your Apache server, by all means give this book a shot. It's an above average book, but it's below average by O'Reilly standards.

Reviewer rating:

Hallelujah!
I think this book was exactly what I needed. Coming over from the M$ world where everything is a GUI, the httpd.conf file was a bit frustrating. Apache's online documentation was not newbie friendly. This book bridges that gap. I liked the way they begin with NO conf file and explains the Apache errors, and how to fix it in the conf file. The book then goes on adding additional functionality and options.

This book does not explain every configuration option available to Apache, and it is a bit outdated (covers up to version 1.3.n). The book did come with a CD with sample conf files, but I found that I didn't even need to use them. The book is NOT a complete desktop reference, but it helped me understand Apache conf files so now the Apache online documentation makes sense.

This book showed me the ropes and I'm successfully running Apache as my web server, which is all I was trying to do.

Reviewer rating:

User webuser
Group webgroup
Servername yourmachinename
DocumentRoot /usr/www/site.toddle/htdocs

Then in the following chapters they introduce different issues, and keep adding lines to the above configuration file and building seperate versions of more advanced sites.

However, there're several things that you might wanna be aware of before purchasing this book. Although the above mentioned feature of the book claims it's well-organized, it's not. Some of the directives just pop-up in the middle of the discussion, where they are not supposed to belong. I found that pretty annoying and confusing. I can recall the one about CERN Metafiles in chapter 3. Another annoying thing was the way they introduce directives. Consider the following lines from page 53:

ServerSignature [off|on|email]
Default: off
Directory, .htaccess

[ ...6 line description follows...]

Yes, it reminds me of the Apache's online documentation (which even does way better job than the above cold-blooded description). Of course, one expects more from a book than citing the online documentaion.

If you want to know what kind of audience the book is designed for, my answer is straightforward: I don't know, period! I have a feeling even the authors don't know anything about their potential readers. They try to get as detailed as they can where it doesn't make sence to do so. And when you expect some detail, they just ignore you.

I used the book as a referense during my internship, but it still didn't keep me from having to visit apache.org for more details. Now I am considering buying another book on Apache. I'll let you know :)