Apache HTTP Server
- العربية
- Azərbaycanca
- Български
- Bosanski
- Català
- Čeština
- Dansk
- Deutsch
- Eesti
- Ελληνικά
- Español
- Esperanto
- Euskara
- فارسی
- Français
- Galego
- 한국어
- Hausa
- हिन्दी
- Hrvatski
- Bahasa Indonesia
- Interlingua
- Italiano
- עברית
- ქართული
- Қазақша
- Kurdî
- Кыргызча
- Latviešu
- Lietuvių
- Lombard
- Magyar
- മലയാളം
- Bahasa Melayu
- Nederlands
- नेपाली
- 日本語
- Norsk bokmål
- Norsk nynorsk
- Oʻzbekcha / ўзбекча
- Polski
- Português
- Română
- Русский
- Shqip
- Simple English
- Slovenčina
- Slovenščina
- کوردی
- Српски / srpski
- Srpskohrvatski / српскохрватски
- Sunda
- Suomi
- Svenska
- தமிழ்
- Taqbaylit
- తెలుగు
- ไทย
- Türkçe
- Українська
- Vèneto
- Tiếng Việt
- Winaray
- 吴语
- 粵語
- 中文
Apache HTTP Server | |
---|---|
Original author | Robert McCool |
Developer | Apache Software Foundation |
Initial release | 1995; 30 years ago (1995)[1] |
Stable release | |
Repository | |
Written in | C [3] |
Operating system | Unix-like, Microsoft Windows,[4] OpenVMS |
Type | Web server |
License | Apache-2.0 |
Website | httpd |
The Apache HTTP Server 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,[5] but current versions also run on Microsoft Windows,[6] OpenVMS,[7] and a wide variety of Unix-like systems. Past versions also ran on NetWare, OS/2 and other operating systems,[8] including ports to mainframes.[9]
Originally based on the NCSA HTTPd server, development of Apache began in early 1995 after work on the NCSA code stalled.[10] Apache played a key role in the initial growth of the World Wide Web,[11] 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.[12]
As of March 2025[update] , 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%.[13] 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%.[14]
Name
[edit ]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".[15] 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.[16] [17] But it conceded that the name "also makes a cute pun on 'a patchy web server'—a server made from a series of patches".
Other sources also claim that that the name originated as a pun on 'patchy', 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."[18] [19] This documentation did not mention Native American tribes in the context of the name.
But in an April 2000 interview, Behlendorf asserted that the origins of Apache were not a pun, stating:[20]
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.[21] [22]
When Apache is running under Unix, its process name is httpd
, which is short for "HTTP daemon".[23]
Feature overview
[edit ]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.[24]
A more detailed list of features is provided below:
- Loadable Dynamic Modules
- Multiple Request Processing modes (MPMs) including Event-based/Async, Threaded and Prefork.
- Highly scalable (easily handles more than 10,000 simultaneous connections)
- Handling of static files, index files, auto-indexing and content negotiation
- .htaccess per-directory configuration support[25]
- Reverse proxy with caching[26]
- Load balancing [27] with in-band health checks
- Multiple load balancing mechanisms
- Fault tolerance and Failover with automatic recovery
- WebSocket, FastCGI, SCGI, AJP and uWSGI support with caching
- Dynamic configuration[28]
- TLS/SSL with SNI and OCSP stapling support, via OpenSSL or wolfSSL.
- Name- and IP address-based virtual servers
- IPv6-compatible
- HTTP/2 support
- Fine-grained authentication and authorization access control[29]
- gzip compression and decompression
- URL rewriting[30]
- Headers[31] and content[32] [33] rewriting
- Custom logging with rotation
- Concurrent connection limiting
- Request processing rate limiting
- Bandwidth throttling
- Server Side Includes [34]
- IP address-based geolocation
- User and Session tracking[35]
- WebDAV
- Embedded Perl, PHP and Lua scripting
- CGI support[36]
public_html
per-user web-pages[37]- Generic expression parser[38]
- Real-time status views[39]
- FTP support (by a separate module)[40]
Performance
[edit ]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.
For delivering static pages, Apache 2.2 series was considered significantly slower than nginx and varnish.[41] 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.[42] [clarification needed ] 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.[43] [44] [45] However, some independent but significantly outdated benchmarks show that it is still half as fast as nginx, e.g.[46]
Licensing
[edit ]The Apache HTTP Server codebase was relicensed to the Apache 2.0 License (from the previous 1.1 license) in January 2004,[47] and Apache HTTP Server 1.3.31 and 2.0.49 were the first releases using the new license.[48]
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.[49] [50] [51] They initially replaced it with Nginx, and soon after made their own replacement, OpenBSD Httpd, based on the Relayd project.[52] [53] [54] [55]
Versions
[edit ]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
[edit ]Version | Initial release | Latest release |
---|---|---|
Unsupported: 1.3 | 1998年06月06日[56] | 2010年02月03日 (1.3.42)[57] |
Unsupported: 2.0 | 2002年04月06日[58] | 2013年07月10日 (2.0.65)[59] |
Unsupported: 2.2 | 2005年12月01日[60] | 2017年07月11日 (2.2.34)[61] |
Latest version: 2.4 | 2012年02月21日[62] | 2025年07月23日 (2.4.65)[63] |
Legend: Unsupported Supported Latest version Preview version Future version |
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.[64] [65] [66]
Apache 2.4 dropped support for BeOS, TPF, A/UX, NeXT, and Tandem platforms.[8]
Security
[edit ]Older versions of Apache were vulnerable to a denial-of-service attack called Slowloris, which creates many simultaneous partially completed requests, exhausting the server's pool of available connections.[67] Since Apache 2.2.15, Apache ships the module mod_reqtimeout as the official solution supported by the developers.[68]
See also
[edit ]- .htaccess
- .htpasswd
- ApacheBench
- Comparison of web server software
- IBM HTTP Server
- LAMP (software bundle)
- XAMPP
- List of Apache modules
- List of free and open-source software packages
- POSSE project
- suEXEC
- Apache Tomcat - another web server developed by the Apache Software Foundation
References
[edit ]- ^ "About the Apache HTTP Server Project". Apache Software Foundation. Archived from the original on 7 June 2008. Retrieved 2008年06月25日.
- ^ "[ANNOUNCEMENT] Apache HTTP Server 2.4.65 Released". 23 July 2025. Retrieved 24 July 2025.
- ^ "Apache Software Foundation Index: Projects by Programming Language Index". Archived from the original on 2016年03月02日. Retrieved 2016年02月27日.
- ^ "Compiling and Installing". httpd.apache.org. The Apache Software Foundation. Archived from the original on 7 May 2016. Retrieved 9 May 2016.
- ^ "OS/Linux Distributions using Apache". secure1.securityspace.com. Archived from the original on 2018年09月18日. Retrieved 2018年09月17日.
- ^ "Platform Specific Notes - Apache HTTP Server Version 2.4". httpd.apache.org. Archived from the original on 2019年01月22日. Retrieved 2019年01月21日.
- ^ "Secure Web Server". vmssoftware.com. Archived from the original on 2020年10月22日. Retrieved 2020年10月20日.
- ^ a b "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.
- ^ "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日.
- ^ "About the Apache HTTP Server Project - The Apache HTTP Server Project". httpd.apache.org. Retrieved 2024年02月08日.
- ^ Netcraft Market Share Archived 2010年05月20日 at the Wayback Machine for Top Servers Across All Domains August 1995 - today (monthly updated)
- ^ "February 2009 Web Server Survey". Netcraft. 18 February 2009. Archived from the original on 26 February 2009. Retrieved 2009年03月29日.
- ^ "March 2025 Web Server Survey". Netcraft News. 25 March 2025. Archived from the original on 2025年04月01日. Retrieved 2025年04月14日.
- ^ "Usage Statistics of Web Servers". w3techs.com. Retrieved 2025年04月14日.
- ^ "Apache Foundation". www.apache.org. Archived from the original on 13 December 2021. Retrieved 22 August 2018.
- ^ ""Trillions and Trillions Served" documentary feature on The Apache Software Foundation". TheApacheFoundation / Youtube. 2020. Archived from the original on 2021年11月22日.
- ^ "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日.
- ^ "Information on the Apache HTTP Server Project". 1997年04月15日. Archived from the original on April 15, 1997.
- ^ "Apache Server Frequently Asked Questions". Archived from the original on 1997年01月06日. Retrieved 15 January 2017.
- ^ McMillan, Robert (15 April 2000). "Apache Power". Linux Magazine. Archived from the original on 28 January 2019.
- ^ 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日.
- ^ 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日.
- ^ "Apache Docs". httpd.apache.org. Archived from the original on 5 September 2018. Retrieved 22 August 2018.
- ^ "Apache Web Server". webopedia.com. 23 March 1998. Archived from the original on 12 May 2021. Retrieved 12 May 2021.
- ^ "Apache HTTP Server Tutorial: .htaccess files". Apache.org. Archived from the original on 2016年02月25日. Retrieved 2016年02月19日.
- ^ "mod_proxy". Apache.org. Archived from the original on 2018年07月29日. Retrieved 2016年02月19日.
- ^ "mod_proxy_balancer". Apache.org. Archived from the original on 2016年02月13日. Retrieved 2016年02月19日.
- ^ "Balancer Manager". Apache.org. Archived from the original on 2016年03月04日. Retrieved 2016年02月19日.
- ^ "Authentication and Authorization". Apache.org. Archived from the original on 2018年01月31日. Retrieved 2016年02月19日.
- ^ "mod_rewrite". Apache.org. Archived from the original on 2016年02月13日. Retrieved 2016年02月19日.
- ^ "mod_headers". Apache.org. Archived from the original on 2016年02月21日. Retrieved 2016年02月19日.
- ^ "mod_sed". Apache.org. Archived from the original on 2016年03月04日. Retrieved 2016年02月19日.
- ^ "mod_substitute". Apache.org. Archived from the original on 2016年03月04日. Retrieved 2016年02月19日.
- ^ "Apache httpd Tutorial: Introduction to Server Side Includes". Apache.org. Archived from the original on 2016年02月18日. Retrieved 2016年02月19日.
- ^ "mod_usertrack". Apache.org. Archived from the original on 2021年05月12日. Retrieved 2021年05月12日.
- ^ "Apache Tutorial: Dynamic Content with CGI". Apache.org. Archived from the original on 2021年11月15日. Retrieved 2016年02月19日.
- ^ "Per-user web directories". Apache.org. Archived from the original on 2016年02月16日. Retrieved 2016年02月19日.
- ^ "Expressions in Apache HTTP Server". Apache.org. Archived from the original on 2016年02月29日. Retrieved 2016年02月19日.
- ^ "mod_status". Apache.org. Archived from the original on 2016年02月13日. Retrieved 2016年02月19日.
- ^ "Apache Module: mod_ftp". Apache.org. Archived from the original on 2017年07月10日. Retrieved 2017年07月08日.
- ^ "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.
- ^ "worker - Apache HTTP Server Version 2.2". apache.org. Archived from the original on 2021年05月10日. Retrieved 2021年05月12日.
- ^ "Apache httpd 2.4" (PDF). Archived (PDF) from the original on 2012年01月27日. Retrieved 2012年02月08日.
- ^ "Picking a Proxy Server". 14 April 2014. Archived from the original on 3 March 2016. Retrieved 19 February 2016.
- ^ "Throughput evaluation of Apache 2.4.1". 22 February 2012. Archived from the original on 2016年03月02日. Retrieved 2016年02月19日.
- ^ "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.
- ^ "Apache License, Version 2.0". The Apache Software Foundation. January 2004. Archived from the original on 2013年05月18日. Retrieved 2013年05月21日.
- ^ Burton, Richard Antony. "FYI: Apache HTTP Server 2.0.49 Released". Newsgroup: alt.apache.configuration . Retrieved 2018年02月16日.
- ^ de Raadt, Theo (18 February 2004). "The new apache license". openbsd-misc (Mailing list). Retrieved 2013年05月21日.
- ^ "Copyright Policy". OpenBSD. Archived from the original on 2017年11月13日. Retrieved 2013年05月12日.
- ^ "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日.
- ^ 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.
- ^ "OpenBSD Upgrade Guide: 5.1 to 5.2". openbsd.org. Archived from the original on 2017年12月22日. Retrieved 2014年03月13日.
- ^ 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日.
- ^ "OpenBSD Upgrade Guide: 5.5 to 5.6". openbsd.org. Archived from the original on 2014年12月22日. Retrieved 2014年12月29日.
- ^ "Announcement: Apache 1.3.0 Released !". 1998年06月06日. Archived from the original on 2018年12月11日. Retrieved 2015年01月06日.
- ^ "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日.
- ^ "Official Release: Apache 2.0.35 is now GA". 2002年04月06日. Archived from the original on 2018年12月12日. Retrieved 2015年01月06日.
- ^ "[Announcement] Apache HTTP Server 2.0.65 Released". apache.org. Archived from the original on 2015年07月28日. Retrieved 2015年01月06日.
- ^ "Apache HTTP Server 2.2.0 Released". 2005年12月01日. Archived from the original on 2018年12月12日. Retrieved 2015年01月06日.
- ^ "[Announce] Apache HTTP Server 2.2.34 Released". apache.org. Archived from the original on 2020年08月21日. Retrieved 2019年04月03日.
- ^ "[ANNOUNCEMENT] Apache HTTP Server 2.4.1 Released". 2012年02月21日. Archived from the original on 2021年02月12日. Retrieved 2015年07月17日.
- ^ "Apache HTTP Server 2.4.65 Released". apache.org. Retrieved 2025年07月29日.
- ^ 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日.
- ^ "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.
- ^ "Chapter 4. The Apache HTTP Server". fedoraproject.org. Archived from the original on 2012年11月25日. Retrieved 2012年12月03日.
- ^ Zdrnja, Bojan (21 June 2009). "Apache HTTP DoS tool mitigation". SANS Institute. Archived from the original on 12 November 2021. Retrieved 12 November 2021.
- ^ "mod_reqtimeout". Apache.org. Archived from the original on 2013年07月03日. Retrieved 2013年07月03日.