Return-Path: X-Original-To: apmail-shindig-dev-archive@www.apache.org Delivered-To: apmail-shindig-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 03CCC952A for ; Thu, 26 Jan 2012 01:34:11 +0000 (UTC) Received: (qmail 38707 invoked by uid 500); 26 Jan 2012 01:34:10 -0000 Delivered-To: apmail-shindig-dev-archive@shindig.apache.org Received: (qmail 38654 invoked by uid 500); 26 Jan 2012 01:34:10 -0000 Mailing-List: contact dev-help@shindig.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@shindig.apache.org Delivered-To: mailing list dev@shindig.apache.org Received: (qmail 38645 invoked by uid 99); 26 Jan 2012 01:34:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jan 2012 01:34:09 +0000 X-ASF-Spam-Status: No, hits=0.9 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of rjbaxter@us.ibm.com does not designate 192.147.106.25 as permitted sender) Received: from [192.147.106.25] (HELO capricorn.lotus.com) (192.147.106.25) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jan 2012 01:34:05 +0000 In-Reply-To: References: To: dev@shindig.apache.org MIME-Version: 1.0 Subject: Re: Posting files through the shindig makeRequest proxy X-KeepSent: BEF01125:AAA8AA20-85257991:00088A92; type=4; name=$KeepSent X-Mailer: Lotus Notes Release 8.5.3NP September 15, 2011 From: "Ryan J Baxter" Message-ID: Date: Wed, 25 Jan 2012 20:31:46 -0500 X-MIMETrack: Serialize by Router on Capricorn/Iris(Build V853_08122011|August 12, 2011) at 01/25/2012 08:32:22 PM, Serialize complete at 01/25/2012 08:32:22 PM Content-Type: multipart/related; boundary="=_related 0008924E85257991_=" --=_related 0008924E85257991_= Content-Type: multipart/alternative; boundary="=_alternative 0008924E85257991_=" --=_alternative 0008924E85257991_= Content-Type: text/plain; charset="US-ASCII" Dan this might be of interest from a spec perspective... http://groups.google.com/group/opensocial-and-gadgets-spec/browse_thread/thread/cf1755fdaec6d5a0 Regards, RYAN J. BAXTER Software Engineer - OpenSocial IBM Collaboration Solutions Phone: 1-978-899-3041 E-mail: rjbaxter@us.ibm.com Blog: ryanjbaxter.com Chat: rbaxter85 ryanjasonbaxter Find me on: and within IBM on: 550 King St Littleton, MA 01460-1250 United States From: Dan Dumont/Westford/IBM@Lotus To: dev@shindig.apache.org, Date: 01/25/2012 06:01 PM Subject: Posting files through the shindig makeRequest proxy It looks like shindig has a pretty significant issue here in that posting file attachments through the proxy does not seem possible. >From what I've read online, passing a form element to a native xhr in FF and chrome will create a multipart mime post for you to the target. In IE you have to use a flash plugin or something. I think even supporting FF and Chrome would be an issue though, as we treat POST_DATA to the makeRequest call as a string... and osapi.http.post goes through RPC so that seems like it will be impossible to ever get to work posting binary data. Anyone have any ideas, or run into this before? --=_alternative 0008924E85257991_= Content-Type: text/html; charset="US-ASCII" Dan this might be of interest from a spec perspective...
http://groups.google.com/group/opensocial-and-gadgets-spec/browse_thread/thread/cf1755fdaec6d5a0

Regards,

RYAN J. BAXTER
Software Engineer - OpenSocial
IBM Collaboration Solutions


Phone: 1-978-899-3041 E-mail: rjbaxter@us.ibm.com Blog: ryanjbaxter.com Chat: rbaxter85 ryanjasonbaxter Find me on: and within IBM on:	550 King St Littleton, MA 01460-1250 United States

From: Dan Dumont/Westford/IBM@Lotus
To: dev@shindig.apache.org,
Date: 01/25/2012 06:01 PM
Subject: Posting files through the shindig makeRequest proxy

It looks like shindig has a pretty significant issue here in that posting file attachments through the proxy does not seem possible. >From what I've read online, passing a form element to a native xhr in FF and chrome will create a multipart mime post for you to the target. In IE you have to use a flash plugin or something. I think even supporting FF and Chrome would be an issue though, as we treat POST_DATA to the makeRequest call as a string... and osapi.http.post goes through RPC so that seems like it will be impossible to ever get to work posting binary data. Anyone have any ideas, or run into this before?
--=_alternative 0008924E85257991_=-- --=_related 0008924E85257991_=--