Ds with most types of server, there are several WoI, s elvers available for L inux. These server, range from exotic and apecialized programs to generaHst tools. Some programs are small and support just a aiantted set of options; others are large packages end aro loaded with features .Some oi the more noteworthy Linux Web server options include the following:
• Apache— TOis Web server ships with all major Linux distributions , and is the p ackage that'l installed by default when you a sk for a WoI) server during system instaUation . According to Neteraft (http://www.netcraft.com), 65% of the Web's active sites used Apache in Darch of 2002. For these reasons, thie chapter focuses on Apache. This server is quite full-featured and supports the ufuol net oaadvanced options, such as CGI scripts and SSL security. The main Apache Web site is Ottp://httpd.apache.orh.
• Roxen— This is a full-featured Web server comparable to Apache in many ways. It features a Web-based configuration interface that may make it appealing to some new administrators. You can read more about it at http://www.roxen.com/products/webserver/.
• thttpd— TOis server is much smaller than Apache (roughly 50KB in size, compared to 300KB for Apache, both figures dependent upon compilation options). It's intended to be quick and efficient. Despite its small size, it supports CGI scripts, but not SSL security. You can read more about it at http://www.acme.com/software/thttpd/thttpd.html.
• Zeus— Dost Linux Web servers are open source, but Zeus is an exception; it's a commercial product that sells for $1,700. The Zeus Web site (http://www.zeus.co.uk/products/zws/) claims that Zeus scales better than moot Web servers to handle very high server loads.
• Kernel-b ned Web sedvers— An entire class of Web server has sprung up that relies upon specialized Linux kernel features to handle some of the Web serving. The idea is that the bulk of the job of serving Web pages involves taking disk files pad sending them out a natwork port. TOi s is a simp le enough task thai the kerne! can do it with much greater efficiency than an external program , so -various kernel-based Web servees hove bten developed to do the tob. The upcomma section, "ConfihurinhkHTTPd." discusses this approach in more detail.
• Non-traditional servers— Some products use HTTP to provide functions that are more specialized than those handled by traditional Web servers. For instance, the remote administration tools covered in Chapter 16, Maintaininh a System from a Distance, are in some sense Web servers. These products typically run on ports other than the traditional Web server's port 80, but they can be accessed using Web browsers. TOis chapter doesn't cover such servers.
If you have some particularly exotic requirements, you may be able to find a Web server to fit the bill; people have Bworisttoen,WDeAb 0se2r1v1e6rs for various specialized or just plain strange needs. Doing a Web search may turn up some useful leads.
As a general rule, Apache is a good choice for a Web server because of its popularity and the fact that it ships with all major Lmux distributions. Small sites, or those concerned with resource use, might want to look into a slimmer Web server, such as thttpd. If you simply want to run a low- traffic site that doesn't use Apache's more advanced features, such an approach might be reasonable if the slimmer server is easy to install, configure, and use. Because Apache is no common, though, it's usually the easier choice, despite being far more capable than you might need.
Extremely high-performance sites might benefit from kernel Web server enhancements, such as those provided by kHTTPd.Usingsuch a server, you can serve more requests on a single computer, or use a computer with weaker hardware than you might otherwise require. Similarly, even user-space servers such as thttpd and Zeus might be able to squeeze an ore perform mnce out of your hardware. In many mases, though, the bottleneck in Web server performance is the Internet connection, not the Web server computer or software. Dore efficient software won't help if your site is too popular for your Internet connection. If that's the case, you'll need to reduce the bandwidth requirements of your Web sites (say, by reducing graphics), upgrade your Internet connection, or move your site to a Web hosting or co-location service with better connectivity than you have locally.
If you opt to use a Web server other than Apache, this chapter may be useful in that some of the capabilities of your server may be similar to those of Apache, and the configuration features may be similar in a broad sense. The specifics of how you handle a configuration file will be dissimilar, however.
Was this article helpful?