<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>britg - Latest Comments in Nginx Proxies with FirePHP</title><link>http://britg.disqus.com/</link><description></description><atom:link href="https://britg.disqus.com/nginx_proxies_with_firephp/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Sun, 21 Feb 2010 04:16:13 -0000</lastBuildDate><item><title>Re: Nginx Proxies with FirePHP</title><link>http://britg.com/2009/06/16/nginx-proxies-with-firephp/#comment-35703895</link><description>&lt;p&gt;Hi, FYI this can also happen if you're not using nginx as a proxy but as a regular httpd, using fastcgi for PHP.  The fix is very similar - just add these lines to your nginx config file and adjust the sizes as necessary:&lt;/p&gt;&lt;p&gt;fastcgi_buffer_size 16k;&lt;br&gt;fastcgi_buffers 4 16k;&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matt Saunders</dc:creator><pubDate>Sun, 21 Feb 2010 04:16:13 -0000</pubDate></item><item><title>Re: Nginx Proxies with FirePHP</title><link>http://britg.com/2009/06/16/nginx-proxies-with-firephp/#comment-11499027</link><description>&lt;p&gt;And yes, I think Jack support is a great move for the project -- I think it'll find more adoption on Jack than Jaxer.  Nothing wrong with Jaxer, but I have a feeling that Jack will be widely adopted going forward just because of it's WSGI/Rack approach.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Sat, 20 Jun 2009 09:30:22 -0000</pubDate></item><item><title>Re: Nginx Proxies with FirePHP</title><link>http://britg.com/2009/06/16/nginx-proxies-with-firephp/#comment-11498943</link><description>&lt;p&gt;Very cool project you put together!  I will definitely give it a try -- I'm finding that I can't live without FirePHP now.  I'm sure that will carry over to my server-side JS projects and this sounds like the perfect solution.  Cheers!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Sat, 20 Jun 2009 09:25:23 -0000</pubDate></item><item><title>Re: Nginx Proxies with FirePHP</title><link>http://britg.com/2009/06/16/nginx-proxies-with-firephp/#comment-11493351</link><description>&lt;p&gt;Your last article talked about server-side js, you can use firephp on that, too: &lt;a href="http://nlsmith.com/projects/console/" rel="nofollow noopener" target="_blank" title="http://nlsmith.com/projects/console/"&gt;http://nlsmith.com/projects...&lt;/a&gt; (and rails: &lt;a href="http://github.com/smith/firephp_rails/tree/master)" rel="nofollow noopener" target="_blank" title="http://github.com/smith/firephp_rails/tree/master)"&gt;http://github.com/smith/fir...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;I ran into the same type of bug on Jaxer and to a lesser degree, ASP.&lt;/p&gt;&lt;p&gt;I'm planning on making it Jack middleware, too.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Nathan L Smith</dc:creator><pubDate>Sat, 20 Jun 2009 00:38:46 -0000</pubDate></item></channel></rss>