You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Stewart Brodie <S....@ecs.soton.ac.uk> on 1997/09/10 16:00:03 UTC

mod_log-any/1112: Correction to PR #1111 - Suspected read through NULL pointer in logging

>Number:         1112
>Category:       mod_log-any
>Synopsis:       Correction to PR #1111 - Suspected read through NULL pointer in logging
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache (Apache HTTP Project)
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Sep 10 07:00:02 1997
>Originator:     S.N.Brodie@ecs.soton.ac.uk
>Organization:
apache
>Release:        1.2.4 (plus earlier 1.2 releases)
>Environment:
uname -a: SunOS mccarthy 4.1.2 2 sun4c
gcc --version:  2.7.2
>Description:
(This report supercedes PR #1111 was was accidentally submitted before it was completed - sorry)

When a completely empty request is received by Apache, log entries in both
access_log and error_log (in default configuration - it will affect any logging of the RequestLine) contain "rubbish" data - typically lots of character &FF data., although the data that is written will be OS dependent.
>How-To-Repeat:
Use 'telnet' to connect to the Apache server.  Once conected hit the intr key (^C usually).  Connection will close, both error_log & access_log will then contain the unexpected data
>Fix:
Trap these empty requests in the logging module to prevent that data being written to the log file, although it may be the case that it should be handled elsewhere if the logging modules is not the only one that assumes the request line was valid
>Audit-Trail:
>Unformatted: