<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Upload a photo from iphone with 64 encoding multi part form data</title>
	<atom:link href="http://www.wetware.co.nz/2009/03/upload-a-photo-from-iphone-64-encoding-multi-part-form-data/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.wetware.co.nz/2009/03/upload-a-photo-from-iphone-64-encoding-multi-part-form-data/</link>
	<description>Getting computers to do stuff so we don&#039;t have too</description>
	<lastBuildDate>Tue, 17 Jan 2012 22:29:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Matt</title>
		<link>http://www.wetware.co.nz/2009/03/upload-a-photo-from-iphone-64-encoding-multi-part-form-data/comment-page-1/#comment-3505</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Wed, 11 May 2011 16:24:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.wetware.co.nz/blog/?p=69#comment-3505</guid>
		<description>This post helped a lot connecting an iPhone to a Ruby server. One thing I did have to do differently was change:

&quot;Content-Type: image/jpg
&quot;

to

&quot;Content-Type: image/jpeg
&quot;

Thanks!</description>
		<content:encoded><![CDATA[<p>This post helped a lot connecting an iPhone to a Ruby server. One thing I did have to do differently was change:</p>
<p>&#8220;Content-Type: image/jpg<br />
&#8221;</p>
<p>to</p>
<p>&#8220;Content-Type: image/jpeg<br />
&#8221;</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tewks</title>
		<link>http://www.wetware.co.nz/2009/03/upload-a-photo-from-iphone-64-encoding-multi-part-form-data/comment-page-1/#comment-1911</link>
		<dc:creator>tewks</dc:creator>
		<pubDate>Thu, 30 Jul 2009 14:19:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.wetware.co.nz/blog/?p=69#comment-1911</guid>
		<description>cheers for this</description>
		<content:encoded><![CDATA[<p>cheers for this</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Lachman</title>
		<link>http://www.wetware.co.nz/2009/03/upload-a-photo-from-iphone-64-encoding-multi-part-form-data/comment-page-1/#comment-1355</link>
		<dc:creator>Ben Lachman</dc:creator>
		<pubDate>Thu, 18 Jun 2009 07:51:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.wetware.co.nz/blog/?p=69#comment-1355</guid>
		<description>I think this is a bug with Ruby&#039;s multi part parser.  PERL will handle the leading &#039;\r\n&#039; just fine and the RFC on the topic (2046) states: 

&#039;The boundary delimiter MUST occur at the beginning of a line, i.e., following a CRLF, and the initial CRLF is considered to be attached to the boundary delimiter line rather than part of the preceding part.  The boundary may be followed by zero or more characters of linear whitespace. It is then terminated by either another CRLF and the header fields for the next part, or by two CRLFs, in which case there are no header fields for the next part.&#039;

e.g. it is correct to have that \r\n at the beginning of the boundary line.</description>
		<content:encoded><![CDATA[<p>I think this is a bug with Ruby&#8217;s multi part parser.  PERL will handle the leading &#8216;\r\n&#8217; just fine and the RFC on the topic (2046) states: </p>
<p>&#8216;The boundary delimiter MUST occur at the beginning of a line, i.e., following a CRLF, and the initial CRLF is considered to be attached to the boundary delimiter line rather than part of the preceding part.  The boundary may be followed by zero or more characters of linear whitespace. It is then terminated by either another CRLF and the header fields for the next part, or by two CRLFs, in which case there are no header fields for the next part.&#8217;</p>
<p>e.g. it is correct to have that \r\n at the beginning of the boundary line.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arrel</title>
		<link>http://www.wetware.co.nz/2009/03/upload-a-photo-from-iphone-64-encoding-multi-part-form-data/comment-page-1/#comment-1343</link>
		<dc:creator>Arrel</dc:creator>
		<pubDate>Thu, 18 Jun 2009 02:16:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.wetware.co.nz/blog/?p=69#comment-1343</guid>
		<description>....er, and it did it in my comment, too.</description>
		<content:encoded><![CDATA[<p>&#8230;.er, and it did it in my comment, too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arrel</title>
		<link>http://www.wetware.co.nz/2009/03/upload-a-photo-from-iphone-64-encoding-multi-part-form-data/comment-page-1/#comment-1342</link>
		<dc:creator>Arrel</dc:creator>
		<pubDate>Thu, 18 Jun 2009 02:15:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.wetware.co.nz/blog/?p=69#comment-1342</guid>
		<description>One problem I rant into, the browser is converting the double dash before the boundary into an mdash:
@&quot;–%@\r\n&quot; instead of
@&quot;--%@\r\n&quot;

Changing that got it working.  Thanks!</description>
		<content:encoded><![CDATA[<p>One problem I rant into, the browser is converting the double dash before the boundary into an mdash:<br />
@&#8221;–%@\r\n&#8221; instead of<br />
@&#8221;&#8211;%@\r\n&#8221;</p>
<p>Changing that got it working.  Thanks!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

