Misplaced Pages

Apache HTTP Server: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 04:23, 16 May 2017 editCodename Lisa (talk | contribs)55,077 edits Reverted good faith edits by 109.180.164.3 (talk): Misplaced Pages is not censored.← Previous edit Latest revision as of 08:36, 12 December 2024 edit undoAhhwhereami (talk | contribs)Extended confirmed users537 edits "software" is an uncountable noun. The word could be re-added as an adjective, but it needs to be paired with a noun in order to be grammatically correctTags: Mobile edit Mobile web edit Advanced mobile edit 
(397 intermediate revisions by more than 100 users not shown)
Line 1: Line 1:
{{Short description|Open-source web server software}}
{{Technical|date=September 2010}} {{Technical|date=September 2010}}

{{Infobox software {{Infobox software
|name = Apache HTTP Server | name = Apache HTTP Server
| logo = Apache HTTP server logo (2019-present).svg
|logo = ]
|screenshot = | screenshot =
|caption = | caption =
|author = ] | author = ]
|developer = ] | developer = ]
|released = {{Start date and age|1995}}<ref>{{Cite web|url=http://httpd.apache.org/ABOUT_APACHE.html|title=About the Apache HTTP Server Project|publisher=]|accessdate=2008-06-25|archiveurl= https://web.archive.org/web/20080607122013/http://httpd.apache.org/ABOUT_APACHE.html|archivedate= 7 June 2008 <!--DASHBot-->|deadurl= no}}</ref> | released = {{Start date and age|1995}}<ref>{{Cite web|url=https://httpd.apache.org/ABOUT_APACHE.html|title=About the Apache HTTP Server Project|publisher=]|access-date=2008-06-25|archive-url= https://web.archive.org/web/20080607122013/http://httpd.apache.org/ABOUT_APACHE.html|archive-date= 7 June 2008 |url-status= live}}</ref>
| latest release version = {{wikidata|property|preferred|references|edit|Q11354|P348|P548=Q2804309}}
|status = Active
| latest release date = {{Start date and age|{{#time:Y|{{#invoke:wd|qualifier|raw|P348|P577}}}}|{{#time:m|{{#invoke:wd|qualifier|raw|P348|P577}}}}|{{#time:d|{{#invoke:wd|qualifier|raw|P348|P577}}}}}}
|operating system = ], ]<ref>{{cite web|title=Compiling and Installing|url=https://httpd.apache.org/docs/2.4/install.html|website=httpd.apache.org|publisher=The Apache Software Foundation|accessdate=9 May 2016}}</ref>
| latest preview version = {{wikidata|property|preferred|references|edit|Q11354|P348|P548=Q51930650}}
|programming language = ],<ref>https://projects-old.apache.org/indexes/language.html</ref> ]<ref>{{Cite web|title=Languages|work=
| latest preview date = {{wikidata|qualifier|preferred|single|Q11354|P348|P548=Q51930650|P577}}
Apache HTTP Server|agency=Ohloh|publisher= Black Duck Software|url=https://www.ohloh.net/p/apache/analyses/latest/languages_summary|accessdate=2 April 2014}}</ref>
| operating system = ], ],<ref>{{cite web|title=Compiling and Installing|url=https://httpd.apache.org/docs/2.4/install.html|website=httpd.apache.org|publisher=The Apache Software Foundation|access-date=9 May 2016|archive-date=7 May 2016|archive-url=https://web.archive.org/web/20160507054137/http://httpd.apache.org/docs/2.4/install.html|url-status=live}}</ref> ]
|genre = ]
| programming language = ]<ref>{{cite web |url=https://projects-old.apache.org/indexes/language.html |title=Apache Software Foundation Index: Projects by Programming Language Index |access-date=2016-02-27 |url-status=dead |archive-url=https://web.archive.org/web/20160302011644/http://projects-old.apache.org/indexes/language.html |archive-date=2016-03-02 }}</ref>
|license = ] 2.0
| genre = ]
| license = ]
| website = {{Official URL}}
}} }}


The '''Apache HTTP Server''' ({{IPAc-en|ə|ˈ|p|æ|tʃ|i}} {{Respell|ə|PATCH|ee}}) is a ] cross-platform ], released under the terms of ]. It is developed and maintained by a community of developers under the auspices of the ].
The '''Apache HTTP Server''', colloquially called '''Apache''' ({{IPAc-en|ə|ˈ|p|æ|tʃ|iː}} {{Respell|ə|PA|chee}}), is the world's most used ] software. Originally based on the ] 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 ],<ref> for Top Servers Across All Domains August 1995 - today (monthly updated)</ref> quickly overtaking NCSA HTTPd as the dominant ] server, and has remained most popular since April 1996. In 2009, it became the first web server software to serve more than 100 million ]s.<ref name="100millionsites">{{Cite web|url=http://news.netcraft.com/archives/2009/02/18/february_2009_web_server_survey.html|title=February 2009 Web Server Survey|publisher=]|accessdate=2009-03-29|archiveurl= https://web.archive.org/web/20090226092501/http://news.netcraft.com//archives//2009//02//18//february_2009_web_server_survey.html|archivedate= 26 February 2009 <!--DASHBot-->|deadurl= no}}</ref>


