Linux – apache CustomLog with multiple env

apache-2.4httpdlinux

I have 2 CustomLog statements:

# SVN-ACTION is default env
CustomLog logs/svn_access_log common env=SVN-ACTION
SetEnvIf Request_Method GET GET-ACTION
CustomLog logs/get_access_log common env=GET-ACTION

That works, but the CustomLog statement below doesn't work… it prints an error:

CustomLog logs/ssl_access_log common env=!GET-ACTION env=!SVN-ACTION

How can I use multiple env conditions in CustomLog?

Best Answer

use this:

CustomLog logs/ssl_access_log common \ "expr=(-z reqenv('GET-ACTION') && -z reqenv('SVN_ACTION'))"

the whole third argument seems to need double quotes. quoting right-side of "=" only is not enough.

syntax tested with version 2.4.34.

Update:

Without more information about your backup cron job, my only other suggestion is to redirect the output of the command to a file (or let cron capture it in email) and the output of the ssh session to /dev/null. Something like:

0 0 * * * ssh backuphost "backup_script_that_writes_to_a_log" >/dev/null

0 0 * * * ssh backuphost "backup_command 2>&1" >/dev/null

I'd have to play around with the commands a bit, but that should get you started.

Linux – Preventing an Apache 2 Server from Logging Sensitive Data

Apache 2 by default logs the entire request URI including query string of every request.

What is a straight forward way to prevent an Apache 2 web server from logging sensitive data, for example passwords, credit card numbers, etc., but still log the rest of the request?

Am I reading right, that you are sending sensitive information in URI as QueryString ? I would suggest changing the application so it does do so in the first place.

Then, there would be no requirement to change apache, since, it does not do any such thing by default.

Best Answer

Related Solutions

SSH Login – Stop Printing MOTD from the Client

Update:

Linux – Preventing an Apache 2 Server from Logging Sensitive Data

Related Topic