Bug 62724 - Custom log omits "/" requests
Summary: Custom log omits "/" requests
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Runtime Config (show other bugs)
Version: 2.4.29
Hardware: PC All
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Depends on:
Reported: 2018-09-15 05:04 UTC by joshk03
Modified: 2018-09-15 19:36 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description joshk03 2018-09-15 05:04:29 UTC
Apache/2.4.29 (Ubuntu) OpenSSL/1.1.0g configured

I have setup a simple custom log file, but it skips logging requests to the homepage. I tried log type common, combined, custom, the issue persists. Here are some entries from the access.log that are omitted from the custom log: - - [14/Sep/2018:23:05:31 -0500] "GET / HTTP/1.1" 403 160 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/601.7.7 (KHTML, like Gecko) Version/9.1.2 Safari/601.7.7" - - [14/Sep/2018:23:10:18 -0500] "GET / HTTP/1.1" 403 160 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36"

Nevermind the 403 forbidden status, that covers the whole site at the moment.
Comment 1 joshk03 2018-09-15 05:08:11 UTC
PS - I do not have this issue on my Ubuntu 16.04 system last I checked.
The bug is on my 18.04 system.

Apache/2.4.29 (Ubuntu) OpenSSL/1.1.0g configured
Comment 2 Eric Covener 2018-09-15 10:36:02 UTC
What's the vhost config? Tested w/ a command-line client?
Comment 3 joshk03 2018-09-15 15:12:17 UTC
Well this is unconfirmed... and a little embarrassing.  The server 16.04 server I borrowed from has an exclusion that I suspect is the issue.  If I recall correctly this exclusion was to clean up some ownCloud local traffic from the logs.  The behavior must be different between the server?

SetEnvIf Request_URI "/$" bor

CustomLog ${APACHE_LOG_DIR}/public.log common env=!bor

Comment 4 joshk03 2018-09-15 19:36:36 UTC
I have confirmed that was the issue.  In my defense I re-purposed the "bor" env to clean up the logs on this server, but didn't notice that "/$" statement buried in the other statements.

Status: Resolved/Invalid.