You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Douglas Hall <do...@uk.psi.com> on 1999/02/04 22:51:54 UTC

mod_log-any/3839: documentation implies environment variables should be in upper case in logformat directive

>Number:         3839
>Category:       mod_log-any
>Synopsis:       documentation implies environment variables should be in upper case in logformat directive
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Feb  4 15:10:01 PST 1999
>Last-Modified:
>Originator:     doug@uk.psi.com
>Organization:
apache
>Release:        1.3.4
>Environment:
SunOS dev.sa.uk.psi.com 5.5.1 Generic_103640-24 sun4m sparc SUNW,SPARCstation-20

Reading specs from /opt/PSIgcc/lib/gcc-lib/sparc-sun-solaris2.5.1/2.8.0/specs
gcc version 2.8.0

>Description:
If i specify %{Server_Name}e in a logformat directive, I get the appropriate
output in the logfile, but if I use %{SERVER_NAME}, then only a - is generated.

This appears to be the case for any other environment variable I have tried.

The documentation seems to imply that environment variables should be
in uppercase (e.g. http://www.apache.org/docs/mod/mod_log_config.html#formats):
%...{FOOBAR}e:  The contents of the environment variable FOOBAR

Also, the output from /cgi-bin/printenv (as supplied with the apache
distribution), prints all environment variables in uppercase.

but apache seems to work otherwise.

Am I missing something here?
>How-To-Repeat:
Try logging environment variables in the logformat directive, and see if
you get output if the variable is specified in uppercase.

>Fix:
Amend the documentation or code, or don't make case sensitive?
>Audit-Trail:
>Unformatted:
[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. ]
[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!         ]