Apache 1.3.37 not logging 404 errors

Question

While attempting to diagnose another issue (which I asked about over here), I discovered that the apache 1.3.37 installation on a machine I inherited doesn't log 404 errors to error_log. I've scoured the config files for CustomLog and ErrorLog directives, but they're all just the standard 'set a path and (for CustomLog) combined format' type.

It does log other errors normally, such as 'Permission denied', but 404s are silently ignored.

What might be causing this and how can I get the 404s to appear (at least temporarily)?

@Nifle: Yes, the request shows in access_log with a 404 status. — Dave Sherohman, Jan 02 '12 at 15:30

udo · Answer 1 · 2012-01-02T15:59:50.443

1

maybe the CustomLog directive is configured (also check .htaccess files) which excludes 404s.

edited Jan 02 '12 at 15:59

answered Jan 02 '12 at 15:29

udo

8,001
7
38
47

score 0 · Accepted Answer · edited Mar 20 '17 at 10:16

It turned out that the context of the original issue was relevant here - the problem URL contained the sequence %2F (a URI-encoded forward slash). In an attempt to protect security-oblivious CGI programmers from their own ignorance, apache immediately rejects (as 404 Not found) any requested URL which contains that sequence at a very early stage in the request-handling process, which apparently bypasses any writes to error_log.

Apache 1.3.37 not logging 404 errors

2 Answers2