>Number: 4744 >Category: mod_status >Synopsis: Visiting server-status logs the hostname of the client >regardless of HostnameLookup. >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Tue Jul 20 09:40:02 PDT 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.6 >Environment: SunOS pubserv 5.5.1 Generic_103640-24 sun4m sparc sun4m >Description: I don't want hostnames resolved for the access log, so I commented out the default 'HostnameLookup on' line (I also tried changing on to off). This works fine for general hits to the server, but any access of /server-status/ (using mod_status) causes a lookup:
199.172.48.67 - - [20/Jul/1999:12:27:33 -0400] "GET / HTTP/1.0" 200 7320 kenny.chrysalis.com - - [20/Jul/1999:12:27:43 -0400] "GET /server-status/ HTTP/1.0" 200 2591 >How-To-Repeat: Configure mod_status to be used for some URL, and turn hostnamelookup off. Visit the status page, and any other URL on the same server. >Fix: >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include <[EMAIL PROTECTED]> in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]