> >
> > [1]
> > https://httpd.apache.org/docs/current/mod/mod_log_config.html
> >
> > [2]
> > https://httpd.apache.org/docs/current/mod/mod_log_config.html#formats
>
> You could also use
> https://httpd.apache.org/docs/current/mod/mod_lua.html#luahooklog to
> split up your logs or discard/silence
On 4/10/24 07:22, Marc wrote:
Oops I was mislead by some old posts. GlobalLog[1] does this for everything.
However I have not found what value[2] has the requested virtual host name.
[1]
https://httpd.apache.org/docs/current/mod/mod_log_config.html
[2]
https://httpd.apache.org/docs/current/mo
%v sorry for polluting this list
PS. If it is any consolation, I have registered myself at a retirement home
> -Original Message-
> From: Marc
> Sent: Wednesday, 10 April 2024 14:22
> To: users@httpd.apache.org
> Subject: [users@httpd] RE: pipe logs to somethings that resembles a curl
>
Oops I was mislead by some old posts. GlobalLog[1] does this for everything.
However I have not found what value[2] has the requested virtual host name.
[1]
https://httpd.apache.org/docs/current/mod/mod_log_config.html
[2]
https://httpd.apache.org/docs/current/mod/mod_log_config.html#formats
Currently I have modified some rust application that does this to satisfaction.
But piping to a 60MB binary for quite a few virtual hosts does not really seem
efficient to me.
Is there not some apache module that can offer a "global" access to logging and
'clones' all logging to some tcp socket
