Yes, I did see that page. It's what prompted my question to this list. It indicates the use of a local webserver, but says nothing about the needed functionality on that web server which, in Apache, manifest as modules outside the core and MPM functionality present on every Apache httpd server.
For example, the solution proposed in section 2 says to let FreshClam download the *.cvd files to the webserver's DocumentRoot. If the clients directed to use a private local mirror are instructed to do the same thing, that becomes a problem because there's no way in HTTP to retrieve a wildcard. That's why sites have index pages either explicitly created or automatically generated by a piece of server code like mod_autoindex.
None of this is a problem if the client knows exactly what files it's going to request and in that case only core and MPM functionality is required which is a perfectly valid answer to my question, but the LPM page doesn't get into that level of detail which is why I posted to the list.
Thanks,
Scott
-----------------------------------
Hi there,
On Sun, 22 Sep 2019, Scott A. Wozny via clamav-users wrote:
> Does anyone know what Apache modules (beyond the Core and the
> appropriate Multi-Processing Module) are needed for a ClamAV private
> local mirror to work properly? For example, does Freshclam rely on
> mod_autoindex on the mirror to get a list of available files or does
> it already know what it expects and just asks for the file(s) it
> needs? Is there anything Apache needs to do with the content other
> than serve files the FreshClam instance requests (which it would
> need a PHP / CGI / etc... engine for)?
>
> Any thoughts or suggestions would be appreciated.
Did you see
https://www.clamav.net/documents/private-local-mirrors ?
--
73,
Ged.
________________________________