Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5BC0BECB3 for ; Tue, 29 Jan 2013 01:26:12 +0000 (UTC) Received: (qmail 67571 invoked by uid 500); 29 Jan 2013 01:26:12 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 67526 invoked by uid 500); 29 Jan 2013 01:26:12 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 67414 invoked by uid 99); 29 Jan 2013 01:26:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Jan 2013 01:26:12 +0000 Date: Tue, 29 Jan 2013 01:26:12 +0000 (UTC) From: "chenwei (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CXF-4785) in AttachmentSerializer, content-transfer-encoding can only be binary MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CXF-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13564956#comment-13564956 ] chenwei commented on CXF-4785: ------------------------------ Thanks, I will . > in AttachmentSerializer, content-transfer-encoding can only be binary > --------------------------------------------------------------------- > > Key: CXF-4785 > URL: https://issues.apache.org/jira/browse/CXF-4785 > Project: CXF > Issue Type: Bug > Components: Core > Reporter: chenwei > > AttachmentSerializer line 197: > writer.write("Content-Transfer-Encoding: binary\r\n"); > why Content-Transfer-Encoding cannot be "base64" or "7bit"? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira