Jump to content

Apache HTTP Server

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by DorganBot (talk | contribs) at 21:24, 5 May 2012 (r2.7.3) (Robot: Modifying sr:Apač (server)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Apache HTTP Server
Original author(s)Robert McCool
Developer(s)Apache Software Foundation
Initial release1995[1]
Stable release
2.4.2 / April 17, 2012; 12 years ago (2012-04-17)
Repository
Written inXML and C[2]
Operating systemCross-platform
Available inEnglish
TypeWeb server
LicenseApache License 2.0
Websitehttpd.apache.org

The Apache HTTP Server, commonly referred to as Apache (/əˈpætʃiː/), is web server software notable for playing a key role in the initial growth of the World Wide Web.[3] In 2009 it became the first web server software to surpass the 100 million website milestone.[4] Apache was the first viable alternative to the Netscape Communications Corporation web server (currently named Oracle iPlanet Web Server), and since has evolved to rival other web servers in terms of functionality and performance[citation needed]. Typically Apache is run on a Unix-like operating system.[5]

Apache is developed and maintained by an open community of developers under the auspices of the Apache Software Foundation. The application is available for a wide variety of operating systems, including Unix, FreeBSD, Linux, Solaris, Novell NetWare, Mac OS X, Microsoft Windows, OS/2, TPF, and eComStation. Released under the Apache License, Apache is open-source software.

Apache was originally based on NCSA HTTPd code. The NCSA code has since been removed from Apache, due to a rewrite.

Since April 1996 Apache has been the most popular HTTP server software in use. As of March 2012 Apache was estimated to serve 57.46% of all active websites and 65.24% of the top servers across all domains.[6]

Name

According to the FAQ in the Apache project website, the name Apache was chosen out of respect to the Native American tribe Apache (Inde) and its superior skills in warfare and strategy. The website also explains the popular but erroneous origin of the name, A Patchy Server (since it was a conjunction of software patches)[7]

Features

Apache supports a variety of features, many implemented as compiled modules which extend the core functionality. These can range from server-side programming language support to authentication schemes. Some common language interfaces support Perl, Python, Tcl, and PHP. Popular authentication modules include mod_access, mod_auth, mod_digest, and mod_auth_digest, the successor to mod_digest. A sample of other features include Secure Sockets Layer and Transport Layer Security support (mod_ssl), a proxy module (mod_proxy), a URL rewriter (also known as a rewrite engine, implemented under mod_rewrite), custom log files (mod_log_config), and filtering support (mod_include and mod_ext_filter).

Popular compression methods on Apache include the external extension module, mod_gzip, implemented to help with reduction of the size (weight) of web pages served over HTTP. ModSecurity is an open source intrusion detection and prevention engine for web applications. Apache logs can be analyzed through a web browser using free scripts such as AWStats/W3Perl or Visitors.

Virtual hosting allows one Apache installation to serve many different actual websites. For example, one machine with one Apache installation could simultaneously serve www.example.com, www.example.org, test47.test-server.example.edu, etc.

Apache features configurable error messages, DBMS-based authentication databases, and content negotiation. It is also supported by several graphical user interfaces (GUIs).

It supports password authentication and digital certificate authentication. Apache has a built in search engine and an HTML authorizing tool and supports FTP.

Performance

Although the main design goal of Apache is not to be the "fastest" web server, Apache does have performance similar to other "high-performance" web servers. Instead of implementing a single architecture, Apache provides a variety of MultiProcessing Modules (MPMs) which allow Apache to run in a process-based, hybrid (process and thread) or event-hybrid mode, to better match the demands of each particular infrastructure. This implies that the choice of correct MPM and the correct configuration is important. Where compromises in performance need to be made, the design of Apache is to reduce latency and increase throughput, relative to simply handling more requests, thus ensuring consistent and reliable processing of requests within reasonable time-frames.

The Apache version considered by the Apache Foundation as providing high-performance is the multi-threaded version which mixes the use of several processes and several threads per process.[8] This architecture, and the way implemented in Apache 2.4.0, provides for performance at least equal to other event-based webservers [9]

Licensing

With the release of Apache 2.0, there was a change to the Apache Foundation license. Some Apache users[who?] did not like the change and continued the use of pre-2.0 Apache versions (typically 1.3.x). The OpenBSD project went to the extent of effectively forking Apache 1.3.x for its purposes.[10]

See also

Overview and discussions
Proxy servers
  • lighttpd - open-source web server, optimized for speed-critical environments
  • Nginx - lightweight, high-performance web server, reverse proxy and e-mail proxy (IMAP/POP3)
  • Polipo - lightweight pipelining, multiplexing proxy server and daemon for a small number of users
  • Pound reverse proxy
  • Privoxy - privacy enhancing proxy
  • Squid (software) - a proxy server and web cache daemon
  • Tinyproxy - a fast and small HTTP proxy server daemon, which supports reverse proxying and transparent proxying
  • Varnish - a performance-focused open source reverse proxy
  • Ziproxy - lightweight forwarding, non-caching, HTTP proxy for traffic optimization

References

  1. ^ "About the Apache HTTP Server Project". Apache Software Foundation. Retrieved 2008-06-25.
  2. ^ "Apache HTTP Server". Ohloh.net.
  3. ^ Netcraft Market Share for Top Servers Across All Domains August 1995 - November 2009
  4. ^ "February 2009 Web Server Survey". Netcraft. Retrieved 2009-03-29.
  5. ^ https://secure1.securityspace.com/s_survey/data/man.200907/apacheos.html
  6. ^ "March 2012 Web Server Survey". Netcraft. Retrieved 2012-03-05.
  7. ^ "Why the name 'Apache'?". HTTPd Frequently Asked Questions.
  8. ^ Apache MPM worker
  9. ^ (http://people.apache.org/~jim/presos/ACNA11/Apache_httpd_cloud.pdf Apache httpd 2.4)
  10. ^ OpenBSD however may ultimately replace Apache with Nginx, a 2-clause BSD licensed web server. [1]

Further reading

Retrieved from "https://en.wikipedia.org/w/index.php?title=Apache_HTTP_Server&oldid=490848194"