The Apache Haus Forum

Advanced search  


Welcome to Apache Haus Distribution Forum

Pages: [1] 2 3 ... 10
 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 gmail sign up 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,

 on: May 26, 2020, 10:49:14 AM 
Started by shishir - Last post by mario
Yes, you find it here
But now it is a much fresher OpenSSL Version  ;)

 on: May 26, 2020, 10:46:22 AM 
Started by shishir - Last post by juankax
hi! i am also looking for new updates.

porno gratis free porn porno sex webcam

 on: May 26, 2020, 10:17:03 AM 
Started by youngpee0110 - Last post by robincortez
This is a good question, the problem is a pain in the back side. I have to credit mario for the answer.

1. Put a copy of your patch.exe file into a folder somewhere.
2. Create a text file named patch.exe.manifest and add the below and code to it modifying the version to match yours. Save it in the folder you put patch.exe in.

Code: [Select]
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
<description> A tool for applying diff-generated patches. </description>
<!-- Identify the application security requirements. -->
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">

3. Open a Visual Studio x86 command window and cd to the folder you put patch.exe and patch.exe.manifest in.
4. Run this command
Code: [Select]
  mt -manifest patch.exe.manifest -outputresource:patch.exe;1  5. Test it on something, it should never ask again or at least mine doesn't.

Thanks. It works just fine now.

 on: May 25, 2020, 10:24:19 PM 
Started by jleveille1337 - Last post by jleveille1337
Thanks Gregg.  However, something doesn't add up here.  On a separate machine at work, one of my team members got this working.  He was running Windows 2012, not 2019 like I am.  He was also running a system with, perhaps, some slightly different software packages on it.  I am really bothered by not understanding how this fresh build could fail on me while he was able to make that other setup work.

Before you go digging for old stuff - how about I check in with him tomorrow at work and try to dig into that other virtual machine and see if I can figure out how it is working for him?

I suppose the best way for me to compare the systems is to look at his setup and see what msvcr version he has in the Apache bin folder, eh?


Pages: [1] 2 3 ... 10