Re: mod_log-any/1908: %p in LogFormat isn't replaced with the right port (fwd)

[Dean Gaudet <dg...@arctic.org>]

mod_log_config doesn't use get_server_name or get_server_port. 

I can't seem imagine a situation where logging "%{HTTP_HOST}e" isn't
sufficient for those folks doing the wildcard vhost thing with mod_rewrite
and UseCanonicalName off.

So I think mod_log_config should be left alone. 

Dean

---------- Forwarded message ----------
Date: 3 Mar 1998 08:40:13 -0000
To: apache-bugdb@apache.org, dgaudet@apache.org, hs19@irz.inf.tu-dresden.de
From: dgaudet@hyperreal.org
Subject: Re: mod_log-any/1908: %p in LogFormat isn't replaced with the right port

[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]


Synopsis: %p in LogFormat isn't replaced with the right port

State-Changed-From-To: closed-analyzed
State-Changed-By: dgaudet
State-Changed-When: Tue Mar  3 00:40:13 PST 1998
State-Changed-Why:
A clear sign that I should just go to sleep right now.  I
changed my mind, and added this note to the mod_log_config
docs.  I'm putting this back to analysed for now in case
someone else disagrees with me.

Note that the canonical <a href="core.html#servername">ServerName</a>
and <a href="core.html#port">Port</a> of the server serving the request
are used for <code>%v</code> and <code>%p</code> respectively.  This
happens regardless of the
<a href="core.html#usecanonicalname">UseCanonicalName</a> setting because
otherwise log analysis programs would have to duplicate the entire
vhost matching algorithm in order to decide what host really served
the request.

Dean