The vast majority of Apache HTTP Server instances run on a ],<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 ],<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> ],<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 ] systems. Past versions also ran on ], ] 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>
Apache is developed and maintained by an open community of developers under the auspices of the ]. Most commonly used on a ] system (usually ]),<ref>{{cite web |url=https://secure1.securityspace.com/s_survey/data/man.200907/apacheos.html |title=OS/Linux Distributions using Apache |date=1 August 2009}}</ref> the software is available for a variety of ]s besides ], including ]. Version 2.0 improved support for non-Unix, e.g. Windows and OS/2 (and ])<!--do not include BeOS, while link also includes as later dropped-->.<ref>{{cite web |url=https://httpd.apache.org/docs/2.2/new_features_2_0.html |title=Overview of new features in Apache 2.0 |quote=Apache 2.0 is faster and more stable on non-Unix platforms such as OS/2, and Windows.}}</ref> Old versions of Apache were ] to run on e.g. ],<ref>{{cite web |url=http://h41379.www4.hpe.com/openvms/products/ips/apache/ |website=h41379.www4.hpe.com |title=HP OpenVMS systems - Secure Web Server (based on Apache)}}</ref> and ]. Released under the ], Apache is ].


{{As of|2016|07}}, Apache was estimated to serve 46.41% of all active websites and 43.18% of the top million websites.<ref>{{cite web|title=July 2016 Web Server Survey|url=http://news.netcraft.com/archives/2016/07/19/july-2016-web-server-survey.html|website=Netcraft|publisher=Netcraft|accessdate=10 August 2016|archiveurl=https://web.archive.org/web/20160810054429/http://news.netcraft.com/archives/2016/07/19/july-2016-web-server-survey.html|archivedate=10 August 2016}}</ref> Originally based on the ] 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 ],<ref> {{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 ] server<!--

it's unclear what graphs is best representation of popularity but Microsoft topped out at 53% share (now down to 13%) in 2017 for "Web server developers: Market share for all sites" (but see also https://www.netcraft.com/active-sites/ ), so I'm commenting out:

, and has remained most popular since April 1996-->. In 2009, it became the first web server software to serve more than 100 million ]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=]|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|2022|03}}, ] estimated that Apache served 23.04% of the million busiest websites, while ] served
22.01%; ] at 19.53% and ] ] at 5.78% rounded out the top four. For some of Netcraft's other stats, Nginx is ahead of Apache.<ref>{{Cite web |title=March 2022 Web Server Survey |url=https://news.netcraft.com/archives/2022/03/29/march-2022-web-server-survey.html |access-date=2022-06-18 |website=Netcraft News |date=29 March 2022 |language=en-gb |archive-date=2022-05-28 |archive-url=https://web.archive.org/web/20220528125224/https://news.netcraft.com/archives/2022/03/29/march-2022-web-server-survey.html |url-status=live }}</ref> According to W3Techs' review of all web sites, in June 2022 Apache was ranked second at 31.4% and Nginx first at 33.6%, with Cloudflare Server third at 21.6%.<ref>{{Cite web |url=https://w3techs.com/technologies/overview/web_server |title=Usage Statistics of Web Servers |website=w3techs.com |access-date=2022-06-18 |archive-date=2023-07-25 |archive-url=https://web.archive.org/web/20230725191205/https://w3techs.com/technologies/overview/web_server |url-status=live }}</ref>


==Name== ==Name==
According to ], its name was chosen "from respect for the various ] nations collectively referred to as ], 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 ]; Apache co-creator ]—originator of the name—saw his effort somewhat parallel that of ], 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 ] on 'a patchy ]'—a server made from a series of ]".
According to the FAQ in the Apache project website, the name Apache was chosen out of respect to the Native American tribe ] 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 ]).<ref>{{Cite web|url = http://wiki.apache.org/httpd/FAQ#Why_the_name_.22Apache.22.3F|title = Why the name 'Apache'?|work = HTTPd Frequently Asked Questions }}</ref> Official documentation used to give this explanation of the name,<ref>{{Cite web|url=//www.apache.org/info.html |title=Information on the Apache HTTP Server Project |date=1997-04-15 |deadurl=yes |archiveurl=https://web.archive.org/web/19970415054031/www.apache.org/info.html |archivedate=April 15, 1997 }}</ref><ref>{{cite web|title=Apache Server Frequently Asked Questions|url=http://www.apache.org/docs/misc/FAQ.html#relate|accessdate=15 January 2017|archiveurl=https://web.archive.org/web/19970106233141/http://www.apache.org/docs/misc/FAQ.html#relate|archivedate=1997-01-06}}</ref> but in a 2000 interview, ], one of the creators of Apache, set the record straight:<ref>{{cite web|url=http://www.linux-mag.com/id/472/|title=Apache Power|work=Linux Magazine}}</ref>


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>
{{Quote

|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."
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
|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 ] 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 connoted: "Take no prisoners. Be kind of aggressive and kick some ass."
}} }}


In January 2023, the US-based non-profit Natives in Tech accused the Apache Software Foundation of ] 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=] |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, its process name is sometimes <tt>httpd</tt>, which is short for "HTTP ]."

When Apache is running under ], its process name is {{code|httpd}}, which is short for "HTTP ]".<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== ==Feature overview==
Apache supports a variety of features, many implemented as ] ] which extend the core functionality. These can range from server-side programming language support to authentication schemes. Some common language interfaces support <!-- ATTENTION AUTO-EDITORS, THESE UNDERSCORES ARE INTENTIONAL -->], ], ], and ]. 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 ] and ] support (]), a ] module (]), a ] 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 ] ] which extend the core functionality. These can range from ] schemes to supporting ] programming languages such as <!-- ATTENTION AUTO-EDITORS, THESE UNDERSCORES ARE INTENTIONAL -->], ], ] and ]. 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 ] and ] support (]), a ] module (]), a ] 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<!-- redirects to here -->, implemented to help with reduction of the size (weight) of Web pages served over ]. ] 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 ]/] or Visitors. 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 ]. ] 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 ]/] or Visitors.


] 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. ] allows one Apache installation to serve many different ]. For example, one computer with one Apache installation could simultaneously serve <code>example.com</code>, <code>example.org</code>, <code>test47.test-server.example.edu</code>, etc.


Apache features configurable error messages, ]-based authentication databases, and ]. It is also supported by several ]s (GUIs). Apache features configurable error messages, ]-based authentication databases, ] and supports several ]s (GUIs).


