Thanks for posting this. I wasn't aware that Apache 2.2.12 supported SNI out of the box. SNI is kind of a big deal. It means that you can have multiple virtual hosts running HTTPS on the same IP address.
mod_proxy_balancer is also a very nice feature worth some attention.
SNI looks nice but considering that amount of SSL libraries out there that don't support it (including browsers), it will probably be something like 5-10 years before we could deploy SNI for a general purpose site/service.
Opera 8.0 and later (the TLS 1.1 protocol must be enabled)
Internet Explorer 7 or later (under Windows Vista and later only, not under Windows XP)
Firefox 2.0 or later
Curl 7.18.1 or later (when compiled against an SSL/TLS toolkit with SNI support)
Chrome (under Windows Vista and later only, not under Windows XP)
Safari 3.0 or later (when running under OS X 10.5.6 or later and under Windows Vista)
Something else most may have not known about apache is it has a built-in server-side scripting feature, think php w/o loops, called mod_include http://en.wikipedia.org/wiki/Shtml In the purest sense though, it is templating for html.
This feature is a bit dated and unnecessarily redundant if you write php, but could be great a addition if your back-end requires CGI or you don't wanna 'messy' up your pretty mark-up with php. ;)
Apache does too much. Whatever happened to the Unix dictum to "do one thing well"? I think this is actually a good reason for switching to Nginx whenever possible, where the conf files are tiny enough to be readable by mortals.
Dear writer. In the future, please refrain from telling your visitors "Well if you ain't gonna read the whole thing here's the best". Having your article on one fucking page usually ensures people will scroll to the bottom. Thank you.
mod_proxy_balancer is also a very nice feature worth some attention.