similar to: Lighttpd + Mongrel Upload Progress Problem

Hi guys, I''ve been chasing a problem in my web-stack: Lighttpd -> Mongrel -> Rails, and found a problem with the interaction of Lighttpd and Mongrel. If a request takes more than 5 seconds, Lighty will retry it - and then the requests / responses get mixed up in Lighty and it returns a bad response to the client. Not good. I''m convinced that the problem is

I''m trying to implement the upload progress bar with lighttpd 1.4.11, and i''m seeing various posts (linked below) indicating that lighty doesn''t support it. sounds like they''re working on it, though. anyone have any idea what the current status of this is? or if there''s a workaround in the meanwhile? those posts:

I have an existing rails application on lighttpd and I am trrying to upgrade to mongrel for the enhanced scalability it offers. I am running mongrel 1.1.1, rails 1.2.5, lighttpd 1.4.13 and ruby 1.8.5 Everything is working great except request.remote_ip returns 127.0.0.1 or 192.168.0.102 (the internal network address of the server running lighty). I''ve seen some older posts about

Hi guys, I''m here again with a problem. I have a rails app called brewed. It''s located /home/user/brewed. My lighttpd.conf is located at /home/user/lighty. When I execute lighty on port 80 with: /usr/local/sbin/lighttpd -f /home/user/lighty/lighttpd.conf rails seems to work fine. If I type www.mysite.com/main/index on my browser, the page comes out well. I have my files

Hi Folks, I''m sure tons of people are gonna ruin a whole drawer of their best panties over this one. Rick Olson worked on the mongrel_upload_progress gem, documentation and examples and has almost everything you need to do progress tracked file uploads using just Mongrel to handle the upload. This means that Rails (or any other framework) isn''t blocked while the upload

Hi, I wrote a message earlier regarding how I wasn''t getting any feedback from mongrel_upload_progress. After putting lots of debug messages in the plugin, I figured out what was going on. I had a route like this setup in routes.rb (this was the problem): map.upload "upload/:upload_id", :controller => "file", :action

I''ve been using a homegrown system to do billing for my site. Right now I want to add a couple things, but I''m not sure I want to actually have to work on this billing system. Seems like it''d make a lot more sense to just use an existing package like ModernBill [1]. I''ve never used PHP on lighttpd, never needed to. Not sure if MB can run on it, or how well

Hello list, I''ve been developing a rails app using webrick as my server. I''m trying to change my server over to lighttpd as I am now attempting to deploy on a host that uses lighttpd. I had an older version of lighttpd installed and could never get it running correctly with my app. Preparing for deployment I decided to get lighty working and after poking around a bit I

Hi, I''m currently running my rails app on lighttpd. I want to have an upload progress bar for uploading large files. But I have read that lighttpd has removed that functionallity right now. Should I switch over to apache 2.0 if I want this feature? Is there another way around it? Also, I tried installing Apache 2.0 on my mac with fastcgi, but once I tried to start the server, I get

Hello, I have an issue I am having trouble figuring out. I have a Rails app running through lighttpd which is accessed through an Apache proxy. My apache config: <location /rails/> ProxyPass http://localhost:81/ ProxyPassReverse http://localhost:81/ </location> RewriteEngine On RewriteRule ^/rails/(.*) http://localhost:81/$1 [P] So when apache sees /rails/ it

Hello everyone, I?ve been working with Ruby on Rails for about 2 months now and have really enjoyed the ease of use of it. I?m only been doing development on it so I?ve been using WeBrick. Recently, I have built a server running Debian Linux, with ruby 1.8.2, rails 1.0.0, lighty 1.4.3, and Mysql 5.0.18. I used WeBrick to generate a lighttpd.conf file for me, I changed the paths in the

I just got a new Debian Sarge server and followed the brainspl.at "Debian Lighttpd Rails Stack" tutorial. The only place I deviated was the version of Lighty. The page uses 1.4.7 and I spotted that 1.4.10 was available. I installed that and couldn''t get anywhere. Lighty died on first access from the test rails app, and even from a ultra basic static config. No log,

I just got a new Debian Sarge server and followed the brainspl.at "Debian Lighttpd Rails Stack" tutorial. The only place I deviated was the version of Lighty. The page uses 1.4.7 and I spotted that 1.4.10 was available. I installed that and couldn''t get anywhere. Lighty died on first access from the test rails app, and even from a ultra basic static config. No log, no

Hi guys, Im doing fileuploads and it works great with webrick...I just installed lighttpd 1.4.7 and ran ruby script/server suecessfully picking up my lighty and fcgi install... however...when I try to upload a file the proces either stalls (no evidence of the hit in any logs) or returns 503.... any suggestions?? thanks in advance... Mikkel -- Posted via http://www.ruby-forum.com/.

Last time I checked, the upload progress module (http://api.rubyonrails.com/classes/ActionController/UploadProgress.html) was not working under Lighttpd. Anyone know if that that has changed or when it will change? -- Posted via http://www.ruby-forum.com/.

Hi! What''s up with upload progress support in Rails? Does anyone know if it will stay core, or go as a plugin? Does anyone have it working with lighttpd? If yes, what versions? Is it working for all of the Apache crowd? Thanks, Rob

In case this helps anyone I recently finished setting up a Debian server closely following Ezra''s excellent guidance @ http://brainspl.at/rails_stack.html. I used newer libraries in some cases (and mysql 5.0) and everything worked great until the end when lighttpd wouldn''t start. I finally figured out that Lighty 1.4.9 has a problem working with rails out-of-the-box. See

Hi guys, I''ve been running mongrel for a while now with Ruby 1.8.4, and last week upgraded to 1.8.6. Since upgrading, each morning when I wake up there''s a big problem: 1. Accessing the site returns a "500 Internal Server Error" 2. All the mongrel_rails processes are still running, but none of them are active (when I run top) 3. Lighttpd and pound are still

[ERR][17968] Handling client: can''t convert nil into String Hi, We decided to go with SCGI + Lighttpd for Rails at our company and had no problems with the initial setup. Everything ran fine and was fast. However, problems occurred when we tried to rebuild Lighty with SSL capabilities. With this build, even with SSL off in the config file the application fails on the first request.

I am wanting to one run instance of lighttpd, many many instances of mongrel. I also need ssl but only for one of my sites. I understand that Mongrel does not play with SSL so I am forced to use Lighttpd. I think that lighttpd only handles ssl or non-ssl on any given instance. Is there a way for me to accomplish my goal of one lighttpd with multiple mongrels and the occasional ssl connection? --