Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 99772 invoked from network); 20 Jun 2006 10:34:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 20 Jun 2006 10:34:22 -0000 Received: (qmail 58855 invoked by uid 500); 20 Jun 2006 10:34:14 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 58839 invoked by uid 500); 20 Jun 2006 10:34:14 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 58822 invoked by uid 99); 20 Jun 2006 10:34:14 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Jun 2006 03:34:14 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=RCVD_IN_BL_SPAMCOP_NET,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of ruchith.fernando@gmail.com designates 66.249.92.175 as permitted sender) Received: from [66.249.92.175] (HELO ug-out-1314.google.com) (66.249.92.175) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Jun 2006 03:34:13 -0700 Received: by ug-out-1314.google.com with SMTP id m3so2866192ugc for ; Tue, 20 Jun 2006 03:33:52 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ZFDLjbaYZ+R3fsnLyr7i/sZxyPkZJefcyl5m05x4XuI5Qe5gmtroqo1gP/xDUvtOXPewXaj54BSixBt6yd2HWEcKbXG/ivER+aebB/wbK1L7vAnNtsIDXZrHv9fJN2uOEDHQRfbpUmWuQXaVEthFwvk4AVRjAXMb2NIIBVEPDtU= Received: by 10.78.32.16 with SMTP id f16mr2583420huf; Tue, 20 Jun 2006 03:33:52 -0700 (PDT) Received: by 10.78.70.9 with HTTP; Tue, 20 Jun 2006 03:33:51 -0700 (PDT) Message-ID: <559c463d0606200333m3277e795o34eeb31fd31853c9@mail.gmail.com> Date: Tue, 20 Jun 2006 16:03:51 +0530 From: "Ruchith Fernando" To: axis-user@ws.apache.org, nzhang.ee@gmail.com Subject: Re: [Axis2] Will the engagement of Rampart module secure binary attachment sent using MTOM? In-Reply-To: <4496e44e.190e0787.3ec9.63d8@mx.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4496e44e.190e0787.3ec9.63d8@mx.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi Jenny, You should be able to secure MTOM messages using (engaging and configuring) Rampart but you will have to specify the "optimizeParts" configuration to MTOM optimize the base64 content after security processing. Note that the original MTOM attachments will appear as base64 text in place of the elements. Thanks, Ruchith On 6/19/06, Jenny ZHANG wrote: > Dear axis-userall, > > I am wondering if the engagement of Rampart module will secure binary attachment sent using MTOM? Thanks, > > Jenny > nzhang.ee@gmail.com > 2006-06-19 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-user-help@ws.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org For additional commands, e-mail: axis-user-help@ws.apache.org