Apache HTTP Server: Difference between revisions

Browse history interactively

[unchecked revision]

VisualWikitext

@@ Line 20: / Line 20: @@
 }}
-The '''Apache HTTP Server''' ({{IPAc-en|ə|ˈ|p|æ|tʃ|i}} {{Respell|ə|PATCH|ee}}) is a [[free and open-source software|free and open-source]] cross-platform [[web server]], released under the terms of [[Apache License|Apache License 2.0]]. It is developed and maintained by a community of developers under the auspices of the [[Apache Software Foundation]].
+The '''Apache HTTP Server''' is a [[free and open-source software|free and open-source]] cross-platform [[web server]], released under the terms of [[Apache License|Apache License 2.0]]. It is developed and maintained by a community of developers under the auspices of the [[Apache Software Foundation]].
 The vast majority of Apache HTTP Server instances run on a [[Linux distribution]],<ref>{{Cite web|url=https://secure1.securityspace.com/s_survey/data/man.201808/apacheos.html|title=OS/Linux Distributions using Apache|website=secure1.securityspace.com|access-date=2018-09-17|archive-date=2018-09-18|archive-url=https://web.archive.org/web/20180918054337/https://secure1.securityspace.com/s_survey/data/man.201808/apacheos.html|url-status=live}}</ref> but current versions also run on [[Microsoft Windows]],<ref>{{Cite web|url=https://httpd.apache.org/docs/2.4/platform/index.html.en|title=Platform Specific Notes - Apache HTTP Server Version 2.4|website=httpd.apache.org|access-date=2019-01-21|archive-date=2019-01-22|archive-url=https://web.archive.org/web/20190122044008/https://httpd.apache.org/docs/2.4/platform/index.html.en|url-status=live}}</ref> [[OpenVMS]],<ref>{{cite web|url=https://vmssoftware.com/products/secure-web-server/|title=Secure Web Server|access-date=2020-10-20|website=vmssoftware.com|archive-date=2020-10-22|archive-url=https://web.archive.org/web/20201022051216/https://vmssoftware.com/products/secure-web-server/|url-status=live}}</ref> and a wide variety of [[Unix-like]] systems. Past versions also ran on [[NetWare]], [[OS/2]] and other operating systems,<ref name=older/> including ports to mainframes.<ref>{{Cite web|url=https://httpd.apache.org/docs/2.4/platform/ebcdic.html.en|title=The Apache EBCDIC Port - Apache HTTP Server Version 2.4|website=httpd.apache.org|access-date=2019-08-16|archive-date=2019-02-27|archive-url=https://web.archive.org/web/20190227063613/http://httpd.apache.org/docs/2.4/platform/ebcdic.html.en|url-status=live}}</ref>
-Originally based on the [[NCSA HTTPd]] server, development of Apache began in early 1995 after work on the NCSA code stalled.<ref>{{Cite web |title=About the Apache HTTP Server Project - The Apache HTTP Server Project |url=https://httpd.apache.org/ABOUT_APACHE.html |access-date=2024-02-08 |website=httpd.apache.org}}</ref> Apache played a key role in the initial growth of the [[World Wide Web]],<ref>[http://news.netcraft.com/archives/web_server_survey.html Netcraft Market Share] {{Webarchive|url=https://web.archive.org/web/20100520142533/http://news.netcraft.com/archives/web_server_survey.html |date=2010-05-20 }} for Top Servers Across All Domains August 1995 - today (monthly updated)</ref> quickly overtaking NCSA HTTPd as the dominant [[HTTP]] server. In 2009, it became the first web server software to serve more than 100 million [[website]]s.<ref name="100millionsites">{{Cite web|url=https://news.netcraft.com/archives/2009/02/18/february_2009_web_server_survey.html|title=February 2009 Web Server Survey|date=18 February 2009 |publisher=[[Netcraft]]|access-date=2009-03-29|archive-url= https://web.archive.org/web/20090226092501/http://news.netcraft.com//archives//2009//02//18//february_2009_web_server_survey.html|archive-date= 26 February 2009 |url-status= live}}</ref>
+Originally based on the [[NCSA HTTPd]] server, development of Apache began in early 1995 after work on the NCSA code stalled.<ref>{{Cite web |title=About the Apache HTTP Server Project - The Apache HTTP Server Project |url=https://httpd.apache.org/ABOUT_APACHE.html |access-date=2024-02-08 |website=httpd.apache.org}}</ref> Apache played a key role in the initial growth of the [[World Wide Web]],<ref>[http://news.netcraft.com/archives/web_server_survey.html Netcraft Market Share] {{Webarchive|url=https://web.archive.org/web/20100520142533/http://news.netcraft.com/archives/web_server_survey.html |date=2010-05-20 }} for Top Servers Across All Domains August 1995 - today (monthly updated)</ref> It quickly overtook NCSA HTTPd as the dominant web server software for [[HTTP]]. In 2009, it became the first web server software to serve more than 100 million [[website]]s.<ref name="100millionsites">{{Cite web|url=https://news.netcraft.com/archives/2009/02/18/february_2009_web_server_survey.html|title=February 2009 Web Server Survey|date=18 February 2009 |publisher=[[Netcraft]]|access-date=2009-03-29|archive-url= https://web.archive.org/web/20090226092501/http://news.netcraft.com//archives//2009//02//18//february_2009_web_server_survey.html|archive-date= 26 February 2009 |url-status= live}}</ref>
-{{As of|2025|03}}, [[Netcraft]] estimated that Apache served 17.83% of the million busiest websites, with the other top four being [[Cloudflare]] at 22.99%, [[Nginx]] at 20.11%, and [[Microsoft]] [[Internet Information Services]] at 4.16%.<ref>{{Cite web |title=March 2025 Web Server Survey |url=https://www.netcraft.com/blog/march-2025-web-server-survey/ |access-date=2025-04-14 |website=Netcraft News |date=25 March 2025 |language=en-gb |archive-date=2025-04-01 |archive-url=https://web.archive.org/web/20250401132934/https://www.netcraft.com/blog/march-2025-web-server-survey/ |url-status=live }}</ref> According to W3Techs' review of all web sites, in April 2025 Apache was ranked second at 26.4% and Nginx first at 33.8%, with Cloudflare Server third at 23.5%.<ref>{{Cite web |url=https://w3techs.com/technologies/overview/web_server |title=Usage Statistics of Web Servers |website=w3techs.com |access-date=2025-04-14}}</ref>
+{{As of|2025|03}}, [[Netcraft]] estimated that Apache served 17.83% of the million busiest websites, with the other top four being [[Cloudflare]] at 22.99%, [[Nginx]] at 20.11%, and [[Microsoft]] [[Internet Information Services]] at 4.16%.<ref>{{Cite web |title=March 2025 Web Server Survey |url=https://www.netcraft.com/blog/march-2025-web-server-survey/ |access-date=2025-04-14 |website=Netcraft News |date=25 March 2025 |language=en-gb |archive-date=2025-04-01 |archive-url=https://web.archive.org/web/20250401132934/https://www.netcraft.com/blog/march-2025-web-server-survey/ |url-status=live }}</ref> According to W3Techs' review of all web sites, in April 2026 Apache was ranked third at 23.7% and Nginx first at 32.7%, with Cloudflare Server second at 27.7%.<ref>{{Cite web |url=https://w3techs.com/technologies/overview/web_server |title=Usage Statistics of Web Servers |website=w3techs.com |access-date=2025-04-14}}</ref>
 ==Name==
 According to [[The Apache Software Foundation]], its name was chosen "from respect for the various [[Native Americans in the United States|Native American]] nations collectively referred to as [[Apache]], well-known for their superior skills in warfare strategy and their inexhaustible endurance".<ref name="Apache Foundation">{{cite web |title=Apache Foundation |url=https://www.apache.org/foundation/faq.html#name |website=www.apache.org |access-date=22 August 2018 |archive-date=13 December 2021 |archive-url=https://web.archive.org/web/20211213004914/https://www.apache.org/foundation/faq.html#name |url-status=live }}</ref> This was in a context in which it seemed that the open internet—based on free exchange of open source code—appeared to be soon subjected to a kind of conquer by proprietary software vendor [[Microsoft]]; Apache co-creator [[Brian Behlendorf]]—originator of the name—saw his effort somewhat parallel that of [[Geronimo]], Chief of the last of the free Apache peoples.<ref>{{cite web |url=https://www.youtube.com/watch?v=JUt2nb0mgwg&t=234 | archive-url=https://ghostarchive.org/varchive/youtube/20211122/JUt2nb0mgwg| archive-date=2021-11-22 | url-status=live|title="Trillions and Trillions Served" documentary feature on The Apache Software Foundation |publisher=TheApacheFoundation / Youtube |date=2020 }}{{cbignore}}</ref><ref>{{cite web |url=https://www.youtube.com/watch?v=u_dhmGNeNEc&t=2700 | archive-url=https://ghostarchive.org/varchive/youtube/20211122/u_dhmGNeNEc| archive-date=2021-11-22 | url-status=live|title=A Foundation of Trust: Building a Blockchain Future : Brian Behlendorf |date=2020-02-10 |publisher=Long Now Foundation / YouTube }}{{cbignore}}</ref> But it conceded that the name "also makes a cute [[pun]] on 'a patchy [[web server]]'—a server made from a series of [[Patch (computing)|patches]]".
-There are other sources for the "patchy" software pun theory, including the project's official documentation in 1995, which stated: "Apache is a cute name which stuck. It was based on some existing code and a series of software patches, a pun on 'A PAtCHy' server."<ref>{{Cite web|url=http://www.apache.org/info.html |title=Information on the Apache HTTP Server Project |date=1997-04-15 |url-status=dead |archive-url=https://web.archive.org/web/19970415054031/http://www.apache.org/info.html |archive-date=April 15, 1997 }}</ref><ref>{{cite web|title=Apache Server Frequently Asked Questions|url=http://www.apache.org/docs/misc/FAQ.html#relate|access-date=15 January 2017|archive-url=https://web.archive.org/web/19970106233141/http://www.apache.org/docs/misc/FAQ.html#relate |archive-date=1997-01-06}}</ref>
+Despite the Foundation's current claim that the name was chosen out of respect for Native Americans, previous statements, such as the project's official documentation in 1995, say that the name was instead based on a pun. This documentation did not mention Native American tribes in the context of the name:<ref>{{Cite web |date=1997-04-15 |title=Information on the Apache HTTP Server Project |url=http://www.apache.org/info.html |url-status=dead |archive-url=https://web.archive.org/web/19970415054031/http://www.apache.org/info.html |archive-date=April 15, 1997}}</ref><ref>{{cite web |title=Apache Server Frequently Asked Questions |url=http://www.apache.org/docs/misc/FAQ.html#relate |archive-url=https://web.archive.org/web/19970106233141/http://www.apache.org/docs/misc/FAQ.html#relate |archive-date=1997-01-06 |access-date=15 January 2017}}</ref>
-But in an April 2000 interview, Behlendorf asserted that the origins of Apache were not a pun, stating:<ref>{{cite web|url=http://www.linux-mag.com/id/472/|title=Apache Power|work=Linux Magazine |first = Robert|last = McMillan|date = 15 April 2000|url-status=usurped|archive-url = https://web.archive.org/web/20190128065900/http://www.linux-mag.com/id/472/ |archive-date = 28 January 2019}}</ref>
+{{Blockquote|text=Apache is a cute name which stuck. It was based on some existing code and a series of software patches, a pun on 'A PAtCHy' server.}}
+In addition, Behlendorf made no reference to Native American tribes when he talked about the origins of the name in a 2000 interview, where he stated that it was not a pun, but was instead chosen to be aggressive-sounding:<ref>{{cite web|url=http://www.linux-mag.com/id/472/|title=Apache Power|work=Linux Magazine |first = Robert|last = McMillan|date = 15 April 2000|url-status=usurped|archive-url = https://web.archive.org/web/20190128065900/http://www.linux-mag.com/id/472/ |archive-date = 28 January 2019}}</ref>
 {{Blockquote
@@ Line 39: / Line 41: @@
 }}
-In January 2023, the US-based non-profit Natives in Tech accused the Apache Software Foundation of [[cultural appropriation]] and urged them to change the foundation's name, and consequently also the names of the software projects it hosts.<ref>{{Cite web |last=Claburn |first=Thomas |date=2023-01-11 |title=Native Americans ask Apache foundation to change name |url=https://www.theregister.com/2023/01/11/native_american_apache_software_foundation/ |url-status=live |archive-url=https://web.archive.org/web/20230112000842/https://www.theregister.com/2023/01/11/native_american_apache_software_foundation/ |archive-date=2023-01-12 |access-date=2023-01-12 |website=[[The Register]] |language=en}}</ref><ref>{{Cite web |last=Purdy |first=Kevin |date=2023-01-12 |title=Indigenous tech group asks Apache Foundation to change its name |url=https://arstechnica.com/gadgets/2023/01/indigenous-tech-group-asks-apache-foundation-to-change-its-name/ |access-date=2023-01-12 |website=Ars Technica |language=en-us |archive-date=2023-01-12 |archive-url=https://web.archive.org/web/20230112181127/https://arstechnica.com/gadgets/2023/01/indigenous-tech-group-asks-apache-foundation-to-change-its-name/ |url-status=live }}</ref>
+In January 2023, the US-based non-profit Natives in Tech accused the Apache Software Foundation of [[cultural appropriation]] and urged them to change the foundation's name, and consequently also the names of the software projects it hosts. The Foundation did not change the name.<ref>{{Cite web |last=Claburn |first=Thomas |date=2023-01-11 |title=Native Americans ask Apache foundation to change name |url=https://www.theregister.com/2023/01/11/native_american_apache_software_foundation/ |url-status=live |archive-url=https://web.archive.org/web/20230112000842/https://www.theregister.com/2023/01/11/native_american_apache_software_foundation/ |archive-date=2023-01-12 |access-date=2023-01-12 |website=[[The Register]] |language=en}}</ref><ref>{{Cite web |last=Purdy |first=Kevin |date=2023-01-12 |title=Indigenous tech group asks Apache Foundation to change its name |url=https://arstechnica.com/gadgets/2023/01/indigenous-tech-group-asks-apache-foundation-to-change-its-name/ |access-date=2023-01-12 |website=Ars Technica |language=en-us |archive-date=2023-01-12 |archive-url=https://web.archive.org/web/20230112181127/https://arstechnica.com/gadgets/2023/01/indigenous-tech-group-asks-apache-foundation-to-change-its-name/ |url-status=live }}</ref>
 When Apache is running under [[Unix]], its process name is {{code|httpd}}, which is short for "HTTP [[Daemon (computing)|daemon]]".<ref>{{cite web |title=Apache Docs |url=https://httpd.apache.org/docs/current/invoking.html |website=httpd.apache.org |access-date=22 August 2018 |archive-date=5 September 2018 |archive-url=https://web.archive.org/web/20180905182937/http://httpd.apache.org/docs/current/invoking.html |url-status=live }}</ref>
 ==Feature overview==
-Apache supports a variety of features, many implemented as [[Compiler|compiled]] [[Modular programming|modules]] which extend the core functionality. These can range from [[authentication]] schemes to supporting [[server-side]] programming languages such as <!-- ATTENTION AUTO-EDITORS, THESE UNDERSCORES ARE INTENTIONAL -->[[mod perl|Perl]], [[mod python|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 [[Transport Layer Security#SSL 1.0, 2.0, and 3.0|Secure Sockets Layer]] and [[Transport Layer Security]] support ([[mod_ssl]]), a [[proxy server|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).
+Apache supports a variety of features, many implemented as [[Compiler|compiled]] [[Modular programming|modules]] which extend the core functionality. These include [[authentication]] features and support for [[server-side]] programming languages such as <!-- ATTENTION AUTO-EDITORS, THESE UNDERSCORES ARE INTENTIONAL -->[[mod perl|Perl]], [[mod python|Python]], [[Tcl (programming language)|Tcl]] and [[PHP]]. Apache also includes several authentication modules such as mod_access, mod_auth, mod_digest, and mod_auth_digest, the successor to mod_digest. A sample of other features include [[Transport Layer Security#SSL 1.0, 2.0, and 3.0|Secure Sockets Layer]] and [[Transport Layer Security]] support ([[mod_ssl]]), a [[proxy server|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).<ref>{{Cite web |title=Module Index - Apache HTTP Server Version 2.4 |url=https://httpd.apache.org/docs/2.4/mod/index.html.en |access-date=2026-05-24 |website=httpd.apache.org}}</ref>
 Popular compression methods on Apache include the external extension module, mod_gzip<!-- redirects to here -->, 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.
@@ Line 90: / Line 92: @@
 ==Performance==
-Instead of implementing a single architecture, Apache provides a variety of MultiProcessing Modules (MPMs), which allow it to run in either a [[Process (computing)|process]]-based mode, a hybrid (process and [[Thread (computing)|thread]]) mode, or an event-hybrid mode, in order to better match the demands of each particular infrastructure. Choice of MPM and configuration is therefore important.
+Instead of implementing a single architecture, Apache provides a variety of MultiProcessing Modules (MPMs) which determine how the server handles multiple connections and requests. These modules allow Apache to run in either a [[Process (computing)|process]]-based mode, a hybrid (process and [[Thread (computing)|thread]]) mode, or an event-driven mode, in order to better match the demands of different environments. Choice of MPM and configuration is therefore important.<ref>{{Cite web |title=Multi-Processing Modules (MPMs) - Apache HTTP Server Version 2.4 |url=https://httpd.apache.org/docs/2.4/mpm.html.en |access-date=2026-05-24 |website=httpd.apache.org}}</ref>
 For delivering static pages, Apache 2.2 series was considered significantly slower than [[nginx]] and [[Varnish (software)|varnish]].<ref>{{cite web|url=http://nbonvin.wordpress.com/2011/03/14/apache-vs-nginx-vs-varnish-vs-gwan/|title=Serving static files: a comparison between Apache, Nginx, Varnish and G-WAN|work=Spoot!|date=14 March 2011|access-date=23 April 2014|archive-date=24 April 2014|archive-url=https://web.archive.org/web/20140424234153/http://nbonvin.wordpress.com/2011/03/14/apache-vs-nginx-vs-varnish-vs-gwan/|url-status=live}}</ref> 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 [[Asynchrony (computer programming)|asynchronous]] [[Event loop|event-based loop]].<ref>{{cite web|url=https://httpd.apache.org/docs/2.2/mod/worker.html|title=worker - Apache HTTP Server Version 2.2|work=apache.org|access-date=2021-05-12|archive-date=2021-05-10|archive-url=https://web.archive.org/web/20210510050745/https://httpd.apache.org/docs/2.2/mod/worker.html|url-status=live}}</ref>{{clarify |date=August 2018 |reason=Mixes the use of xyz with what? Or, if (a) several processes and (b) several processes per thread are the things being mixed, the sentence should read "...Event MPM, which uses several processes and several threads per process...". Also, can someone with more technical knowledge please explain why this approach is advantageous?}} This architecture as implemented in the Apache 2.4 series performs at least as well as event-based web servers, according to [[Jim Jagielski]] and other independent sources.<ref>{{cite web| url = http://people.apache.org/~jim/presos/ACNA11/Apache_httpd_cloud.pdf| title = Apache httpd 2.4| access-date = 2012-02-08| archive-date = 2012-01-27| archive-url = https://web.archive.org/web/20120127033804/http://people.apache.org/~jim/presos/ACNA11/Apache_httpd_cloud.pdf| url-status = live}}</ref><ref>{{cite web|url=http://www.slideshare.net/bryan_call/choosing-a-proxy-server-apachecon-2014|title=Picking a Proxy Server|date=14 April 2014|access-date=19 February 2016|archive-date=3 March 2016|archive-url=https://web.archive.org/web/20160303105755/http://www.slideshare.net/bryan_call/choosing-a-proxy-server-apachecon-2014|url-status=live}}</ref><ref>{{cite web|url=http://blog.matsumoto-r.jp/?p=1812|title=Throughput evaluation of Apache 2.4.1|date=22 February 2012 |access-date=2016-02-19|archive-date=2016-03-02|archive-url=https://web.archive.org/web/20160302133533/http://blog.matsumoto-r.jp/?p=1812|url-status=live}}</ref> However, some independent but significantly outdated benchmarks show that it is still half as fast as nginx, e.g.<ref>{{cite web|url=http://www.eschrade.com/page/performance-of-apache-2-4-with-the-event-mpm-compared-to-nginx/|title=Performance of Apache 2.4 with the event MPM compared to Nginx|work=eschrade.com|date=3 January 2014|access-date=13 March 2014|archive-date=13 March 2014|archive-url=https://web.archive.org/web/20140313213901/http://www.eschrade.com/page/performance-of-apache-2-4-with-the-event-mpm-compared-to-nginx/|url-status=live}}</ref>
@@ Line 129: / Line 131: @@
 !scope="row" {{Version|c|2.4}}
 |2012-02-21<ref>{{Cite web|url=http://marc.info/?l=apache-httpd-announce&m=132983471818384&w=2|title=[ANNOUNCEMENT] Apache HTTP Server 2.4.1 Released|date=2012-02-21|access-date=2015-07-17|archive-date=2021-02-12|archive-url=https://web.archive.org/web/20210212205004/https://marc.info/?l=apache-httpd-announce&m=132983471818384&w=2|url-status=live}}</ref>
-|2025-01-23 (2.4.63)<ref>{{cite web |title=Apache HTTP Server 2.4.63 Released |url=https://downloads.apache.org/httpd/Announcement2.4.html |archive-url= |archive-date= |access-date=2025-02-20 |work=apache.org}}</ref>
+|2026-05-04 (2.4.67)<ref>{{cite web |title=Apache HTTP Server 2.4.67 Released |url=https://downloads.apache.org/httpd/Announcement2.4.html |archive-url= |archive-date= |access-date=2026-05-10 |work=apache.org}}</ref>
 |-
 |colspan="3"|{{Version|l|show=010100}}

Apache HTTP Server: Difference between revisions

Navigation menu

Search