Apache HTTP Server
||This article may be too technical for most readers to understand. (September 2010) (Learn how and when to remove this template message)|
|Original author(s)||Robert McCool|
|Developer(s)||Apache Software Foundation|
|Stable release||2.4.27 (July 11, 2017[±])|
|Written in||C, XML|
|Operating system||Unix-like, Windows|
|License||Apache License 2.0|
Apache HTTP Server, colloquially called Apache (// ə-PA-chee), is free and open-source cross-platform web server software, released under the terms of Apache License 2.0. Apache is developed and maintained by an open community of developers under the auspices of the Apache Software Foundation.
Apache HTTP Server is cross-platform, meaning that it is built for Unix-like systems (e.g., macOS, Linux and FreeBSD) as well as Windows. However, As of 1 June 2017[update], 92.26% of all Apache HTTPS Server copies ran on Linux distributions. Version 2.0 improved support for non-Unix, e.g. Windows and OS/2 (and eComStation). Old versions of Apache were ported to run on e.g. OpenVMS, and NetWare.
Originally based on the NCSA HTTPd server, development of Apache began in early 1995 after work on the NCSA code stalled. Apache played a key role in the initial growth of the World Wide Web, quickly overtaking NCSA HTTPd as the dominant HTTP server, and has remained most popular since April 1996. In 2009, it became the first web server software to serve more than 100 million websites.
According to the FAQ in the Apache project website, the name Apache was chosen out of respect to the Native American tribe Apache and their superior skills in warfare and strategy. The name was widely believed to be a pun on 'A Patchy Server' (since it was a set of software patches). Official documentation used to give this explanation of the name, but in a 2000 interview, Brian Behlendorf, one of the creators of Apache, set the record straight:
The name literally came out of the blue. I wish I could say that it was something fantastic, but it was out of the blue. I put it on a page and then a few months later when this project started, I pointed people to this page and said: "Hey, what do you think of that idea?" ... Someone said they liked the name and that it was a really good pun. And I was like, "A pun? What do you mean?" He said, "Well, we're building a server out of a bunch of software patches, right? So it's a patchy Web server." I went, "Oh, all right." ... When I thought of the name, no. It just sort of connotated: "Take no prisoners. Be kind of aggressive and kick some ass."
When Apache is running, its process name is sometimes httpd, which is short for "HTTP daemon."
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 rewriting module (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 Web sites. For example, one machine with one Apache installation could simultaneously serve www.example.com, www.example.org, test47.test-server.example.edu, etc.
It supports password authentication and digital certificate authentication. Because the source code is freely available, anyone can adapt the server for specific needs, and there is a large public library of Apache add-ons.
HTTP server and proxy features
||This article is in a list format that may be better presented using prose. (August 2016)|
- Loadable Dynamic Modules
- Multiple Request Processing modes (MPMs) including Event-based/Async, Threaded and Prefork.
- Highly scalable (easily handles more than 10,000 simultaneous connections)
- Handling of static files, index files, auto-indexing and content negotiation
- .htaccess support
- Reverse proxy with caching
- TLS/SSL with SNI and OCSP stapling support, via OpenSSL.
- Name- and IP address-based virtual servers
- HTTP/2 protocol support
- Fine-grained authentication and authorization access control
- gzip compression and decompression
- URL rewriting
- Headers and content rewriting
- Custom logging with rotation
- Concurrent connection limiting
- Request processing rate limiting
- Bandwidth throttling
- Server Side Includes
- IP address-based geolocation
- User and Session tracking
- Embedded Perl, PHP and Lua scripting
- CGI support
- public_html per-user web-pages
- Generic expression parser
- Real-time status views
- XML support
- FTP support (by a separate module) 
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.
For delivery of static pages, Apache 2.2 series was considered significantly slower than nginx and varnish. To address this issue, the Apache developers created the Event MPM, which mixes the use of several processes and several threads per process in an asynchronous event-based loop. This architecture, and the way it was implemented in the Apache 2.4 series, provides for performance equivalent or slightly better than event-based web servers, as is cited by Jim Jagielski and other independent sources. However, some independent, but significantly outdated, benchmarks show that it still is half as fast as nginx, e.g. 
The Apache HTTP Server codebase was relicensed to the Apache 2.0 License (from the previous 1.1 license) in January 2004, and Apache HTTP Server 1.3.31 and 2.0.49 were the first releases using the new license.
The OpenBSD project did not like the change and continued the use of pre-2.0 Apache versions, effectively forking Apache 1.3.x for its purposes. They initially replaced it with Nginx, and soon after made their own replacement, OpenBSD Httpd, based on the relayd project.
Version 1.1: The Apache License 1.1 was approved by the ASF in 2000: The primary change from the 1.0 license is in the 'advertising clause' (section 3 of the 1.0 license); derived products are no longer required to include attribution in their advertising materials, but only in their documentation.
Version 2.0: The ASF adopted the Apache License 2.0 in January 2004. The stated goals of the license included making the license easier for non-ASF projects to use, improving compatibility with GPL-based software, allowing the license to be included by reference instead of listed in every file, clarifying the license on contributions, and requiring a patent license on contributions that necessarily infringe a contributor's own patents.
|Version||Initial release||Latest release|
|Old version, no longer supported: 1.3||1998-06-06||2010-02-03 (1.3.42)|
|Old version, no longer supported: 2.0||2002-04-06||2013-07-10 (2.0.65)|
|Old version, no longer supported: 2.2||2005-12-01||2017-07-11 (2.2.34)|
|Current stable version: 2.4||2012-02-21||2017-07-11 (2.4.27)|
The Apache HTTP Server Project is a collaborative software development effort aimed at creating a robust, commercial-grade, feature-rich and freely available source code implementation of an HTTP (Web) server. The project is jointly managed by a group of volunteers located around the world, using the Internet and the Web to communicate, plan, and develop the server and its related documentation. This project is part of the Apache Software Foundation. In addition, hundreds of users have contributed ideas, code, and documentation to the project.
- Comparison of web server software
- IBM HTTP Server
- LAMP (software bundle)
- List of Apache modules
- POSSE project
- "About the Apache HTTP Server Project". Apache Software Foundation. Archived from the original on 7 June 2008. Retrieved 2008-06-25.
- "Languages". Apache HTTP Server. Black Duck Software. Ohloh. Retrieved 2 April 2014.
- "Compiling and Installing". httpd.apache.org. The Apache Software Foundation. Retrieved 9 May 2016.
- "OS/Linux Distributions using Apache". 1 June 2017.
- "Overview of new features in Apache 2.0".
Apache 2.0 is faster and more stable on non-Unix platforms such as [..] OS/2, and Windows.
- "HP OpenVMS systems - Secure Web Server (based on Apache)". h41379.www4.hpe.com.
- Netcraft Market Share for Top Servers Across All Domains August 1995 - today (monthly updated)
- "February 2009 Web Server Survey". Netcraft. Archived from the original on 26 February 2009. Retrieved 2009-03-29.
- "July 2016 Web Server Survey". Netcraft. Netcraft. Archived from the original on 10 August 2016. Retrieved 10 August 2016.
- "Why the name 'Apache'?". HTTPd Frequently Asked Questions.
- "Information on the Apache HTTP Server Project". 1997-04-15. Archived from the original on April 15, 1997.
- "Apache Server Frequently Asked Questions". Archived from the original on 1997-01-06. Retrieved 15 January 2017.
- "Apache Power". Linux Magazine.
- "What is Apache Web Server? Webopedia". webopedia.com.
- "Apache HTTP Server Tutorial: .htaccess files".
- "Balancer Manager".
- "Authentication and Authorization".
- "Apache httpd Tutorial: Introduction to Server Side Includes".
- "Apache Tutorial: Dynamic Content with CGI".
- "Per-user web directorie".
- "Expressions in Apache HTTP Server".
- "Apache Module: mod_ftp".
- "Serving static files: a comparison between Apache, Nginx, Varnish and G-WAN". Spoot!.
- "worker - Apache HTTP Server Version 2.2". apache.org.
- Apache httpd 2.4
- "Picking a Proxy Server".
- "Throughput evaluation of Apache 2.4.1".
- "Performance of Apache 2.4 with the event MPM compared to Nginx". eschrade.com.
- "Apache License, Version 2.0". The Apache Software Foundation. January 2004. Retrieved 2013-05-21.
- Burton, Richard Antony. "FYI: Apache HTTP Server 2.0.49 Released". Newsgroup: alt.apache.configuration.
- de Raadt, Theo (18 February 2004). "The new apache license". openbsd-misc (Mailing list). Retrieved 2013-05-21.
- "Copyright Policy". OpenBSD. Retrieved 2013-05-12.
- "apache-httpd-openbsd-1.3.20140502p2 – OpenBSD improved and secured version of Apache 1.3". OpenBSD ports. Retrieved 2014-12-28.
- "OpenBSD Upgrade Guide: 5.1 to 5.2". openbsd.org.
- jj, ed. (2014-03-14). "Heads Up: Apache Removed from Base". OpenBSD Journal.
- "OpenBSD Upgrade Guide: 5.5 to 5.6". openbsd.org.
- "Announcement: Apache 1.3.0 Released !". 1998-06-06. Retrieved 2015-01-06.
- "Apache HTTP Server 1.3.42 released (final release of 1.3.x)". apache.org.
- "Official Release: Apache 2.0.35 is now GA". 2002-04-06. Retrieved 2015-01-06.
- "[Announcement] Apache HTTP Server 2.0.65 Released". apache.org.
- "Apache HTTP Server 2.2.0 Released". 2005-12-01. Retrieved 2015-01-06.
- "[Announce] Apache HTTP Server 2.2.34 Released". apache.org.
- "[ANNOUNCEMENT] Apache HTTP Server 2.4.1 Released". 2012-02-21. Retrieved 2015-07-17.
- "Apache HTTP Server 2.4.27 Released". apache.org.
- Documentation Group. "About the Apache HTTP Server Project - The Apache HTTP Server Project". apache.org.
- The Apache HTTP Server Open Source Project on Ohloh. (n.d.). Ohloh, the open source network. Retrieved November 12, 2012
- "Chapter 4. The Apache HTTP Server". fedoraproject.org.
- "Upgrading to 2.4 from 2.2".
Platform support has been removed for BeOS, TPF, and even older platforms such as A/UX, Next, and Tandem. These were believed to be broken anyway.