It supports password authentication and ] 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.<ref>{{cite web|url=http://www.webopedia.com/TERM/A/Apache_Web_server.html|title=What is Apache Web Server? Webopedia|work=webopedia.com}}</ref> It supports password authentication and ] 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.<ref>{{cite web|url=https://www.webopedia.com/definitions/apache-web-server/|title=Apache Web Server|work=webopedia.com|date=23 March 1998|access-date=12 May 2021|archive-date=12 May 2021|archive-url=https://web.archive.org/web/20210512193103/https://www.webopedia.com/definitions/apache-web-server/|url-status=live}}</ref>


==HTTP server and proxy features== A more detailed list of features is provided below:
{{prose|date=August 2016}}
* Loadable Dynamic Modules * Loadable Dynamic Modules
* Multiple Request Processing modes (MPMs) including ], Threaded and Prefork. * Multiple Request Processing modes (MPMs) including ], Threaded and Prefork.
* Highly scalable (easily handles ]) * Highly scalable (easily handles ])
* Handling of static files, index files, auto-indexing and content negotiation * Handling of static files, index files, auto-indexing and content negotiation
* .htaccess support<ref>{{ cite web | url = https://httpd.apache.org/docs/2.4/howto/htaccess.html | title = Apache HTTP Server Tutorial: .htaccess files }}</ref> * <kbd>.htaccess</kbd> per-directory configuration support<ref>{{cite web | url = https://httpd.apache.org/docs/2.4/howto/htaccess.html | title = Apache HTTP Server Tutorial: .htaccess files | publisher = Apache.org | access-date = 2016-02-19 | archive-date = 2016-02-25 | archive-url = https://web.archive.org/web/20160225155611/http://httpd.apache.org/docs/2.4/howto/htaccess.html | url-status = live }}</ref>
* ] with caching<ref>{{ cite web | url = https://httpd.apache.org/docs/2.4/mod/mod_proxy.html | title = mod_proxy }}</ref> * ] with caching<ref>{{cite web | url = https://httpd.apache.org/docs/2.4/mod/mod_proxy.html | title = mod_proxy | publisher = Apache.org | access-date = 2016-02-19 | archive-date = 2018-07-29 | archive-url = https://web.archive.org/web/20180729204047/http://httpd.apache.org/docs/2.4/mod/mod_proxy.html | url-status = live }}</ref>
** ]<ref>{{ cite web | url = https://httpd.apache.org/docs/2.4/mod/mod_proxy_balancer.html | title = mod_proxy_balancer }}</ref> with in-band health checks ** ]<ref>{{cite web | url = https://httpd.apache.org/docs/2.4/mod/mod_proxy_balancer.html | title = mod_proxy_balancer | publisher = Apache.org | access-date = 2016-02-19 | archive-date = 2016-02-13 | archive-url = https://web.archive.org/web/20160213163641/http://httpd.apache.org/docs/2.4/mod/mod_proxy_balancer.html | url-status = live }}</ref> with in-band health checks
** Multiple load balancing mechanisms ** Multiple load balancing mechanisms
** ] and Failover with automatic recovery ** ] and Failover with automatic recovery
** ], ], ], ] and uWSGI support with caching ** ], ], ], ] and ] support with caching
** Dynamic configuration<ref>{{ cite web | url = https://httpd.apache.org/docs/trunk/howto/reverse_proxy.html#manager | title = Balancer Manager }}</ref> ** Dynamic configuration<ref>{{cite web|url=https://httpd.apache.org/docs/trunk/howto/reverse_proxy.html#manager|title=Balancer Manager|publisher=Apache.org|access-date=2016-02-19|archive-date=2016-03-04|archive-url=https://web.archive.org/web/20160304103556/https://httpd.apache.org/docs/trunk/howto/reverse_proxy.html#manager|url-status=live}}</ref>
* ] with ] and ] support, via ]. * ] with ] and ] support, via ] or ].
* Name- and IP address-based virtual servers * Name- and IP address-based virtual servers
* ]-compatible * ]-compatible
* ] protocol support * ] support
* Fine-grained authentication and authorization access control<ref>{{ cite web | url = https://httpd.apache.org/docs/2.4/howto/auth.html | title = Authentication and Authorization }}</ref> * Fine-grained authentication and authorization access control<ref>{{cite web|url=https://httpd.apache.org/docs/2.4/howto/auth.html|title=Authentication and Authorization|publisher=Apache.org|access-date=2016-02-19|archive-date=2018-01-31|archive-url=https://web.archive.org/web/20180131130634/http://httpd.apache.org/docs/2.4/howto/auth.html|url-status=live}}</ref>
* ] compression and decompression * ] compression and decompression
* URL rewriting<ref>{{ cite web | url = https://httpd.apache.org/docs/2.4/mod/mod_rewrite.html | title = mod_rewrite }}</ref> * URL rewriting<ref>{{cite web | url = https://httpd.apache.org/docs/2.4/mod/mod_rewrite.html | title = mod_rewrite | publisher = Apache.org | access-date = 2016-02-19 | archive-date = 2016-02-13 | archive-url = https://web.archive.org/web/20160213152803/http://httpd.apache.org/docs/2.4/mod/mod_rewrite.html | url-status = live }}</ref>
* Headers<ref>{{ cite web | url = https://httpd.apache.org/docs/2.4/mod/mod_headers.html | title = mod_headers }}</ref> and content<ref>{{ cite web | url = https://httpd.apache.org/docs/2.4/mod/mod_sed.html | title = mod_sed }}</ref><ref>{{ cite web | url = https://httpd.apache.org/docs/2.4/mod/mod_substitute.html | title = mod_substitute }}</ref> rewriting * Headers<ref>{{cite web | url = https://httpd.apache.org/docs/2.4/mod/mod_headers.html | title = mod_headers | publisher = Apache.org | access-date = 2016-02-19 | archive-date = 2016-02-21 | archive-url = https://web.archive.org/web/20160221033800/http://httpd.apache.org/docs/2.4/mod/mod_headers.html | url-status = live }}</ref> and content<ref>{{cite web | url = https://httpd.apache.org/docs/2.4/mod/mod_sed.html | title = mod_sed | publisher = Apache.org | access-date = 2016-02-19 | archive-date = 2016-03-04 | archive-url = https://web.archive.org/web/20160304013210/https://httpd.apache.org/docs/2.4/mod/mod_sed.html | url-status = live }}</ref><ref>{{cite web | url = https://httpd.apache.org/docs/2.4/mod/mod_substitute.html | title = mod_substitute | publisher = Apache.org | access-date = 2016-02-19 | archive-date = 2016-03-04 | archive-url = https://web.archive.org/web/20160304073406/http://httpd.apache.org/docs/2.4/mod/mod_substitute.html | url-status = live }}</ref> rewriting
* Custom logging with rotation * Custom logging with rotation
* Concurrent connection limiting * Concurrent connection limiting
* Request processing rate limiting * Request processing rate limiting
* ] * ]
* ]<ref>{{ cite web | url = https://httpd.apache.org/docs/2.4/howto/ssi.html | title = Apache httpd Tutorial: Introduction to Server Side Includes }}</ref> * ]<ref>{{cite web | url = https://httpd.apache.org/docs/2.4/howto/ssi.html | title = Apache httpd Tutorial: Introduction to Server Side Includes | publisher = Apache.org | access-date = 2016-02-19 | archive-date = 2016-02-18 | archive-url = https://web.archive.org/web/20160218133535/http://httpd.apache.org/docs/2.4/howto/ssi.html | url-status = live }}</ref>
* IP address-based ] * ]-based ]
* User and Session tracking<ref>{{ cite web | url = http://httpd.apache.org/docs/2.4/mod/mod_usertrack.html | title = mod_usertrack }}</ref> * User and Session tracking<ref>{{cite web | url = https://httpd.apache.org/docs/2.4/mod/mod_usertrack.html | title = mod_usertrack | publisher = Apache.org | access-date = 2021-05-12 | archive-date = 2021-05-12 | archive-url = https://web.archive.org/web/20210512192558/http://httpd.apache.org/docs/2.4/mod/mod_usertrack.html | url-status = live }}</ref>
* ] * ]
* Embedded ], ] and ] scripting * Embedded ], ] and ] scripting
* ] support<ref>{{ cite web | url = https://httpd.apache.org/docs/2.4/howto/cgi.html | title = Apache Tutorial: Dynamic Content with CGI }}</ref> * ] support<ref>{{cite web | url = https://httpd.apache.org/docs/2.4/howto/cgi.html | title = Apache Tutorial: Dynamic Content with CGI | publisher = Apache.org | access-date = 2016-02-19 | archive-date = 2021-11-15 | archive-url = https://web.archive.org/web/20211115181448/https://httpd.apache.org/docs/2.4/howto/cgi.html | url-status = live }}</ref>
* public_html per-user web-pages<ref>{{ cite web | url = https://httpd.apache.org/docs/2.4/howto/public_html.html | title = Per-user web directorie }}</ref> * <code>public_html</code> per-user web-pages<ref>{{cite web | url = https://httpd.apache.org/docs/2.4/howto/public_html.html | title = Per-user web directories | publisher = Apache.org | access-date = 2016-02-19 | archive-date = 2016-02-16 | archive-url = https://web.archive.org/web/20160216122731/http://httpd.apache.org/docs/2.4/howto/public_html.html | url-status = live }}</ref>
* Generic expression parser<ref>{{ cite web | url = https://httpd.apache.org/docs/2.4/expr.html| title = Expressions in Apache HTTP Server }}</ref> * Generic expression parser<ref>{{cite web| url = https://httpd.apache.org/docs/2.4/expr.html| title = Expressions in Apache HTTP Server| publisher = Apache.org| access-date = 2016-02-19| archive-date = 2016-02-29| archive-url = https://web.archive.org/web/20160229120307/http://httpd.apache.org/docs/2.4/expr.html| url-status = live}}</ref>
* Real-time status views<ref>{{ cite web | url = https://httpd.apache.org/docs/2.4/mod/mod_status.html | title = mod_status }}</ref> * Real-time status views<ref>{{cite web | url = https://httpd.apache.org/docs/2.4/mod/mod_status.html | title = mod_status | publisher = Apache.org | access-date = 2016-02-19 | archive-date = 2016-02-13 | archive-url = https://web.archive.org/web/20160213154107/http://httpd.apache.org/docs/2.4/mod/mod_status.html | url-status = live }}</ref>
* ] support<ref>{{ cite web | url = http://httpd.apache.org/docs/2.4/mod/mod_xml2enc.html | title = mod_xml2enc }}</ref> * ] support (by a separate module)<ref>{{cite web | url= https://httpd.apache.org/mod_ftp/mod/mod_ftp.html | title= Apache Module: mod_ftp | publisher= Apache.org | access-date= 2017-07-08 | archive-date= 2017-07-10 | archive-url= https://web.archive.org/web/20170710072314/http://httpd.apache.org/mod_ftp/mod/mod_ftp.html | url-status= live }}</ref>


==Performance== ==Performance==
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 ], relative to simply handling more requests, thus ensuring consistent and reliable processing of requests within reasonable time-frames. Instead of implementing a single architecture, Apache provides a variety of MultiProcessing Modules (MPMs), which allow it to run in either a ]-based mode, a hybrid (process and ]) 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. Where compromises in performance must be made, Apache is designed to reduce ] and increase ] relative to simply handling more requests, thus ensuring consistent and reliable processing of requests within reasonable time-frames.{{clarify |date=August 2018}}<!--It isn't clear to a non-specialist like me why increasing throughput is different from handling more requests or why reducing latency (which sounds like increasing speed) wouldn't enable you to handle more requests. It also isn't clear how either of these represent a compromise in performance. Also, is Apache doing something that decreases latency and increases throughput _relative_ to what you would get by handling more requests, or is it decreasing latency and increasing throughput _rather_ than handling more requests? If the latter, "rather than" should replace "relative to" in that sentence.-->


For delivery of static pages, Apache 2.2 series was considered significantly slower than ] and ].<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!}}</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 asynchronous event-based loop.<ref>{{cite web|url=http://httpd.apache.org/docs/2.2/mod/worker.html|title=worker - Apache HTTP Server Version 2.2|work=apache.org}}</ref> 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 ] and other independent sources.<ref></ref><ref>{{cite web|url=http://www.slideshare.net/bryan_call/choosing-a-proxy-server-apachecon-2014|title=Picking a Proxy Server}}</ref><ref>{{cite web|url=http://blog.matsumoto-r.jp/?p=1812|title=Throughput evaluation of Apache 2.4.1}}</ref> However, some independent, but significantly outdated, benchmarks show that it still is 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}}</ref> For delivering static pages, Apache 2.2 series was considered significantly slower than ] and ].<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 ] ].<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 ] 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>


==Licensing== ==Licensing==
The Apache HTTP Server ] was ] to the ] (from the previous 1.1 license) in January 2004,<ref>{{Cite web|url=https://www.apache.org/licenses/LICENSE-2.0.html|title=Apache License, Version 2.0|publisher=The Apache Software Foundation|date=January 2004|accessdate=2013-05-21}}</ref> and Apache HTTP Server 1.3.31 and 2.0.49 were the first ] using the new license.<ref>{{Cite newsgroup|url=|title=FYI: Apache HTTP Server 2.0.49 Released|last=Burton|first=Richard Antony|newsgroup=alt.apache.configuration|accessdate=2013-05-23}}</ref> The Apache HTTP Server ] was ] to the ] (from the previous 1.1 license) in January 2004,<ref>{{Cite web|url=https://www.apache.org/licenses/LICENSE-2.0.html|title=Apache License, Version 2.0|publisher=The Apache Software Foundation|date=January 2004|access-date=2013-05-21|archive-date=2013-05-18|archive-url=https://web.archive.org/web/20130518072534/http://www.apache.org/licenses/LICENSE-2.0.html|url-status=live}}</ref> and Apache HTTP Server 1.3.31 and 2.0.49 were the first ] using the new license.<ref>{{Cite newsgroup|title=FYI: Apache HTTP Server 2.0.49 Released|last=Burton|first=Richard Antony|newsgroup=alt.apache.configuration|url=https://groups.google.com/d/msg/alt.apache.configuration/042hhGcLWUs/rDJdt5b927cJ|access-date=2018-02-16}}</ref>


The ] 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.<ref>{{Cite mailing list|url=http://marc.info/?l=openbsd-misc&m=107714762916291|title=The new apache license|last=de Raadt|first=Theo|authorlink=Theo de Raadt|mailinglist=openbsd-misc|date=18 February 2004|accessdate=2013-05-21}}</ref><ref>{{Cite web|url=http://www.openbsd.org/policy.html|title=Copyright Policy|publisher=OpenBSD|accessdate=2013-05-12}}</ref><ref>{{cite web|url=http://ports.su/www/apache-httpd-openbsd |title=apache-httpd-openbsd-1.3.20140502p2 – OpenBSD improved and secured version of Apache 1.3 |website=OpenBSD ports |date=|accessdate=2014-12-28}}</ref> They initially replaced it with ], and soon after made their own replacement, OpenBSD Httpd, based on the relayd project.<ref>{{cite web|url=http://www.openbsd.org/faq/upgrade52.html#nginx|title=OpenBSD Upgrade Guide: 5.1 to 5.2|work=openbsd.org}}</ref><ref>{{cite web|url=http://undeadly.org/cgi?action=article&sid=20140314080734|date=2014-03-14|title= Heads Up: Apache Removed from Base |website=]|editor=jj}}</ref><ref>{{cite web|url=http://www.openbsd.org/faq/upgrade56.html#ToPorts|title=OpenBSD Upgrade Guide: 5.5 to 5.6|work=openbsd.org}}</ref> The ] project did not like the change and continued the use of pre-2.0 Apache versions, effectively ] Apache 1.3.x for its purposes.<ref>{{Cite mailing list|url=http://marc.info/?l=openbsd-misc&m=107714762916291|title=The new apache license|last=de Raadt|first=Theo|author-link=Theo de Raadt|mailing-list=openbsd-misc|date=18 February 2004|access-date=2013-05-21}}</ref><ref>{{Cite web|url=http://www.openbsd.org/policy.html|title=Copyright Policy|publisher=OpenBSD|access-date=2013-05-12|archive-date=2017-11-13|archive-url=https://web.archive.org/web/20171113040622/http://www.openbsd.org/policy.html|url-status=live}}</ref><ref>{{cite web |url=http://ports.su/www/apache-httpd-openbsd |title=apache-httpd-openbsd-1.3.20140502p2 – OpenBSD improved and secured version of Apache 1.3 |website=OpenBSD ports |access-date=2014-12-28 |archive-date=2015-03-02 |archive-url=https://web.archive.org/web/20150302031504/http://ports.su/www/apache-httpd-openbsd |url-status=live }}</ref> They initially replaced it with ], and soon after made their own replacement, OpenBSD Httpd, based on the Relayd project.<ref>{{cite news |last1=Marvin |first1=Rob |title=Inside OpenBSD's new httpd Web server |url=https://sdtimes.com/httpd/inside-openbsds-new-httpd-web-server/ |access-date=12 October 2019 |work=SD Times |date=25 March 2015 |archive-date=12 October 2019 |archive-url=https://web.archive.org/web/20191012215958/https://sdtimes.com/httpd/inside-openbsds-new-httpd-web-server/ |url-status=live }}</ref><ref>{{cite web|url=http://www.openbsd.org/faq/upgrade52.html#nginx|title=OpenBSD Upgrade Guide: 5.1 to 5.2|work=openbsd.org|access-date=2014-03-13|archive-date=2017-12-22|archive-url=https://web.archive.org/web/20171222055544/http://www.openbsd.org/faq/upgrade52.html#nginx|url-status=live}}</ref><ref>{{cite web|url=http://undeadly.org/cgi?action=article&sid=20140314080734|date=2014-03-14|title=Heads Up: Apache Removed from Base|website=]|editor=jj|access-date=2014-12-29|archive-date=2014-10-18|archive-url=https://web.archive.org/web/20141018182803/http://www.undeadly.org/cgi?action=article&sid=20140314080734|url-status=live}}</ref><ref>{{cite web|url=http://www.openbsd.org/faq/upgrade56.html#ToPorts|title=OpenBSD Upgrade Guide: 5.5 to 5.6|work=openbsd.org|access-date=2014-12-29|archive-date=2014-12-22|archive-url=https://web.archive.org/web/20141222025858/http://www.openbsd.org/faq/upgrade56.html#ToPorts|url-status=live}}</ref>


===Versions=== ===Versions===


Version 1.1: 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. 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, only in their documentation.


Version 2.0: Version 2.0:
Line 99: Line 114:
==Development== ==Development==
{|class="wikitable" style="float: right; margin-left: 1em;" {|class="wikitable" style="float: right; margin-left: 1em;"
|+Versions of Apache HTTP Server
|- |-
!Version !scope="col"|Version
!Initial release !scope="col"|Initial release
!Latest release !scope="col"|Latest release
|- |-
|{{Version|o|1.3}} !scope="row" {{Version|o|1.3}}
|1998-06-06<ref>{{Cite web|url=http://marc.info/?l=apache-httpd-announce&m=90221040625561&w=2|title=Announcement: Apache 1.3.0 Released !|date=1998-06-06|accessdate=2015-01-06}}</ref> |1998-06-06<ref>{{Cite web|url=http://marc.info/?l=apache-httpd-announce&m=90221040625561&w=2|title=Announcement: Apache 1.3.0 Released !|date=1998-06-06|access-date=2015-01-06|archive-date=2018-12-11|archive-url=https://web.archive.org/web/20181211203756/https://marc.info/?l=apache-httpd-announce&m=90221040625561&w=2|url-status=live}}</ref>
|2010-02-03 (1.3.42)<ref>{{cite web|url=http://mail-archives.apache.org/mod_mbox/httpd-announce/201002.mbox/%3C20100203000334.GA19021%40infiltrator.stdlib.net%3E|title=Apache HTTP Server 1.3.42 released (final release of 1.3.x)|work=apache.org}}</ref> |2010-02-03 (1.3.42)<ref>{{cite web|url=http://mail-archives.apache.org/mod_mbox/httpd-announce/201002.mbox/%3C20100203000334.GA19021%40infiltrator.stdlib.net%3E|title=Apache HTTP Server 1.3.42 released (final release of 1.3.x)|work=apache.org|access-date=2015-01-06|archive-date=2015-03-11|archive-url=https://web.archive.org/web/20150311184801/http://mail-archives.apache.org/mod_mbox/httpd-announce/201002.mbox/%3C20100203000334.GA19021@infiltrator.stdlib.net%3E|url-status=live}}</ref>
|- |-
|{{Version|o|2.0}} !scope="row" {{Version|o|2.0}}
|2002-04-06<ref>{{Cite web|url=http://marc.info/?l=apache-httpd-announce&m=101810732100356&w=2|title=Official Release: Apache 2.0.35 is now GA|date=2002-04-06|accessdate=2015-01-06}}</ref> |2002-04-06<ref>{{Cite web|url=http://marc.info/?l=apache-httpd-announce&m=101810732100356&w=2|title=Official Release: Apache 2.0.35 is now GA|date=2002-04-06|access-date=2015-01-06|archive-date=2018-12-12|archive-url=https://web.archive.org/web/20181212084822/https://marc.info/?l=apache-httpd-announce&m=101810732100356&w=2|url-status=live}}</ref>
|2013-07-10 (2.0.65)<ref>{{cite web|url=http://mail-archives.apache.org/mod_mbox/httpd-announce/201307.mbox/%3C20130710124920.2b8793ed.wrowe%40rowe-clan.net%3E|title= Apache HTTP Server 2.0.65 Released|work=apache.org}}</ref> |2013-07-10 (2.0.65)<ref>{{cite web|url=http://mail-archives.apache.org/mod_mbox/httpd-announce/201307.mbox/%3C20130710124920.2b8793ed.wrowe%40rowe-clan.net%3E|title= Apache HTTP Server 2.0.65 Released|work=apache.org|access-date=2015-01-06|archive-date=2015-07-28|archive-url=https://web.archive.org/web/20150728000646/http://mail-archives.apache.org/mod_mbox/httpd-announce/201307.mbox/%3C20130710124920.2b8793ed.wrowe@rowe-clan.net%3E|url-status=live}}</ref>
|- |-
|{{Version|co|2.2}} !scope="row" {{Version|o|2.2}}
|2005-12-01<ref>{{Cite web|url=http://marc.info/?l=apache-httpd-announce&m=113347470201565&w=2|title=Apache HTTP Server 2.2.0 Released|date=2005-12-01|accessdate=2015-01-06}}</ref> |2005-12-01<ref>{{Cite web|url=http://marc.info/?l=apache-httpd-announce&m=113347470201565&w=2|title=Apache HTTP Server 2.2.0 Released|date=2005-12-01|access-date=2015-01-06|archive-date=2018-12-12|archive-url=https://web.archive.org/web/20181212145848/https://marc.info/?l=apache-httpd-announce&m=113347470201565&w=2|url-status=live}}</ref>
|2017-01-13 (2.2.32)<ref>{{cite web|url=http://www.apache.org/dist/httpd/Announcement2.2.html|title= Apache HTTP Server 2.2.32 Released|work=apache.org}}</ref> |2017-07-11 (2.2.34)<ref>{{cite web|url=https://mail-archives.apache.org/mod_mbox/www-announce/201707.mbox/%3CCACsi2512a0dKZm5SEb9GyNH6nMfs1+swpxyui3c+UZUwvi3vvg@mail.gmail.com%3E|title= Apache HTTP Server 2.2.34 Released|work=apache.org|access-date=2019-04-03|archive-date=2020-08-21|archive-url=https://web.archive.org/web/20200821113300/https://mail-archives.apache.org/mod_mbox/www-announce/201707.mbox/%3CCACsi2512a0dKZm5SEb9GyNH6nMfs1+swpxyui3c+UZUwvi3vvg@mail.gmail.com%3E|url-status=live}}</ref>
|- |-
|{{Version|c|2.4}} !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= Apache HTTP Server 2.4.1 Released|date=2012-02-21|accessdate=2015-07-17}}</ref> |2012-02-21<ref>{{Cite web|url=http://marc.info/?l=apache-httpd-announce&m=132983471818384&w=2|title= 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>
|2016-12-20 (2.4.25)<ref>{{cite web|url=http://www.apache.org/dist/httpd/Announcement2.4.html|title=Apache HTTP Server 2.4.25 Released|work=apache.org}}</ref> |2024-07-17 (2.4.62)<ref>{{cite web |title=Apache HTTP Server 2.4.62 Released |url=https://www.apache.org/dist/httpd/Announcement2.4.html |archive-url= |archive-date= |access-date=2017-10-25 |work=apache.org}}</ref>
|- |-
|colspan="3"|<small>{{Version|l|show=011100}}</small> |colspan="3"|{{Version|l|show=010100}}
|} |}
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.<ref>{{cite web|url=http://httpd.apache.org/ABOUT_APACHE.html|title=About the Apache HTTP Server Project - The Apache HTTP Server Project|author=Documentation Group|work=apache.org}}</ref><ref></ref><ref>{{cite web|url=http://docs.fedoraproject.org/en-US/Fedora/13/html/Managing_Confined_Services/chap-Managing_Confined_Services-The_Apache_HTTP_Server.html|title=Chapter 4. The Apache HTTP Server|work=fedoraproject.org}}</ref> 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 ]. In addition, hundreds of users have contributed ideas, code, and documentation to the project.<ref>{{cite web|url=https://httpd.apache.org/ABOUT_APACHE.html|title=About the Apache HTTP Server Project - The Apache HTTP Server Project|author=Documentation Group|work=apache.org|access-date=2021-05-12|archive-date=2008-06-07|archive-url=https://web.archive.org/web/20080607122013/http://httpd.apache.org/ABOUT_APACHE.html|url-status=live}}</ref><ref>{{cite web| url = http://www.ohloh.net/p/apache| title = The Apache HTTP Server Open Source Project on Ohloh. (n.d.). Ohloh, the open source network. Retrieved November 12, 2012| access-date = February 8, 2012| archive-date = March 9, 2012| archive-url = https://web.archive.org/web/20120309003935/https://www.ohloh.net/p/apache| url-status = live}}</ref><ref>{{cite web|url=http://docs.fedoraproject.org/en-US/Fedora/13/html/Managing_Confined_Services/chap-Managing_Confined_Services-The_Apache_HTTP_Server.html|title=Chapter 4. The Apache HTTP Server|work=fedoraproject.org|access-date=2012-12-03|archive-date=2012-11-25|archive-url=https://web.archive.org/web/20121125111059/http://docs.fedoraproject.org/en-US/Fedora/13/html/Managing_Confined_Services/chap-Managing_Confined_Services-The_Apache_HTTP_Server.html|url-status=dead}}</ref>

Apache 2.4 dropped support for ], ], ], ], and ] platforms.<ref name=older>{{cite web |url=https://httpd.apache.org/docs/2.4/upgrading.html |title=Upgrading to 2.4 from 2.2 |quote=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. |access-date=2021-05-12 |archive-date=2021-05-10 |archive-url=https://web.archive.org/web/20210510141206/https://httpd.apache.org/docs/2.4/upgrading.html |url-status=live }}</ref>


==Security==
Apache 2.4 dropped support for ], ] and even older platforms.<ref>{{cite web |url=http://httpd.apache.org/docs/2.4/upgrading.html |title=Upgrading to 2.4 from 2.2 |quote=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.}}</ref>
{{Disputed section|date=January 2021}}
Apache, like other server software, can be hacked and exploited. The main Apache attack tool is ], which exploits a bug in Apache software.<ref>{{cite web|url=https://isc.sans.edu/diary/Apache+HTTP+DoS+tool+mitigation/6613|title=Apache HTTP DoS tool mitigation|last=Zdrnja|first=Bojan|publisher=]|date=21 June 2009|access-date=12 November 2021|archive-date=12 November 2021|archive-url=https://web.archive.org/web/20211112130802/https://isc.sans.edu/diary/Apache+HTTP+DoS+tool+mitigation/6613|url-status=live}}</ref> It creates many sockets and keeps each of them alive and busy by sending several bytes (known as "keep-alive headers") to let the server know that the computer is still connected and not experiencing network problems. The Apache developers have addressed Slowloris with several modules to limit the damage caused; the Apache modules mod_limitipconn, ], mod_evasive, ], mod_noloris, and mod_antiloris have all been suggested as means of reducing the likelihood of a successful Slowloris attack.<ref name="ha.ckers.org">{{cite web |url=http://ha.ckers.org/slowloris |title=Slowloris HTTP DoS |access-date=2009-06-26 |url-status=bot: unknown |archive-url=https://web.archive.org/web/20150426090206/http://ha.ckers.org/slowloris |archive-date=26 April 2015 |df=dmy-all }}</ref><ref>{{cite web |url=http://bahumbug.wordpress.com/2009/07/01/mod_noloris-defending-against-dos/ |title=mod_noloris: defending against DoS |date=July 2009 |publisher=niq's soapbox |access-date=7 January 2012 |archive-date=8 October 2011 |archive-url=https://web.archive.org/web/20111008151654/http://bahumbug.wordpress.com/2009/07/01/mod_noloris-defending-against-dos/ |url-status=live }}</ref> Since Apache 2.2.15, Apache ships the module mod_reqtimeout as the official solution supported by the developers.<ref>{{cite web |url=https://httpd.apache.org/docs/2.4/mod/mod_reqtimeout.html |title=mod_reqtimeout |publisher=Apache.org |access-date=2013-07-03 |archive-date=2013-07-03 |archive-url=https://web.archive.org/web/20130703041319/http://httpd.apache.org/docs/2.4/mod/mod_reqtimeout.html |url-status=live }}</ref>


==See also== ==See also==
{{Portal|Free software}} {{Portal|Free and open-source software}}
* ] * ]
* ] * ]
Line 134: Line 154:
* ] * ]
* ] * ]
* ]
* ] * ]
*]
* ] * ]
* ] * ]
* ] - another web server developed by the Apache Software Foundation


