I cannot stress how amazing the Apache community has been when I have needed help. Not only do I spend a lot of time reading the great documentation on the Apache web site, I subscribe to the Apache mailing lists, and when I really need help fast, I jump on the #Apache channel using IRC (server=irc.freenode.net). So, if you ever have any questions/problems with Apache, support is only a few minutes away. (I had questions about some mod_rewrite syntax yesterday that I got instant help with yesterday via the IRC channel.) I know I promised a link today to my XOOPS project, but I still need a day or so to figure out the cacheing. I am not someone who likes to release links unless they are pretty polished, and I am not there yet.
[tags]Apache, mod_rewrite[/tags]

Set Up: Mac OS X Client OS, one network card, and multiple Virtual Hosts (three of the Virtual Hosts need SSL certificates) using Apache.
Problem: I have been using Virtual Hosts with Apache for a few years and until now, I have only had one web site that has needed a SSL certificate. After rethinking site security, I decided at least two additional web sites needed SSL certificates so no passwords were sent as clear text while using http basic authentication. However, my current Virtual Host setup only supports one SSL certificate...and I need to use three.

Basic Apache background:
When configuring multiple Virtual Hosts in Apache, you can use IP-based Virtual Hosts, or name-based Virtual Hosts. (When using IP-based Virtual Hosts, the server uses an IP address for each Virtual Host. When using name-based Virtual Hosts, all sites use the same IP address and the client's browser sends the name of the site with each request. Apache then uses the name to determine which host should serve the request.) The problem with using name-based Virtual Hosts is that the host name is contained in the data stream (which is encrypted by SSL). In ... [more]

If you find yourself developing more than one web site at home, or anywhere with a *NIX machine with Apache, and want to be able to access all the sites for testing, it is time to set up Virtual Hosts. By using Virtual Hosts, you can access all your web sites easily (especially if you use absolute links) and separately by typing in: http://jappler/ and http://bareminimum/ and http://other. How does this work? Like I mentioned before, the first step is to set up Virtual Hosts. The second step is to edit your /etc/hosts file so you can assign names to your localhost address (jappler for http://jappler/)
Setting up Virtual Hosts

To set up virtual hosts, you will need to edit your Apache configuration (sudo pico /etc/httpd/httpd.conf). You can make a number of changes in the Apache configuration to set up an environment that is right for you, but for now, all you are concerned about is located at the end of the standard config file.
Uncomment the line: NameVirtualHost *:80 (delete the number sign in front of the line)
Add in your Virtual Hosts information:
< virtualhost *:80 >
ServerAdmin youremailaddress@whatever.com
... [more]

So you have a web server and one/some domain names. You want to have all requests to domain.com to go to www.domain.com. most companies have this redirect in place (Apple is an example). I was stumped when I first set out to do this...so here is what I learned from our friends on the Apache mailing list.

< virtualhost *:80 >
ServerName www.domain.com
ServerAlias domain.com
Redirect permanent / http://www.domain.com/
< /virtualhost >

< virtualhost *:80 >
ServerName www.domain.com
ServerAdmin webmaster@domain.com
DocumentRoot /Volumes/www/domain.com/documents
< /virtualhost >

This set up in Apache will then redirect all domain.com requests to www.domain.com.
You cannot beat mailing lists' support!
[tags]apache, vhosts, redirect[/tags]

If you ever need to serve a web site for, let's say a presentation, on a local address and need to connect to another computer...perhaps your database/ Web Objects server locally as well, and you are running Mac OS X...then I have some information for you.

If you want to serve the web site on 10.0.0.2 and have your other server on 10.0.0.3, open the terminal and type in: sudo ifconfig en0 10.0.0.2. This will change the IP address. (changing the IP address in the network control panel was not enough)
Next, edit the apache conf file: sudo pico /etc/httpd/httpd.conf and add Listen 10.0.0.2:80 and then restart apache

Now you can serve 10.0.0.2 on your local machine and connect to a computer on your local network. (connected by an ethernet cable)

After spending the weekend with my parents, proud new owners of a G4 14" iBook, I realized why I get paid the big bucks for administering computers/servers. The biggest contribution to my wealth: I read manuals. I also frequent application specific support web sites, and I sign up for listervs. I have been working with Apache for four years and have been able to learn a lot about it through all of the usual support mechanisms, but Apache also offers something great for problems that cannot wait: an irc channel with some of the best and brightest Apache developers and users.

I have been in a jam with some SSL problems that needed to be solved within one business day and I would not have been able to do it without the help from the experts at the #apache channel on irc.freenode.net.

So if you ever need some Apache help, or have time to help others, jump on the #apache channel!