Log4cxx
  1. Log4cxx
  2. LOGCXX-165

XMLSocketAppender may generate erroneous output due to mismatched encoding

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.9.7
    • Fix Version/s: 0.10.0
    • Component/s: Appender
    • Labels:
      None

      Description

      XMLSocketAppender in both 0.9.7 and 0.10.0 encode their output in the current default encoding. In the absence of an specified encoding in the XML declaration, a mismatch between the expected encoding (UTF-8) and actual encoding may result in non-well-formed XML content or otherwise corrupted XML content. The XMLSocketAppender does not appear to have an analog in log4j. It may be desirable to modify log4j's SocketAppender to support both Java serialization and XML encoding and then make log4cxx match the enhanced SocketAppender.

        Activity

        Hide
        Curt Arnold added a comment -

        Appears to be fixed in rev 600045. SocketAppender is now compatible with log4j format and XMLSocketAppender always uses UTF-8 encoding.

        Show
        Curt Arnold added a comment - Appears to be fixed in rev 600045. SocketAppender is now compatible with log4j format and XMLSocketAppender always uses UTF-8 encoding.

          People

          • Assignee:
            Curt Arnold
            Reporter:
            Curt Arnold
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development