==References== ==References==
Line 142: Line 165:


==External links== ==External links==
{{Wikibooks|Apache}}
* {{Official website}} * {{Official website}}


{{Apache}} {{Apache Software Foundation}}
{{Web server software}} {{Web server software}}
{{Web interfaces}} {{Web interfaces}}
Line 151: Line 175:


] ]
]
] ]
] ]

Latest revision as of 08:36, 12 December 2024

Open-source web server software
This article may be too technical for most readers to understand. Please help improve it to make it understandable to non-experts, without removing the technical details. (September 2010) (Learn how and when to remove this message)
Apache HTTP Server
Original author(s)Robert McCool
Developer(s)Apache Software Foundation
Initial release1995; 30 years ago (1995)
Stable release2.4.62 Edit this on Wikidata / July 17, 2024; 5 months ago (2024-07-17)
Repository
Written inC
Operating systemUnix-like, Microsoft Windows, OpenVMS
TypeWeb server
LicenseApache-2.0
Websitehttpd.apache.org Edit this at Wikidata

The Apache HTTP Server (/əˈpætʃi/ ə-PATCH-ee) is a free and open-source cross-platform web server, released under the terms of 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, but current versions also run on Microsoft Windows, OpenVMS, and a wide variety of Unix-like systems. Past versions also ran on NetWare, OS/2 and other operating systems, including ports to mainframes.

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. In 2009, it became the first web server software to serve more than 100 million websites.

