That is a great tool. You only should avoid using the feather icon from ASF.

As part of my job I have to install and uninstall Apache quite frequently for our apprentices, sometimes with PHP, sometimes without.

Because of this, I made an installer. I don't mean a collection of scripts, but a real installer like you would use for any other software.
https://imgur.com/a/QjeJtRG

I originally didn't intend for it to be used publicly but I changed a few things to make it suitable. Notable features:

• Created a page for update checks and download of installer bundles. There's currently only one installer but I intend for it to grow over time
• Made installer more foolproof (It should stop the service when you try to update a running instance for example)
• Added ability to create firewall rules
• It will create the configuration files and php.ini if not present but will never overwrite them
• php.ini is dynamically changed to reflect a custom path selection by the user
• Post install notes that provide some troubleshooting hints and explain the problems that can arise from running Apache as "Local Service"
• Digital signature. Note: Only the installer and uninstaller are currently signed. I can sign all Apache+PHP binaries in the installer upon popular request but it should not be necessary
• Made PHP optional
• Added the license and changes file
• Permission hardening can be reversed and reapplied at any time
• Removes firewall rules again when you uninstall
• The contents of "htdocs" are never deleted when uninstalling in case you need them later
• Apache is run under an unprivileged "Local Service" user instead of a god account
• It should work if there are spaces in the path name (I still recommend you don't)

I can include all the optional modules if requested. I do not plan on creating 32 bit installers.

The default server configuration has been slightly changed:

• Apache is configured to use PHP as a CGI module using the ScriptAlias/ContentType model. This is always present, even if you don't install PHP, but in that case it has no effect
• index.php added to the automatic directory index
• inclusion of conf/extra/httpd-mpm.conf is enabled by default

The PHP configuration is as follows:

• The base is the development PHP ini file
• Custom "temp" and "session" paths so PHP doesn't pollutes the Windows temp directory
• Safer session handling (user can't create their own id, the id is not accessible from JS)
• Configured a CA file that's in sync with Windows (at the time of creating the setup)

If interested, you can obtain the setup here: https://cable.ayra.ch/apache/

Feedback is encouraged. Thank you.

You can name the file anything you want and just Include it in httpd.conf.

If you need to whitelist IPs often and cannot afford a graceful restart every time, then you probably shouldn't be using the module.

I read from other source, there is configuration file for mod_evasive module, like evasive.conf or mod_evasive.conf (https://phoenixnap.com/kb/apache-mod-evasive). We can put all whitelist IPs in that configuration file. So where can we put that configuration file at , and whats the correct file name? Thanks

That mod_evasive doesn't allow to use .htaccess. So your only chance is to restart the server.

First i would like to THANK YOU for this website. It's very well done and all modules works well so far

Anyway, i have problem with evasive2_module. I know you don't like it (read from other forum), but this is very important mod.

Can you help me, after install and running well, some Ip got DOS blocked.

Now, i want to WHITELIST that IP.

I have to include new line of "DOSWhitelist   101.100.182.149" in "httpd.conf" then RESTART SERVER

The RESTART PART is IMPOSSIBLE everytime we need to whitelist IP.

So where is this module CONFIGURATION FILE that we can WHITELIST in .conf file without have to RESTART SERVER?

Can you help us to locate the correct .conf location and filename, and the settings inside .conf

If that's not possible, is there a way we can override/supercede the IP BLACKLIST in .htaccess instead ?

Imagine if an IP got blocked, and we have to RESTART the SERVER in order to let the IP able to access again.

THANK YOU for the help

I cannot remember exactly.

I started in the 90's with Sambar, the http and https are based on Apache 1 (version I cannot recall).  Started a support site with chat and forum . The first picture  I could find  is from  2001 https://web.archive.org/web/20011202001202/http://www.sambarserver.info/ 

Very nice GUI and ton of functions. Most config changes, no restart required. Features:  DHCP DNS FTP HTTPS HTTP WebDAV IM Jabber IRC MailSyslog Telnet TFTP Content Management Document Versioning Bridge Proxy FTP IMAP4 NNTP POP3 Reverse Proxies SMTP SOCKS Pass-thru Proxies.

Admin panel, see http://www.apachelounge.com/SambarServerAdministration.png . Still using it and forum at https://www.apachelounge.com/sambar/

Pity that development stopped and that HTTPD.Apache.org has not adopted some or all from Sambar.

I cannot recall when I was starting using Apache, I think in 2002. I started Apachelounge in 2003.

I can't say which version number it was for me. But I know it had only one digit after the three. Maybe 1.3.6 or 1.3.9.

IIRC 1.3.17 was the first one with an msi installer. One with the sources and one jsut the binaries. I wanted a portable version or at least a zip file. I was never able to open the msi files to extract the files. After some time I figured out how the change the path in the config that I was able to run it with from a USB strick any drive letter on any computer.
The msi was one of the reasons I found frist XAMPP which was too bloated and then Apache Lounge.

I confess that I still miss the VC6, it ran on every windows computer without installing anything. Plug the USB stick or copy the files and one of my friends had a running apache on their computer for the next LAN party. Safer than open the windows share.

I still miss the VC6...

Thank you Mario and Gregg.  I switched to NTLM and I was able to get subversion working where it captures userid in the subversion log.  Many thanks!

John

I think I figured it out. I had to make <directory> point to the tomcat webapp folder and I had to put JKMount in the <VirtualHost> area, it was not taking it from my mod_jk.conf file like in the base httpd.con file. If anyone see some errors or a better solution please post away.

I have a similar issue. Thanks for the solution.