Hi, I am partially new to Apache but very new to Apache Haus.

I have worked briefly with Apache on Linux and it just seemed to work minimum hassle: Put your files into a folder and the server read them.

I'm trying to put together a light PHP server to test some code on Windows 10 and I'm having trouble finding where to put the files.

I have got Apache working and it loads localhost with the default /htdocs/index.html. I cracked open the /conf/httpd.conf as I've read that's where the server settings are set. I used [this tutorial][https://www.znetlive.com/blog/how-to-install-apache-php-and-mysql-on-windows-10-machine/] to setup the php. (instead of adding the PHP code, I uncommented the Include conf/extra/httpd-fcgid.conf and pointed the server to the php code in httpd-fcgid.conf)

My understanding is that in httpd.conf,DocumentRoot is where the server looks for folders and DirectoryIndex is where it sets the index.

So I thought I could add files to where DocumentRoot was looking , like having "~/htdocs/home.html" to load "localhost/home.html" or change DirectoryIndex in httpd.conf to look at a file called home.html instead of looking at index.html.

What I was expecting was to add something similar to DocumentRoot D:/www to httpd.conf and then just dropping my html files in there for the server to read.

I changed the "htdocs/index.html" to include the line "Hello World" and now the page won't load. I've re-extracted the httpd.conf from the downloaded file and replaced mine, and it's still not loading.

Is there a trick I'm missing here?

Trying to start Apache24 in services.msc gives me "Error 1067: The process terminated unexpectedly".

I have noticed that in services.msc windows has saved the "Path to executable:" as "D:\Apache24\bin\httpd.exe" -k runservice instead of using the command -k start. Don't know if that might be causing any issue.

---------------------------------------------------------------------------------------------------------
Edit:
Did a clean install, removed all files and all services and then reinstalled everything using apache commands. Removed environmental variables another tutorial suggested I include and it all seems to be working fine.

Loaded my files into /htdocs/ and they seem to load on the server now.

Only thing I haven't done yet is installed my php which I'm guessing is where the problem is...

---------------------------------------------------------------------------------------------------------
Edit:
From the sounds of Gregg's lament here it sounds like it's a headache along with MySQL...
https://forum.apachehaus.com/index.php?topic=117.0

----------------------------------------------------------------------------------------------------------
Edit:
And using this tut I managed to get my php to work.
https://danielarancibia.wordpress.com/2015/09/27/installing-apache-2-4-and-php-7-for-development-on-windows/

Now to try and get this damned contact form working...

I can send you my testogen review posted here recipe 
That looks to be 2.4.7 which came with OpenSSL 1.0.1e and there is a 1.0.1f update for it as well.

How is the last project i send you?

I think you are using wrong Javascript for web Development ?

Server side javasript or the M$ variant JScript was long used parallel to VBS. It still runs with Classic ASP on IIS.

Too bad that the example script is now kinda disabled in trunk :-/

I think you are using wrong Javascript for web Development ?

Solved 

For the benefit of those who may also have this dilemma, here's how I resolved this:

In my apache httpd-ssl.conf file:
1. I copied the existing Virtual Host block that I had created for mywebservername,com
2. In the new block I changed ServerName from mywebservername.com to niceURLgoeshere.com
3. In the new block I also set ProxPreserveHost Off
4. I restarted the Apache service, and I can now access my application using the niceURLgoeshere.com URL

I've kept the existing Virtual Host block in my httpd-ssl.conf file so that I have (for now) a 'backdoor' to the application.

Please bear with me - I'm a newbie to TomCat & Apache.
I've built a web server using TomCat 9, with Apache 2.4 as the front-end.  I can access my application with no issues using https://mywebservername.com/apps/f?p=myapp
My boss now wants to hide the web server behind another server (for security).  Users will access my application by typing in https://niceURLgoeshere.com/apps/f?p=myapp - this will take them to the new server which will forward requests to my web server.
If I type in https://niceURLgoeshere.com I reach the Tomcat front page (which is as I expect).  However, if I type in https://niceURLgoeshere.com/apps/f?p=myapp I get "can't find this page".
I've looked through the log files, that suggest that the request is being passed on by Apache, but then hitting a brick wall when it reaches TomCat (I can't see anything in the logs that points to an error, entries just seem to stop when the request reaches TomCat).  I've tried searching the internet for clues/pointers, but I'm now confused as to what I should be doing to get the new URL to work. Do I use proxy? proxy_html? proxypass? redirect? something else I haven't heard of yet?
Can someone point me in the right direction please?  (Please bear in mind I have no experience of Apache or TomCat, so keep your replies as jargon-free as possible )

Without much fanfare, both the OpenSSL and LibreSSL releases have been updated.

I've had the LibreSSL releases a few weeks and lagged on getting them out with all the fires around this area.
Now is as good a time as any to put them up.

Changes:

 Changes between OpenSSL 1.1.1g and 1.1.1h [22 Sep 2020]

  *) Certificates with explicit curve parameters are now disallowed in
     verification chains if the X509_V_FLAG_X509_STRICT flag is used.
     [Tomas Mraz]

  *) The 'MinProtocol' and 'MaxProtocol' configuration commands now silently
     ignore TLS protocol version bounds when configuring DTLS-based contexts, and
     conversely, silently ignore DTLS protocol version bounds when configuring
     TLS-based contexts.  The commands can be repeated to set bounds of both
     types.  The same applies with the corresponding "min_protocol" and
     "max_protocol" command-line switches, in case some application uses both TLS
     and DTLS.
 
     SSL_CTX instances that are created for a fixed protocol version (e.g.
     TLSv1_server_method()) also silently ignore version bounds.  Previously
     attempts to apply bounds to these protocol versions would result in an
     error.  Now only the "version-flexible" SSL_CTX instances are subject to
     limits in configuration files in command-line options.
     [Viktor Dukhovni]

  *) Handshake now fails if Extended Master Secret extension is dropped
     on renegotiation.
     [Tomas Mraz]

  *) The Oracle Developer Studio compiler will start reporting deprecated APIs


Changes between LibreSSL 3.1.3 and 3.1.4  [17 Aug 2020]


    * Improve client certificate selection to allow EC certificates
      instead of only RSA certificates.

    * Do not error out if a TLSv1.3 server requests an OCSP response as
      part of a certificate request.

    * Fix SSL_shutdown behavior to match the legacy stack.  The previous
      behaviour could cause a hang.

    * Fix a memory leak and add a missing error check in the handling of
      the key update message.

    * Fix a memory leak in tls13_record_layer_set_traffic_key.

    * Avoid calling freezero with a negative size if a server sends a
      malformed plaintext of all zeroes.

    * Ensure that only PSS may be used with RSA in TLSv1.3 in order
      to avoid using PKCS1-based signatures.

    * Add the P-521 curve to the list of curves supported by default
      in the client.


As always, you can get your copy of the updated Apache HTTP Server from our download page.

I'll try this. Sounds pretty cool

Do you believe the KeepAlive would keep the worker busy?

Hi Max,
that can be an option why it is that way.

Do you believe the KeepAlive would keep the worker busy?

Yeah, I'll test the logging on our test server.

Max