<?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: Nginx &amp; Django on Webfaction &#8211; Part 3</title>
	<atom:link href="http://fightingrabbits.com/archives/210/feed" rel="self" type="application/rss+xml" />
	<link>http://fightingrabbits.com/archives/210</link>
	<description>and herding cats...</description>
	<lastBuildDate>Tue, 06 Jul 2010 10:56:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: Passy</title>
		<link>http://fightingrabbits.com/archives/210/comment-page-1#comment-4879</link>
		<dc:creator>Passy</dc:creator>
		<pubDate>Thu, 17 Jun 2010 12:24:39 +0000</pubDate>
		<guid isPermaLink="false">http://fightingrabbits.com/?p=210#comment-4879</guid>
		<description>Excellent post, exactly what I was searching for. Thanks for sharing!</description>
		<content:encoded><![CDATA[<p>Excellent post, exactly what I was searching for. Thanks for sharing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gordon</title>
		<link>http://fightingrabbits.com/archives/210/comment-page-1#comment-3346</link>
		<dc:creator>Gordon</dc:creator>
		<pubDate>Mon, 22 Feb 2010 07:36:31 +0000</pubDate>
		<guid isPermaLink="false">http://fightingrabbits.com/?p=210#comment-3346</guid>
		<description>I’m trying to setup an upload progress bar using Nginx with Passenger and Rails on WebFaction. The problem I’m having is that it reports as &quot;starting&quot; for the duration of the upload, then jumps the progress bar to 100% for a split second at the end of the upload. I’ve tried asking the WebFaction guys for help, also Stack Overflow and googling around, but did not get anywhere. I realize that it may be the different technologies in use that are causing my problems eg not using fastcgi, passenger, etc. but i was just wondering if you had thoughts on if there might be any salient details I might be missing. 

This is the conf file I have currently:
http://pastie.org/836127 

Any advice would be much appreciate!</description>
		<content:encoded><![CDATA[<p>I’m trying to setup an upload progress bar using Nginx with Passenger and Rails on WebFaction. The problem I’m having is that it reports as &#8220;starting&#8221; for the duration of the upload, then jumps the progress bar to 100% for a split second at the end of the upload. I’ve tried asking the WebFaction guys for help, also Stack Overflow and googling around, but did not get anywhere. I realize that it may be the different technologies in use that are causing my problems eg not using fastcgi, passenger, etc. but i was just wondering if you had thoughts on if there might be any salient details I might be missing. </p>
<p>This is the conf file I have currently:<br />
<a href="http://pastie.org/836127" rel="nofollow">http://pastie.org/836127</a> </p>
<p>Any advice would be much appreciate!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Schenck</title>
		<link>http://fightingrabbits.com/archives/210/comment-page-1#comment-2540</link>
		<dc:creator>Ian Schenck</dc:creator>
		<pubDate>Mon, 11 Jan 2010 07:13:18 +0000</pubDate>
		<guid isPermaLink="false">http://fightingrabbits.com/?p=210#comment-2540</guid>
		<description>Actually, I just had to move away from Cherokee because it both caches the upload and doesn&#039;t have any replacement such as Nginx&#039;s upload progress module.

There is an open ticket and the Cherokee guys are aware of it.  If it wasn&#039;t for this issue (admittedly, combined with some laziness), I&#039;d still be using it.</description>
		<content:encoded><![CDATA[<p>Actually, I just had to move away from Cherokee because it both caches the upload and doesn&#8217;t have any replacement such as Nginx&#8217;s upload progress module.</p>
<p>There is an open ticket and the Cherokee guys are aware of it.  If it wasn&#8217;t for this issue (admittedly, combined with some laziness), I&#8217;d still be using it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Cooper</title>
		<link>http://fightingrabbits.com/archives/210/comment-page-1#comment-2488</link>
		<dc:creator>Richard Cooper</dc:creator>
		<pubDate>Fri, 08 Jan 2010 10:19:19 +0000</pubDate>
		<guid isPermaLink="false">http://fightingrabbits.com/?p=210#comment-2488</guid>
		<description>Nginx was specifically designed to move work away from the back end process and thus the core Nginx sever does this caching. I believe that the author Igor is now considering changing this and adding a server directive to allow you to bypass the proxy/caching of uploads. In the meantime you could write (or get someone to write) an upload passthrough module. I suggest you ask this question on the &lt;a href=&quot;http://forum.nginx.org/list.php?2&quot; rel=&quot;nofollow&quot;&gt;Nginx mailing list&lt;/a&gt; to find out a timeline for this from Igor.

If this is complete blocker for you then I suggest you stick with apache or consider something like &lt;a href=&quot;http://www.lighttpd.net/&quot; rel=&quot;nofollow&quot;&gt;lighttpd&lt;/a&gt; or &lt;a href=&quot;http://www.cherokee-project.com/&quot; rel=&quot;nofollow&quot;&gt;cherokee&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Nginx was specifically designed to move work away from the back end process and thus the core Nginx sever does this caching. I believe that the author Igor is now considering changing this and adding a server directive to allow you to bypass the proxy/caching of uploads. In the meantime you could write (or get someone to write) an upload passthrough module. I suggest you ask this question on the <a href="http://forum.nginx.org/list.php?2" rel="nofollow">Nginx mailing list</a> to find out a timeline for this from Igor.</p>
<p>If this is complete blocker for you then I suggest you stick with apache or consider something like <a href="http://www.lighttpd.net/" rel="nofollow">lighttpd</a> or <a href="http://www.cherokee-project.com/" rel="nofollow">cherokee</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Gollás</title>
		<link>http://fightingrabbits.com/archives/210/comment-page-1#comment-2484</link>
		<dc:creator>Daniel Gollás</dc:creator>
		<pubDate>Fri, 08 Jan 2010 03:40:52 +0000</pubDate>
		<guid isPermaLink="false">http://fightingrabbits.com/?p=210#comment-2484</guid>
		<description>I spent a day implementing a custom UploadHandler in django only to find out that it won&#039;t really work with an nginx proxy since it will not stream the upload but instead cache it until it is complete... so is nginx progress module the only way to get progress? Do you know if there is a way to get nginx to actually send me (django upload handler) chunks of data as they arrive? 

The progress module is great for progress reporting but what if I want to do something a little more customized to my data as it arrives? I think it falls a little short.</description>
		<content:encoded><![CDATA[<p>I spent a day implementing a custom UploadHandler in django only to find out that it won&#8217;t really work with an nginx proxy since it will not stream the upload but instead cache it until it is complete&#8230; so is nginx progress module the only way to get progress? Do you know if there is a way to get nginx to actually send me (django upload handler) chunks of data as they arrive? </p>
<p>The progress module is great for progress reporting but what if I want to do something a little more customized to my data as it arrives? I think it falls a little short.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Cooper</title>
		<link>http://fightingrabbits.com/archives/210/comment-page-1#comment-1284</link>
		<dc:creator>Richard Cooper</dc:creator>
		<pubDate>Fri, 30 Oct 2009 22:11:13 +0000</pubDate>
		<guid isPermaLink="false">http://fightingrabbits.com/?p=210#comment-1284</guid>
		<description>Thanks, 
        I&#039;ve updated the title, and I&#039;m glad you like the post.

Regards,
Richard.</description>
		<content:encoded><![CDATA[<p>Thanks,<br />
        I&#8217;ve updated the title, and I&#8217;m glad you like the post.</p>
<p>Regards,<br />
Richard.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mauricio Q.</title>
		<link>http://fightingrabbits.com/archives/210/comment-page-1#comment-1283</link>
		<dc:creator>Mauricio Q.</dc:creator>
		<pubDate>Fri, 30 Oct 2009 22:00:58 +0000</pubDate>
		<guid isPermaLink="false">http://fightingrabbits.com/?p=210#comment-1283</guid>
		<description>Great Article. As a minor comment, you HTML title text says &quot;dajngo&quot; instead of &quot;django&quot; that probably affects search engine indexing bla bla...

Thanks again for this post.</description>
		<content:encoded><![CDATA[<p>Great Article. As a minor comment, you HTML title text says &#8220;dajngo&#8221; instead of &#8220;django&#8221; that probably affects search engine indexing bla bla&#8230;</p>
<p>Thanks again for this post.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
