Topic: mod_qos for Apache on Windows: Patch and build recipe

[rjung]

Hi there,

I managed to build mod_qos with a relatively simple code patch. I proposed the patch for inclusion in the upstreanm source code. Maybe it could be added to the modules ApacheLounge provides, once a mod_qos release includes that patch.

For details see:

https://sourceforge.net/p/mod-qos/bugs/41/

Another trivial patch is needed, which is good independent of the platform:

https://sourceforge.net/p/mod-qos/bugs/40/

Note: above links are not working (anymore).

Feedback welcome!

Rainer

[Steffen]

That is good news. We can add it.

Build with Visual Studio ?

Runs with PCRE2 ?

Let us know when it is included in the source code

[rjung]

Cool Steffen!

I did build it with the tools from Visual Studio latest but just used two command line calls for cl und link, which are generic fpr modules and which I have found in one of your forum threads:

set APACHE_HOME=C:\path\to\Apache24
set OPENSSL_HOME=C:\path\to\openssl-1.1.1m

cl -nologo -MD -W3 -O2 -c -DWIN32 -D_WINDOWS -DNDEBUG -I%APACHE_HOME%\include -I%OPENSSL_HOME%\include mod_qos.c

link /nologo /dll /subsystem:windows /machine:x64 /libpath:%APACHE_HOME%\lib kernel32.lib ws2_32.lib libhttpd.lib libapr-1.lib libaprutil-1.lib libssl.lib libcrypto.lib libpcre.lib /out:mod_qos.so mod_qos.obj

The Apache binary in APACHE_HOME was installed from an ApacheLounge download. OpenSSL and PCRE were compiled before, because ApacheLounge currently only provides httpd header files, but not the ones for OpenSSL and PCRE, and also not the needed library variants for linking.

Currently mod_qos does its own PCRE call, not via httpd. And they do not yet have support for PCRE2, but I guess that will be doable.

I will post again, once a release with the compatibility patch is out.

Thanks and regards,

Rainer

[Steffen]

With 2.4.53+ all is build with PCRE2. For third-party modules (like mod_security) that cannot build with pcre2, pcre.dll is in /bin

What about OpenSSL 3

Steffen

[rjung]

The module only uses very basic crypto functions from OpenSSL to encrypt and decrypt cookies used in optional features. It does compile and link fine against OpenSSL 1.1.1 and 3.0.0. Did not try others.

For PCRE it is currently limited to PCRE 1 (8.x) just like mod_security.

[rjung]

The new version 11.71 of mod_qos is out and it builds on Windows now out-of-the-box.

Here's my simple build recipe:

set APACHE_HOME=C:\path\to\Apache24
set OPENSSL_HOME=C:\path\to\openssl-1.1.1m
set PCRE_HOME=C:\path\to\pcre-win-build
set PCRE_BUILD=build-VS2022\x64\Release

cl -nologo -MD -W3 -O2 -c -DWIN32 -D_WINDOWS -DNDEBUG -I%OPENSSL_HOME%\include -I%PCRE_HOME%\include -I%APACHE_HOME%\include mod_qos.c

link /nologo /dll /subsystem:windows /machine:x64 /libpath:%OPENSSL_HOME%\lib /libpath:%PCRE_HOME%\%PCRE_BUILD% /libpath:%APACHE_HOME%\lib kernel32.lib ws2_32.lib libhttpd.lib libapr-1.lib libaprutil-1.lib libcrypto.lib pcre.lib /out:mod_qos.so mod_qos.obj

As already mentioned, compiling with OpenSSL 3.0 works as well, bur for PCRE it currently has to be PCRE 1 (8.x).

The include path for PCRE and OpenSSL is used to find pcre.h and the openssl header files openssl/rand.h, openssl/evp.h and openssl/hmac.h. The libpath for PCRE and OpenSSL finds pcre.lib and libcrypto.lib. AFAIK currently pcre and openssl header files are not bundled with the ApacheLounge httpd distribution. In addition for pcre and libcrypto only the dll files are bundled, not the "*.lib". That's why I had to first build PCRE and OpenSSL. If the header and lib files were included, one would just habve to issue the single cl and link command for the mod_qos module.

Thanks and regards!

Rainer

[Steffen]

Thank you !

Buid recipe looks fine.

First 2.4.53 and then I give it a try.

[rjung]

Cool!

For a very simple smoke test:

LoadModule qos_module modules/mod_qos.so
QS_LocRequestLimitDefault 2

That would limit the allowed concurrency to 2.
Now you can fire up ab: For example

ab -k -n 10000 -c 2 http://localhost:80

should show no error, but

ab -k -n 10000 -c 3 http://localhost:80

and

ab -k -n 100000 -c 50 http://localhost:80

should both show many errors.

After an ab run with high concurrency, another

ab -k -n 10000 -c 2 http://localhost:80

should again show no errors.

Adding

<Location /qos-status>
SetHandler qos-viewer
</Location>

shows some infos about mod_qos under the URI /qos-status.

[puertoblack2003]

can you suggest the best configuration for windows Apache server?

[Steffen]

Google gives some: