Overall, I assess the configurability of Apache Web Server for optimizing performance and security aspects as acceptable; nowadays, security is on another level. At that time, it was decent for simple, insecure services, with only the concern of someone hacking the system. Today, it is much more severe; you could cause a lot of harm to many different applications without noticing. If I had to create an application using Apache Tomcat again, I would use a lot of other things, not Apache's security modules and functionalities, but authorization services and other security measures. I prefer to stay away from big players such as Oracle and IBM because in the long run, you are bound to their systems. While I can recommend Apache Web Server, especially for simple implementations and administration tools, I advise keeping it on straightforward, simple machines without requiring much service or maintenance. I rate this product an eight overall.
I would recommend Apache Web Server because it is freeware and offers reliable support. Their documentation is well-structured, allowing for seamless migration. I rate the solution nine out of ten. The overall product rating is nine out of ten.
Apache Web Server is a time-tested product and is one of the primary choices of all application users. You can install a web application within the Apache Web Server and then the applications run in the solution allowing you to access the application via a browser. For instance, when you open Gmail, which is an application running on an Apache Web Server, the server displays the webpage and provides a response based on your inputs. Apache Web Server has several in-built modules, and each module needs to be configured within the solution. For example, if you want to use the product as a proxy server, you need to configure the proxy configuration, and if you want to use it as a caching server, you can configure it for caching purposes. Apache also provides a dedicated web server for Java applications known as Apache Tomcat. Due to their wide use cases, Apache products are used by almost every organization. Anywhere you want to use and host web applications, Apache Web Server can be used. There is a widely used platform called LAMP, which is created using Linux, Apache, MySQL, and PHP. Beginner level learners of application development and designing are also using Apache Web Server. Nowadays, in some cases, Apache Web Servers are being used as load balancers. For instance, suppose there are five to six servers in your organization, and you want to divide the load among those servers; let's assume ten requests must be divided among the servers. In the aforementioned case, you will route the incoming requests across the servers in two batches of five requests to balance the load so that one server doesn't get immensely loaded. There are two segments of security provided by the Apache Web Server; one is inside the network, while the other one is outside. If a request has arrived within the application, then it's the user's responsibility to secure the application, and it's usually managed using the concept of militarized zone and de-militarized zone. All the application servers are kept within the militarized zone and to allow public users access to the application, a proxy server or load balancer is used as an interface between the users and the servers which are present within the militarized zone. Therefore, one shouldn't completely rely on a web configuration to manage the complete security because security is multi-level, involving the network level, application level and user level. Professionals often use a combination of servers for different use cases; while someone might use Apache for load balancing, another individual might use NGINX for the same purpose, and this preference often depends upon the professional's expertise in the solutions. I would rate Apache Web Server as nine out of ten. I would definitely recommend others to use Apache Web Server as it's an excellent solution, and they should learn about specific use cases that can be addressed using Apache Web Server. There is reliable documentation available for Apache that includes information on core enhancements and new modules, including modules for functionality enhancement in Apache Web Server. The vendor continues to enhance the Apache Web Server by introducing new modules. Apache Web Server handles traffic efficiently without the need for many configuration adjustments, depending on the cases in which the configuration is primarily implemented. As the solution is open-source, it's always open to anyone who wants to use and learn about Apache Web Server. A beginner can also use it for pilot deployments or user application testing, but for advanced use, one needs to learn about Apache Web Server completely, including its modules, features, and functionality. If someone wants to buy Apache Web Server then it can be bought directly from Red Hat, they sell Apache Web Server as a bundle component when one buys the JBoss platform.
In terms of scalability and performance, I would say that the performance is similar to NGINX. Right now, we are not using the tool in relation to our company's traffic. The tool is fine, but I haven't tried to use it much for the traffic part if I compare it with NGINX. When it comes to modularity, for the configuration part, there is a separate module users can create for each of the shared applications, which is similar to what NGINX offers. The product's security features are reliable, especially since Apache provides ModSecurity for HSTS. You can overcome the need for most of the security headers if you add ModSecurity packaged with Apache, which is fine for our company. I recommend the product to beginners who want a simple base server in their company for security purposes. I have to pay if I go with ModSecurity in NGINX. If I am a beginner who wants to secure my application, then I need to choose Apache Web Server since it offers ModSecurity for free. The benefit of the use of the product stems from the capability it provides in the form of the security module, which is called ModSecurity. For NGINX, if you want to integrate ModSecurity, it comes across as a very lengthy module. If you talk about Apache, it is very easy. I think Apache offers unique features. Apache Web Server offers modular configuration. On multiple websites, you can host multiple domains, and it also offers the capability of modularity, which allows you to create multiple configuration modules on separate web applications. Apache Web Server is available as an open-source tool. In the product, you can get a free signature update for the database which is the most vulnerable, and you will get an update if you are using ModSecurity. Users also get community support. I rate the tool an eight out of ten.
I would suggest optimizing especially the performance of the web server. So wherever my website is forecasting, it should be able to load as much as possible, and then security. I should log the IP addresses of whoever try to access my website information and probe my web content properly. So, I would block those. I would suggest performance and security are what you need to take care of with the Apache web server. Overall, I would rate the solution an eight out of ten.
Overall, I would rate the solution an eight out of ten because I have to manage the infrastructure myself. I would recommend using the product if they're using it on-premises.
I'm not sure of the exact version of the solution. It's around version two. It might be 2.4 or 2.6. I'd recommend the solution to others. Depending on the use case, I'd encourage people to use the Apache security models and to use various proxies. I'd rate the solution nine out of ten.
I rate this solution an eight out of ten. Regarding advice, there is a security-related problem that depends on the web server's configuration. If you install the web server, it works, and you can put your web application in a directory that Apache Web Server reads from to display the web application. The default installation comes with a default configuration. With default configuration comes security flaws, so you need to set permissions in the configuration file in your website directory. Before you deploy your application with Apache Web Server, you need to know how to configure a web server, how the HTTP protocol works, and how communication between the client and the server works. If you don't know how to configure everything in a web server, sometimes your server can hang unexpectedly. Sometimes your website won't work as expected, and you will create or offer malicious persons to have access to your web server. If they have access to the web server, they can access every server in the organization because the web server is like the front door. If it's properly secured, it will be difficult for malicious people to enter your organization, but bad things can happen if it's not very secure. Regarding features, Apache offers a module that will change the behaviour of the Apache Web Server, including some security features that will protect your application from the most used web attacks. It will act like a web firewall where you configure your Apache Web server to protect your web application from widely used attacks on the web. The feature is called Security Mode. It's a module that you can install and act as a web firewall called the WAF (Web Application Firewall), which will not only serve the client but will check their request to see or detect if they are part of an initiated attack or not.
VP at a computer software company with 201-500 employees
Real User
Jan 27, 2021
We're just a customer. We are an end-user of Apache. We haven't done any recent upgrades and therefore aren't likely using the latest version of the solution currently. So far we are still exploring to see what are the best or the more cost-effective tools for us to integrate as there are so many properties we need to integrate with different protocols. So, we are still exploring, looking for the best approach. I'd recommend the solution. Overall, I'd rate the solution at a seven out of ten. We've been mostly happy with that product so far.
Senior Supervisor of Virtualisation & DevOps at a tech consulting company with 201-500 employees
Real User
Jan 7, 2020
The first point of using these services is that you have to use scripts for deploying the web servers on the systems. They can be effectively used in many platforms and deployed for heavy duties, but tuning and improving them requires some work. Automating with scripts will help to save some time. My advice to anybody who is implementing this solution is to deploy it on a Linux-based server and follow the best practices. I would rate this solution an eight out of ten.
Senior Administrator at IMCC ( Tejarat Iran Mall )
Real User
Jan 7, 2020
Of course, I would recommend this service because we have had a good experience with it. On a scale from one to ten where one is the worst and ten is the best, I would rate Apache Web Server as an eight.
The Apache HTTP Server Project was founded in 1995 by a group of webmasters, known as The Apache Group, with the aim of developing robust, richly-featured, freely-available and commercial-standard Web (HTTP) server source code. The result was Apache Web Server or Apache HTTP Server, which is an open-source public-domain web server.This collaborative project has been enhanced ever since with contributions from the core development team and other volunteers situated all over the globe. Also,...
Overall, I assess the configurability of Apache Web Server for optimizing performance and security aspects as acceptable; nowadays, security is on another level. At that time, it was decent for simple, insecure services, with only the concern of someone hacking the system. Today, it is much more severe; you could cause a lot of harm to many different applications without noticing. If I had to create an application using Apache Tomcat again, I would use a lot of other things, not Apache's security modules and functionalities, but authorization services and other security measures. I prefer to stay away from big players such as Oracle and IBM because in the long run, you are bound to their systems. While I can recommend Apache Web Server, especially for simple implementations and administration tools, I advise keeping it on straightforward, simple machines without requiring much service or maintenance. I rate this product an eight overall.
I would recommend Apache Web Server because it is freeware and offers reliable support. Their documentation is well-structured, allowing for seamless migration. I rate the solution nine out of ten. The overall product rating is nine out of ten.
Apache Web Server is a time-tested product and is one of the primary choices of all application users. You can install a web application within the Apache Web Server and then the applications run in the solution allowing you to access the application via a browser. For instance, when you open Gmail, which is an application running on an Apache Web Server, the server displays the webpage and provides a response based on your inputs. Apache Web Server has several in-built modules, and each module needs to be configured within the solution. For example, if you want to use the product as a proxy server, you need to configure the proxy configuration, and if you want to use it as a caching server, you can configure it for caching purposes. Apache also provides a dedicated web server for Java applications known as Apache Tomcat. Due to their wide use cases, Apache products are used by almost every organization. Anywhere you want to use and host web applications, Apache Web Server can be used. There is a widely used platform called LAMP, which is created using Linux, Apache, MySQL, and PHP. Beginner level learners of application development and designing are also using Apache Web Server. Nowadays, in some cases, Apache Web Servers are being used as load balancers. For instance, suppose there are five to six servers in your organization, and you want to divide the load among those servers; let's assume ten requests must be divided among the servers. In the aforementioned case, you will route the incoming requests across the servers in two batches of five requests to balance the load so that one server doesn't get immensely loaded. There are two segments of security provided by the Apache Web Server; one is inside the network, while the other one is outside. If a request has arrived within the application, then it's the user's responsibility to secure the application, and it's usually managed using the concept of militarized zone and de-militarized zone. All the application servers are kept within the militarized zone and to allow public users access to the application, a proxy server or load balancer is used as an interface between the users and the servers which are present within the militarized zone. Therefore, one shouldn't completely rely on a web configuration to manage the complete security because security is multi-level, involving the network level, application level and user level. Professionals often use a combination of servers for different use cases; while someone might use Apache for load balancing, another individual might use NGINX for the same purpose, and this preference often depends upon the professional's expertise in the solutions. I would rate Apache Web Server as nine out of ten. I would definitely recommend others to use Apache Web Server as it's an excellent solution, and they should learn about specific use cases that can be addressed using Apache Web Server. There is reliable documentation available for Apache that includes information on core enhancements and new modules, including modules for functionality enhancement in Apache Web Server. The vendor continues to enhance the Apache Web Server by introducing new modules. Apache Web Server handles traffic efficiently without the need for many configuration adjustments, depending on the cases in which the configuration is primarily implemented. As the solution is open-source, it's always open to anyone who wants to use and learn about Apache Web Server. A beginner can also use it for pilot deployments or user application testing, but for advanced use, one needs to learn about Apache Web Server completely, including its modules, features, and functionality. If someone wants to buy Apache Web Server then it can be bought directly from Red Hat, they sell Apache Web Server as a bundle component when one buys the JBoss platform.
In terms of scalability and performance, I would say that the performance is similar to NGINX. Right now, we are not using the tool in relation to our company's traffic. The tool is fine, but I haven't tried to use it much for the traffic part if I compare it with NGINX. When it comes to modularity, for the configuration part, there is a separate module users can create for each of the shared applications, which is similar to what NGINX offers. The product's security features are reliable, especially since Apache provides ModSecurity for HSTS. You can overcome the need for most of the security headers if you add ModSecurity packaged with Apache, which is fine for our company. I recommend the product to beginners who want a simple base server in their company for security purposes. I have to pay if I go with ModSecurity in NGINX. If I am a beginner who wants to secure my application, then I need to choose Apache Web Server since it offers ModSecurity for free. The benefit of the use of the product stems from the capability it provides in the form of the security module, which is called ModSecurity. For NGINX, if you want to integrate ModSecurity, it comes across as a very lengthy module. If you talk about Apache, it is very easy. I think Apache offers unique features. Apache Web Server offers modular configuration. On multiple websites, you can host multiple domains, and it also offers the capability of modularity, which allows you to create multiple configuration modules on separate web applications. Apache Web Server is available as an open-source tool. In the product, you can get a free signature update for the database which is the most vulnerable, and you will get an update if you are using ModSecurity. Users also get community support. I rate the tool an eight out of ten.
I would suggest optimizing especially the performance of the web server. So wherever my website is forecasting, it should be able to load as much as possible, and then security. I should log the IP addresses of whoever try to access my website information and probe my web content properly. So, I would block those. I would suggest performance and security are what you need to take care of with the Apache web server. Overall, I would rate the solution an eight out of ten.
Overall, I would rate the solution an eight out of ten because I have to manage the infrastructure myself. I would recommend using the product if they're using it on-premises.
Overall, I would rate it ten out of ten.
I would definitely recommend Apache Web Server to anyone who is considering using it. Overall, I would rate it a ten out of ten.
I rate Apache Web Server a ten out of ten. I did an online course to learn how to use the product. I recommend it to users who want to build websites.
I would rate the tool a ten out of ten.
I'm not sure of the exact version of the solution. It's around version two. It might be 2.4 or 2.6. I'd recommend the solution to others. Depending on the use case, I'd encourage people to use the Apache security models and to use various proxies. I'd rate the solution nine out of ten.
I rate this solution an eight out of ten. Regarding advice, there is a security-related problem that depends on the web server's configuration. If you install the web server, it works, and you can put your web application in a directory that Apache Web Server reads from to display the web application. The default installation comes with a default configuration. With default configuration comes security flaws, so you need to set permissions in the configuration file in your website directory. Before you deploy your application with Apache Web Server, you need to know how to configure a web server, how the HTTP protocol works, and how communication between the client and the server works. If you don't know how to configure everything in a web server, sometimes your server can hang unexpectedly. Sometimes your website won't work as expected, and you will create or offer malicious persons to have access to your web server. If they have access to the web server, they can access every server in the organization because the web server is like the front door. If it's properly secured, it will be difficult for malicious people to enter your organization, but bad things can happen if it's not very secure. Regarding features, Apache offers a module that will change the behaviour of the Apache Web Server, including some security features that will protect your application from the most used web attacks. It will act like a web firewall where you configure your Apache Web server to protect your web application from widely used attacks on the web. The feature is called Security Mode. It's a module that you can install and act as a web firewall called the WAF (Web Application Firewall), which will not only serve the client but will check their request to see or detect if they are part of an initiated attack or not.
We're just a customer. We are an end-user of Apache. We haven't done any recent upgrades and therefore aren't likely using the latest version of the solution currently. So far we are still exploring to see what are the best or the more cost-effective tools for us to integrate as there are so many properties we need to integrate with different protocols. So, we are still exploring, looking for the best approach. I'd recommend the solution. Overall, I'd rate the solution at a seven out of ten. We've been mostly happy with that product so far.
I would recommend the solution to others. I would rate this solution as a nine (out of 10).
The first point of using these services is that you have to use scripts for deploying the web servers on the systems. They can be effectively used in many platforms and deployed for heavy duties, but tuning and improving them requires some work. Automating with scripts will help to save some time. My advice to anybody who is implementing this solution is to deploy it on a Linux-based server and follow the best practices. I would rate this solution an eight out of ten.
Of course, I would recommend this service because we have had a good experience with it. On a scale from one to ten where one is the worst and ten is the best, I would rate Apache Web Server as an eight.