Apache HTTP Server

Used to Host Web Applications

Used as a Proxy Server

Used to Host several Virtual Hosts.

it should support multiple versions of PHP out of the box.

Its official documentation needs improvement. It is not user-friendly.

configuration of the XML conf file is complex

Very flexitble

Easy to setup

Lot's of support available

Sometimes too many options

Examples online can be wrong

PHP Integration.

Powerful configuration.

Redirects made easy.

Configuration files are located on different places depending on your Linux distro.

If you have an error on one configuration file, apache refuses to start and sometimes is difficult to know why.

Security is not great by default, but making a todo list help when you configure a new server.

Robust

Well documented

Easy configuration

I think it could use a web UI to configure it

It could allow PHP to override configuration without having to modify it

I've never seen statistics for it so I assume there is not much built in

Easy to configure, although many options are available.

High performance

Industry standard, many colleagues have know-how

Performance of the competitor (NGINX) is a bit better

Incorrect configuration can lead to security risks

Modules that are not needed are difficult to identify

It does good with virtual hosts implementation

It has good easy to read intuitive documentation and tutorials

It is widely used so in the Internet there are many examples that could be adopted

Some specific modules might be difficult to install

Marketing could be more informative; some people prefer NGINX because they do not know how to do it with apache

Virtual host management offers extensive configuration options

The ease of working with own and third-party modules

Implementation as a load balancer is particularly good and helpful

A descriptive graphical interface

Native tool for statistics of use, access, error among others

How hard it is to find something that Apache HTTP Server can improve is really great

Ease of use

Well documented

Mature

Optimization

Not as flexible as new alternatives.

Apache Web Server provides detailed configuration options that makes it great for web applications where performance and a high level of security are a consideration.

It works well even with reasonable compute / hardware for infrastructure.

Although it has detailed configuration and administration capabilities, there is a steep learning curve to be able to configure Apache Web Server. It is not for beginners.

The management console / dashboard can certainly be made better with default parameters in place.

Apache is Open Source, governed well (the foundation) and probably the most stable computing platform ever.

Apache is probably one of the most customizable and configurable pieces of software that I have ever run across in more than 30 years of development.

If there is something that Apache can not do, then you need to ask yourself; should I be doing that? The point here is that it is a solid solution and seems to only integrate other technologies that are of the highest caliber.

Apache will live forever and you can not go wrong with it.

The one thing that I worry about Apache is the PHP language which is integrated into the platform. I am not sure if PHP has a relevant future. I worry about this because Python is becoming very popular.

Some, not so sharp developers, might complain about the configuration file. Yes, it is complex. You need to learn it.

Apache SSL documentation can be better.

I would like to see video streaming, that would be fantastic.

Street Cred: Apache Web Server is the Founder for all of Apache Foundation's other projects. Without the Web Server, Apache Foundation would look very different. That being said, they have done a good job of maintaining the code base, and keeping a lot of what makes Apache so special

Stability: Apache is rock-solid. While no software is perfect, Apache can parse your web sources quickly and cleanly.

Flexibility: Need to startup your own Webpage? Done. Wordpress? Yup. REST Endpoint? Check. Honeypot? Absolutely.

Large Attack Surface: Since Apache WS has been around so long, it's easy for villains to attack a public instance and find a vulnerability that may have existed for a lengthy period of time. With the rise of Platforms such as MetaSploit and Linux distro's like ParrotOS and Kali, finding those types of bugs / holes becomes much easier and cheaper.

Configuration Scheme: While it's easy to configure Apache, it's a bit strange if you have never been exposed to it: Most software packages (indeed, even competing Web Servers) enable / disable webpages by a simple config file, Apache has a multistep process to setting up Websites. And while this might be great for larger websites, it's a lot of work for a simple webpage (say, something that simply vomits a report or informational page). I feel like this could be simplified greatly.

