Apache HTTP Server#Features

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".{{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 }} 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.{{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}}{{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}} 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."{{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 }}{{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}}

But in an April 2000 interview, Behlendorf asserted that the origins of Apache were not a pun, stating:{{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}}

{{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 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.{{Cite web |last=Claburn |first=Thomas |date=2023-01-11 |title=Native Americans ask Apache foundation to change name |url=https://www.theregister.com/2023/01/11/native_american_apache_software_foundation/ |url-status=live |archive-url=https://web.archive.org/web/20230112000842/https://www.theregister.com/2023/01/11/native_american_apache_software_foundation/ |archive-date=2023-01-12 |access-date=2023-01-12 |website=The Register |language=en}}{{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 }}

When Apache is running under Unix, its process name is {{code|httpd}}, which is short for "HTTP daemon".{{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 }}

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.{{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}}

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{{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 }}
• Reverse proxy with caching{{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 }}
• Load balancing{{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 }} 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{{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}}
• 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{{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}}
• gzip compression and decompression
• URL rewriting{{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 }}
• Headers{{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 }} and content{{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 }}{{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 }} rewriting
• Custom logging with rotation
• Concurrent connection limiting
• Request processing rate limiting
• Bandwidth throttling
• Server Side Includes{{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 }}
• IP address-based geolocation
• User and Session tracking{{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 }}
• WebDAV
• Embedded Perl, PHP and Lua scripting
• CGI support{{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 }}
• public_html per-user web-pages{{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 }}
• Generic expression parser{{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}}
• Real-time status views{{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 }}
• FTP support (by a separate module){{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 }}

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.{{clarify |date=August 2018}}

For delivering static pages, Apache 2.2 series was considered significantly slower than nginx and varnish.{{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}} 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.{{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}}{{clarify |date=August 2018 |reason=Mixes the use of xyz with what? Or, if (a) several processes and (b) several processes per thread are the things being mixed, the sentence should read "...Event MPM, which uses several processes and several threads per process...". Also, can someone with more technical knowledge please explain why this approach is advantageous?}} This architecture as implemented in the Apache 2.4 series performs at least as well as event-based web servers, according to Jim Jagielski and other independent sources.{{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}}{{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}}{{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}} However, some independent but significantly outdated benchmarks show that it is still half as fast as nginx, e.g.{{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}}

The Apache HTTP Server codebase was relicensed to the Apache 2.0 License (from the previous 1.1 license) in January 2004,{{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}} and Apache HTTP Server 1.3.31 and 2.0.49 were the first releases using the new license.{{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}}

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.{{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}}{{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}}{{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 }} They initially replaced it with Nginx, and soon after made their own replacement, OpenBSD Httpd, based on the Relayd project.{{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 }}{{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}}{{cite web|url=http://undeadly.org/cgi?action=article&sid=20140314080734|date=2014-03-14|title=Heads Up: Apache Removed from Base|website=OpenBSD Journal|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}}{{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}}

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.

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.{{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}}{{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}}{{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}}

Apache 2.4 dropped support for BeOS, TPF, A/UX, NeXT, and Tandem platforms.{{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 }}

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.{{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=SANS Institute|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}} Since Apache 2.2.15, Apache ships the module mod_reqtimeout as the official solution supported by the developers.{{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 }}

{{Portal|Free and open-source software}}

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

{{Reflist|30em}}

{{Wikibooks|Apache}}

• {{Official website}}

{{Apache Software Foundation}}

{{Web server software}}

{{Web interfaces}}

{{Authority control}}

Category:1995 software

Category:Cross-platform free software

Category:Free software programmed in C

Category:Free web server software

Category:Reverse proxy

Category:Software using the Apache license

Category:Unix network-related software

Category:Web server software for Linux