Comments on: Lighttpd and Ruby on Rails: Secure and Fast Downloading http://johnleach.co.uk/words/213/lighttpd-and-ruby-on-rails-secure-and-fast-downloading Stuff I think, see and do Mon, 14 May 2012 20:40:50 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: glen http://johnleach.co.uk/words/213/lighttpd-and-ruby-on-rails-secure-and-fast-downloading/comment-page-1#comment-17971 glen Fri, 17 Aug 2007 07:56:22 +0000 http://johnleach.co.uk/words/archives/2006/03/16/213/#comment-17971 Richard, at first time when accelerator asks file from backend (no cached copy present) the backend is busy sending file to lighty while this can be avoided using either the techniques. for example: you're serving 150mb file. your php-fcgi backend one process is buzy for ~45min. Richard, at first time when accelerator asks file from backend (no cached copy present) the backend is busy sending file to lighty while this can be avoided using either the techniques. for example: you’re serving 150mb file. your php-fcgi backend one process is buzy for ~45min.

]]> By: David http://johnleach.co.uk/words/213/lighttpd-and-ruby-on-rails-secure-and-fast-downloading/comment-page-1#comment-3934 David Tue, 11 Jul 2006 08:38:11 +0000 http://johnleach.co.uk/words/archives/2006/03/16/213/#comment-3934 Great article, thanks. I am using a very similar helper and have configured lighttpd with the 4 parameters. However, I get a routing recognition error from rails. Should I be doing something magic with the routing, or is there a problem with lighttpd? Great article, thanks. I am using a very similar helper and have configured lighttpd with the 4 parameters. However, I get a routing recognition error from rails.

Should I be doing something magic with the routing, or is there a problem with lighttpd?

]]> By: Richard Jones http://johnleach.co.uk/words/213/lighttpd-and-ruby-on-rails-secure-and-fast-downloading/comment-page-1#comment-623 Richard Jones Sat, 25 Mar 2006 21:19:17 +0000 http://johnleach.co.uk/words/archives/2006/03/16/213/#comment-623 I'd say that this is better solved using a web accelerator - a proxy sitting in front of the web server which sucks up the file and streams it slowly back to the user allowing the expensive web server to handle the next request. Rich. I’d say that this is better solved using a web accelerator – a proxy sitting in front of the web server which sucks up the file and streams it slowly back to the user allowing the expensive web server to handle the next request.

Rich.

]]>