As of March 2022, Netcraft estimated that Apache served 23.04% of the million busiest websites, while Nginx served 22.01%; Cloudflare at 19.53% and Microsoft Internet Information Services at 5.78% rounded out the top four. For some of Netcraft's other stats, Nginx is ahead of Apache. According to W3Techs' review of all web sites, in June 2022 Apache was ranked second at 31.4% and Nginx first at 33.6%, with Cloudflare Server third at 21.6%.

Name

According to The Apache Software Foundation, its name was chosen "from respect for the various Native American nations collectively referred to as Apache, well-known for their superior skills in warfare strategy and their inexhaustible endurance". 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. But it conceded that the name "also makes a cute pun on 'a patchy web server'—a server made from a series of 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."

But in an April 2000 interview, Behlendorf asserted that the origins of Apache were not a pun, stating:

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 connoted: "Take no prisoners. Be kind of aggressive and kick some ass."

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.

When Apache is running under Unix, its process name is httpd, which is short for "HTTP daemon".

Feature overview

Apache supports a variety of features, many implemented as compiled modules which extend the core functionality. These can range from authentication schemes to supporting server-side programming languages such as 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 websites. For example, one computer with one Apache installation could simultaneously serve example.com, example.org, test47.test-server.example.edu, etc.

Apache features configurable error messages, DBMS-based authentication databases, content negotiation and supports several graphical user interfaces (GUIs).

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.

