https://issues.apache.org/bugzilla/show_bug.cgi?id=44765


Curt Arnold <[EMAIL PROTECTED]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




--- Comment #3 from Curt Arnold <[EMAIL PROTECTED]>  2008-08-12 14:42:43 PST ---
Tab characters are prohibited in the MESSAGE section of the packet (see
http://www.ietf.org/rfc/rfc3164.txt?number=3164) along with all other
non-printable characters.

The code fragment that is suggested to be changed does not appear in the
current SVN HEAD (and as far back as the fix for bug 40502) as I can tell.  The
current code is:

      String[] s = event.getThrowableStrRep();
      if (s != null) {
        for(int i = 0; i < s.length; i++) {
            if (s[i].startsWith("\t")) {
               sqw.write(hdr+TAB+s[i].substring(1));
            } else {
               sqw.write(hdr+s[i]);
            }
        }
      }

This should replace any leading tab in the stack trace with the value of
SyslogAppender.TAB (which is initialized at four spaces).

The current code does not address cases where non-printable characters appear
in other positions, but it does appear to do the best possible when the stack
trace starts with a single tab character (which is a common in mainstream
JVM's).  As far as I can tell, the behavior described in the bug report should
not occur with the current SVN head, and I'm going to mark the bug as INVALID. 
If I've misunderstood, please reopen after testing with the SVN HEAD and
providing a patch against the current SVN HEAD.


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to