Configuration Fatigue: Iterating off of the last point: The configuration files themselves are extensive, and lengthy. They resemble XML, but are not quite: They are actually sort of their own Markup, so that makes configuration a little more costly, in units of time.

Apache allows for single site configuration using .htaccess files. This allows you to make changes on a micro level.

Apache offers WHM which allows experienced server admins a powerful tool for configuring their web server.

Apache is well maintained. It receives frequent feature upgrades, security patches, and vulnerability improvements.

Apache spawns new processes for each request.

Apache allows you to modify its configuration (which is a plus). This, however, can cause a serious threat to the security, if not done properly.

Apache consumes more RAM under heavier load.

Apache server is a free and open source multi-platform software which gives ample amount of possibilities and options to use it without worrying about the hardware configurations much; it runs on almost everything!

It is easy to configure quickly for a new project requires to set up a barebone server to serve any type of HTTP request.

It allows us to configure https with encryption and configure virtual hosts easily.

Log files are detailed enough to determine vulnerabilities by providing multiple params which makes it easy to diagnose and debug the root cause of any server issue.

The default configurations which comes with Apache server needs to get optimized for performance and security with every new installation as these defaults are not recommended to push on the production environment directly.

Security options and advanced configurations are not easy to set up and require an additional level of expertise.

Admin frontend GUI could be improved to a great extent to match with other enterprise tools available to serve similar requirements.

Easy to configure and is the go-to web server for many people.

Great documentation and community support.

Modules for added functionality.

Quicker development of new features.

A slim version of Apache would be neat for use in small deployments.

Just copying our application folder in webapps and restarting the server will provide the application in browser and mostly it's secured.

Easily change from default port to custom port

Easily to transition http to https after doing some minimal set of configurations

Can easily navigate with your own domain name using Apache by doing some configuration

I would prefer it to be more user friendly

Looking for clear user guide documentation to understand all functionality

If EAR files are added, they should be accepted. In fact, accepting only WAR files.

The documentation for Apache is very extensive and useful.

There are a lot of users and systems folks that are familiar with Apache Web Server.

There are so many available modules to help you customize Apache for your uses.

There are times that Apache doesn't scale as well as we want.

Stability - the apache web server is extremely stable, with many months or even years in-between crashes or reboots

Documentation - Apache is the #1 web server in the world, so there is a huge amount of documentation for support

Compatibility - Apache is compatible with every technology I have come across

Powerful - Apache can do a lot with a little, with hardware requirements that are very easy to achieve for low cost

Apache configuration can be difficult for advanced setups

Apache is configured slightly differently for the various flavors of Linux.

Private files can be hidden or set up only for specific users.

You can block certain file types from being uploaded to your website.

You can block certain IP addresses from accessing your website.

Apache web server does not allow for multi-threading, meaning that too many users can crash the system causing downtime for your website.

Apache web server is not very fast in that you have to do some tweaking to allow for your website to be faster.

Apache web server is free and doesn't come tagged with license/purchase costs.

Apache is the oldest web server and is widely used. The major advantage here is that all kinds of issues have been reported/resolved which gives an ease of understanding/ability for the user for install/support purposes.

It is the most widely used web server in the market and has been known to support new technology. This web server is continuously updated by a team of developers- keeping it up to standards.

Apache has a strong user community that helps with answering questions in any area - installation/support/maintenance/upgrade of this software.

Apache web server is a highly recommended server and its disadvantages outweigh its advantages any time.

Apache web server uses thread based processing which has some ove head when compared to newer web servers.

Great handling of virtual hosts.

Works extremely well with Perl/CGI and the Mod-Perl module for fast and reliable execution of server side scripts.

Handles serving up web pages well, a true no muss, no fuss situation.

Sometimes a little hard to patch.

If you're not careful with the settings, you can easily provide too much information about your server to people you don't want to.

If you're not familiar with text configuration files, it can get a little hairy, as there is no GUI interface for setting it up.