A more detailed list of features is provided below:

Performance

Instead of implementing a single architecture, Apache provides a variety of MultiProcessing Modules (MPMs), which allow it to run in either a process-based mode, a hybrid (process and 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. Where compromises in performance must be made, Apache is designed 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 delivering 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 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. However, some independent but significantly outdated benchmarks show that it is still half as fast as nginx, e.g.

Licensing

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.

Versions

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, 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.

Development

Versions of Apache HTTP Server
Version Initial release Latest release
Old version, no longer maintained: 1.3 1998-06-06 2010-02-03 (1.3.42)
Old version, no longer maintained: 2.0 2002-04-06 2013-07-10 (2.0.65)
Old version, no longer maintained: 2.2 2005-12-01 2017-07-11 (2.2.34)
Current stable version: 2.4 2012-02-21 2024-07-17 (2.4.62)
Legend:Old versionOld version, still maintainedLatest versionLatest preview versionFuture release

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.

Apache 2.4 dropped support for BeOS, TPF, A/UX, NeXT, and Tandem platforms.

Security

This section's factual accuracy is disputed. Relevant discussion may be found on the talk page. Please help to ensure that disputed statements are reliably sourced. (January 2021) (Learn how and when to remove this message)

Apache, like other server software, can be hacked and exploited. The main Apache attack tool is Slowloris, which exploits a bug in Apache software. It creates many sockets and keeps each of them alive and busy by sending several bytes (known as "keep-alive headers") to let the server know that the computer is still connected and not experiencing network problems. The Apache developers have addressed Slowloris with several modules to limit the damage caused; the Apache modules mod_limitipconn, mod_qos, mod_evasive, mod security, mod_noloris, and mod_antiloris have all been suggested as means of reducing the likelihood of a successful Slowloris attack. Since Apache 2.2.15, Apache ships the module mod_reqtimeout as the official solution supported by the developers.

See also

References

  1. "About the Apache HTTP Server Project". Apache Software Foundation. Archived from the original on 7 June 2008. Retrieved 2008-06-25.
  2. "[ANNOUNCEMENT] Apache HTTP Server 2.4.62 Released". 17 July 2024. Retrieved 17 July 2024.
  3. "Apache Software Foundation Index: Projects by Programming Language Index". Archived from the original on 2016-03-02. Retrieved 2016-02-27.
  4. "Compiling and Installing". httpd.apache.org. The Apache Software Foundation. Archived from the original on 7 May 2016. Retrieved 9 May 2016.
  5. "OS/Linux Distributions using Apache". secure1.securityspace.com. Archived from the original on 2018-09-18. Retrieved 2018-09-17.
  6. "Platform Specific Notes - Apache HTTP Server Version 2.4". httpd.apache.org. Archived from the original on 2019-01-22. Retrieved 2019-01-21.
  7. "Secure Web Server". vmssoftware.com. Archived from the original on 2020-10-22. Retrieved 2020-10-20.
  8. ^ "Upgrading to 2.4 from 2.2". Archived from the original on 2021-05-10. Retrieved 2021-05-12. 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.
  9. "The Apache EBCDIC Port - Apache HTTP Server Version 2.4". httpd.apache.org. Archived from the original on 2019-02-27. Retrieved 2019-08-16.
  10. "About the Apache HTTP Server Project - The Apache HTTP Server Project". httpd.apache.org. Retrieved 2024-02-08.
  11. Netcraft Market Share Archived 2010-05-20 at the Wayback Machine for Top Servers Across All Domains August 1995 - today (monthly updated)
  12. "February 2009 Web Server Survey". Netcraft. 18 February 2009. Archived from the original on 26 February 2009. Retrieved 2009-03-29.
  13. "March 2022 Web Server Survey". Netcraft News. 29 March 2022. Archived from the original on 2022-05-28. Retrieved 2022-06-18.
  14. "Usage Statistics of Web Servers". w3techs.com. Archived from the original on 2023-07-25. Retrieved 2022-06-18.
  15. "Apache Foundation". www.apache.org. Archived from the original on 13 December 2021. Retrieved 22 August 2018.
  16. ""Trillions and Trillions Served" documentary feature on The Apache Software Foundation". TheApacheFoundation / Youtube. 2020. Archived from the original on 2021-11-22.
  17. "A Foundation of Trust: Building a Blockchain Future : Brian Behlendorf". Long Now Foundation / YouTube. 2020-02-10. Archived from the original on 2021-11-22.
  18. "Information on the Apache HTTP Server Project". 1997-04-15. Archived from the original on April 15, 1997.
  19. "Apache Server Frequently Asked Questions". Archived from the original on 1997-01-06. Retrieved 15 January 2017.
  20. McMillan, Robert (15 April 2000). "Apache Power". Linux Magazine. Archived from the original on 28 January 2019.
  21. Claburn, Thomas (2023-01-11). "Native Americans ask Apache foundation to change name". The Register. Archived from the original on 2023-01-12. Retrieved 2023-01-12.
  22. Purdy, Kevin (2023-01-12). "Indigenous tech group asks Apache Foundation to change its name". Ars Technica. Archived from the original on 2023-01-12. Retrieved 2023-01-12.
  23. "Apache Docs". httpd.apache.org. Archived from the original on 5 September 2018. Retrieved 22 August 2018.
  24. "Apache Web Server". webopedia.com. 23 March 1998. Archived from the original on 12 May 2021. Retrieved 12 May 2021.
  25. "Apache HTTP Server Tutorial: .htaccess files". Apache.org. Archived from the original on 2016-02-25. Retrieved 2016-02-19.
  26. "mod_proxy". Apache.org. Archived from the original on 2018-07-29. Retrieved 2016-02-19.
  27. "mod_proxy_balancer". Apache.org. Archived from the original on 2016-02-13. Retrieved 2016-02-19.
  28. "Balancer Manager". Apache.org. Archived from the original on 2016-03-04. Retrieved 2016-02-19.
  29. "Authentication and Authorization". Apache.org. Archived from the original on 2018-01-31. Retrieved 2016-02-19.
  30. "mod_rewrite". Apache.org. Archived from the original on 2016-02-13. Retrieved 2016-02-19.
  31. "mod_headers". Apache.org. Archived from the original on 2016-02-21. Retrieved 2016-02-19.
  32. "mod_sed". Apache.org. Archived from the original on 2016-03-04. Retrieved 2016-02-19.
  33. "mod_substitute". Apache.org. Archived from the original on 2016-03-04. Retrieved 2016-02-19.
  34. "Apache httpd Tutorial: Introduction to Server Side Includes". Apache.org. Archived from the original on 2016-02-18. Retrieved 2016-02-19.
  35. "mod_usertrack". Apache.org. Archived from the original on 2021-05-12. Retrieved 2021-05-12.
  36. "Apache Tutorial: Dynamic Content with CGI". Apache.org. Archived from the original on 2021-11-15. Retrieved 2016-02-19.
  37. "Per-user web directories". Apache.org. Archived from the original on 2016-02-16. Retrieved 2016-02-19.
  38. "Expressions in Apache HTTP Server". Apache.org. Archived from the original on 2016-02-29. Retrieved 2016-02-19.
  39. "mod_status". Apache.org. Archived from the original on 2016-02-13. Retrieved 2016-02-19.
  40. "Apache Module: mod_ftp". Apache.org. Archived from the original on 2017-07-10. Retrieved 2017-07-08.
  41. "Serving static files: a comparison between Apache, Nginx, Varnish and G-WAN". Spoot!. 14 March 2011. Archived from the original on 24 April 2014. Retrieved 23 April 2014.
  42. "worker - Apache HTTP Server Version 2.2". apache.org. Archived from the original on 2021-05-10. Retrieved 2021-05-12.
  43. "Apache httpd 2.4" (PDF). Archived (PDF) from the original on 2012-01-27. Retrieved 2012-02-08.
  44. "Picking a Proxy Server". 14 April 2014. Archived from the original on 3 March 2016. Retrieved 19 February 2016.
  45. "Throughput evaluation of Apache 2.4.1". 22 February 2012. Archived from the original on 2016-03-02. Retrieved 2016-02-19.
  46. "Performance of Apache 2.4 with the event MPM compared to Nginx". eschrade.com. 3 January 2014. Archived from the original on 13 March 2014. Retrieved 13 March 2014.
  47. "Apache License, Version 2.0". The Apache Software Foundation. January 2004. Archived from the original on 2013-05-18. Retrieved 2013-05-21.
  48. Burton, Richard Antony. "FYI: Apache HTTP Server 2.0.49 Released". Newsgroupalt.apache.configuration. Retrieved 2018-02-16.
  49. de Raadt, Theo (18 February 2004). "The new apache license". openbsd-misc (Mailing list). Retrieved 2013-05-21.
  50. "Copyright Policy". OpenBSD. Archived from the original on 2017-11-13. Retrieved 2013-05-12.
  51. "apache-httpd-openbsd-1.3.20140502p2 – OpenBSD improved and secured version of Apache 1.3". OpenBSD ports. Archived from the original on 2015-03-02. Retrieved 2014-12-28.
  52. Marvin, Rob (25 March 2015). "Inside OpenBSD's new httpd Web server". SD Times. Archived from the original on 12 October 2019. Retrieved 12 October 2019.
  53. "OpenBSD Upgrade Guide: 5.1 to 5.2". openbsd.org. Archived from the original on 2017-12-22. Retrieved 2014-03-13.
  54. jj, ed. (2014-03-14). "Heads Up: Apache Removed from Base". OpenBSD Journal. Archived from the original on 2014-10-18. Retrieved 2014-12-29.
  55. "OpenBSD Upgrade Guide: 5.5 to 5.6". openbsd.org. Archived from the original on 2014-12-22. Retrieved 2014-12-29.
  56. "Announcement: Apache 1.3.0 Released !". 1998-06-06. Archived from the original on 2018-12-11. Retrieved 2015-01-06.
  57. "Apache HTTP Server 1.3.42 released (final release of 1.3.x)". apache.org. Archived from the original on 2015-03-11. Retrieved 2015-01-06.
  58. "Official Release: Apache 2.0.35 is now GA". 2002-04-06. Archived from the original on 2018-12-12. Retrieved 2015-01-06.
  59. "[Announcement] Apache HTTP Server 2.0.65 Released". apache.org. Archived from the original on 2015-07-28. Retrieved 2015-01-06.
  60. "Apache HTTP Server 2.2.0 Released". 2005-12-01. Archived from the original on 2018-12-12. Retrieved 2015-01-06.
  61. "[Announce] Apache HTTP Server 2.2.34 Released". apache.org. Archived from the original on 2020-08-21. Retrieved 2019-04-03.
  62. "[ANNOUNCEMENT] Apache HTTP Server 2.4.1 Released". 2012-02-21. Archived from the original on 2021-02-12. Retrieved 2015-07-17.
  63. "Apache HTTP Server 2.4.62 Released". apache.org. Retrieved 2017-10-25.
  64. Documentation Group. "About the Apache HTTP Server Project - The Apache HTTP Server Project". apache.org. Archived from the original on 2008-06-07. Retrieved 2021-05-12.
  65. "The Apache HTTP Server Open Source Project on Ohloh. (n.d.). Ohloh, the open source network. Retrieved November 12, 2012". Archived from the original on March 9, 2012. Retrieved February 8, 2012.
  66. "Chapter 4. The Apache HTTP Server". fedoraproject.org. Archived from the original on 2012-11-25. Retrieved 2012-12-03.
  67. Zdrnja, Bojan (21 June 2009). "Apache HTTP DoS tool mitigation". SANS Institute. Archived from the original on 12 November 2021. Retrieved 12 November 2021.
  68. "Slowloris HTTP DoS". Archived from the original on 26 April 2015. Retrieved 26 June 2009.{{cite web}}: CS1 maint: bot: original URL status unknown (link)
  69. "mod_noloris: defending against DoS". niq's soapbox. July 2009. Archived from the original on 8 October 2011. Retrieved 7 January 2012.
  70. "mod_reqtimeout". Apache.org. Archived from the original on 2013-07-03. Retrieved 2013-07-03.

External links

The Apache Software Foundation
Top-level
projects
Commons
Incubator
Other projects
Attic
Licenses
Web server software
Comparisons
Most popular
Other
Retired
Web interfaces
Server-side
Protocols
Server APIs
Apache modules
Topics
Client-side
Browser APIs
Web APIs
WHATWG
W3C
Khronos
Others
Topics
Related topics
Categories: