Comments on: Nginx Proxies with FirePHP

By: Matt Saunders

Matt Saunders — Sun, 21 Feb 2010 09:16:13 +0000

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:

fastcgi_buffer_size 16k;
fastcgi_buffers 4 16k;

By: britg

britg — Sat, 20 Jun 2009 18:30:22 +0000

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.

By: britg

britg — Sat, 20 Jun 2009 18:25:23 +0000

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!

By: nlsmith

nlsmith — Sat, 20 Jun 2009 09:38:46 +0000

Your last article talked about server-side js, you can use firephp on that, too: http://nlsmith.com/projects/console/ (and rails: http://github.com/smith/firephp_rails/tree/master)

I ran into the same type of bug on Jaxer and to a lesser degree, ASP.

I'm planning on making it Jack middleware, too.