The Apache Haus Forum

Advanced search  


Welcome to Apache Haus Distribution Forum

Pages: 1 2 [3] 4 5 ... 10
 on: July 17, 2020, 09:42:14 PM 
Started by rupindo - Last post by Gregg
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.

 on: July 16, 2020, 12:39:58 PM 
Started by rupindo - Last post by rupindo
I read from other source, there is configuration file for mod_evasive module, like evasive.conf or mod_evasive.conf ( 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

 on: July 15, 2020, 09:10:07 AM 
Started by rupindo - Last post by mario
That mod_evasive doesn't allow to use .htaccess. So your only chance is to restart the server.

 on: July 15, 2020, 07:51:46 AM 
Started by rupindo - Last post by rupindo
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" 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

 on: May 29, 2020, 11:25:18 AM 
Started by Gregg - Last post by Steffen
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 

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 . Still using it and forum at

Pity that development stopped and that 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.

 on: May 29, 2020, 06:46:56 AM 
Started by Gregg - Last post by ryanbaron
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...

 on: May 27, 2020, 09:24:43 PM 
Started by jleveille1337 - Last post by jleveille1337
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!


 on: May 27, 2020, 08:22:32 AM 
Started by RichV - Last post by benprescott
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.

 on: May 27, 2020, 08:14:42 AM 
Started by jleveille1337 - Last post by mario
the sspi does not work well with 2,4.x apache. As Gregg wrote use

 on: May 27, 2020, 04:02:48 AM 
Started by jleveille1337 - Last post by jleveille1337

I did a bit of tinkering.  I verified that the Apache setup that my co-worker built is working on Windows 2012.  Then I lifted the entire Apache2 directory, dragged it over to Windows 2019 and swapped it into place for my Apache server root folder.  When I tried starting it on Windows 2019 I got the very same library load error.  My conclusion is that there is something to do with one of these two things:
1. Somehow, mod_authnz_sspi is not compatible with Windows 2019.
2. Since my Windows 2019 server build is very fresh (not much software is on the virutal machine at this point) there is some third variable in play on the Windows 2012 system.  For instance, some other piece of software got installed that somehow enabled Apache to be able to load the module correctly.

I have no idea how to make progress with either theory.  Any advice that you (or anyone else) can give would be greatly appreciated.

Kind regards,

Pages: 1 2 [3] 4 5 ... 10