By late 2015, the web was undergoing significant changes. HTTP/2 was on the horizon, TLS (Transport Layer Security) was becoming mandatory for serious web applications, and the demand for asynchronous processing was growing.
Running Apache 2.4.18 in a production environment today is dangerous. As a legacy version, it does not receive patches for vulnerabilities discovered after 2015. Here are some critical vulnerabilities that affect this version (or were fixed shortly after): apache 2.4.18
Apache 2.4.18 was a solid, stable release for its time. It bridged the gap between the old web (HTTP/1.1) and the new web (HTTP/2). It offered better proxying, better authentication controls, and early HTTP/2 support. By late 2015, the web was undergoing significant changes
I can provide custom-tailored configuration blocks or upgrade scripts. By late 2015