similar to: POST with huge HTTP body

Hello, I am trying to find a WebDAV library for Ruby that works with fastcgi (production) and Webbrick (development). I''ve found this link which mentions a Webbrick WebDAV library: http://redhanded.hobix.com/inspect/ webrickWebdavHandlerSafelyExtractedFromTheWild.html Unfortunately it sounds limited to Webbrick which will not suit the production environment. Does anyone know of a

Mongrel''s tempfile generation on win32 is broken meaning large files can''t be uploaded. On line 198 of mongrel.rb (0.13.3) HttpRequest#initialize the tempfile function is called:       if clen > Const::MAX_BODY         @body = Tempfile.new(self.class.name)         @body.binmode       else Unfortunately this also includes the module name as the example shows:

I''m looking at writing a Mongrel handler that mimics the behavior of the Apache mod_put [1]. It allows for the streaming upload of very large (GB) files; it also supports resumable upload. Before I get too involved, I''d like to ask if my reading of the mongrel source code is correct, i.e. what I want to do isn''t currently possible. Looking at the class

By default, Mongrel will delete the HTTP request body and short circuit calling any handlers if a request is interrupted or incomplete. Unfortunately, this breaks any attempt to correctly handle a partial PUT. (BTW, PUT is *way* more efficient for uploads compared to POST which requires a MIME parsing step.) So, about a month ago I wrote up some patches to Mongrel 0.3.18 that allowed

Hi all, I''m using Boxroom (http://boxroom.rubyforge.org/) and trying to get upload progress working. I''ve also been testing the sample code at http://itblog.mcgeecorp.com/2007/5/15/mongrel-upload-progress-demo/. I run a Mongrel cluster, and so am using drb (as per http://mongrel.rubyforge.org/docs/upload_progress.html). Starting up rails, I get lots of useful-sounding output:

Hello Mongrel Fans, After about a Month of busy work, bad computers, moving half my house across the country, and other dramas, I''m finally pushing out the next release of Mongrel. This pre-release has lots of little goodies and the start of some documentation that should get everyone primed for the big "Mongrel 0.4 Enterprisey Edition 1.2" coming real soon now. INSTALLING

Hi folks, I have a problem with a storage web service our group wrote using Mongrel::HttpHandler We have a consistent problem when using http PUT to this service when the data is larger than about 4 GB. The web service actually retrieves and processes the data, but the clients hang - the TCP connection is still in the ESTABLISHED state on the client side, but the TCP session no longer exists on

I have an Apache 2.2.3 (mod_proxy_balancer) frontend server that does not have mongrel installed. It does proxy requests to several other mongrel-only servers (each running 2 mongrel processes). Each mongrel node has the same rails code-base and it''s working perfectly. However, my question is when I add an upload file form... where is it going to physically put that file? I mean since

I''ve seen posts of a few people who have this problem, but not a single response about solving it. I can''t upload .png files, but .jpg and .gif work fine. When I upload just a .png, my action gets a StringIO object which breaks when I try to copy the upload to an absolute location. However, using multiple-field upload, as long as one of the to-upload files is *not* a .png, all

I know that Zed has made mention of the fact that using RMagick with mongrel and rails is a bad thing. I''m currently using FlexImage (which in turn uses RMagick) on my application and really haven''t had too many problems. We get a restart for memory usage every 8-10 hours on one mongrel of twelve running, but I''m not sure if that''s an RMagick issue. Either way,

So any files that are uploaded through my form are getting the following mode: -rw------- I need them to have: -rw-r--r-- I''ve tried setting the umask in a script file called set_umask.rb as follows: File.umask(022) and then starting mongrel using: mongrel_rails start -m config/mime.types -S set_umask.rb but it doesn''t seem to change the mode that the files are created

Hi Is there some definitive guide for upload progress plugin ? We have in this mailing list a lot of testimonials, bug reports, bug fixes, but there are still people like me who cannot use it correctly. Here is my config: - mongrel 1.0RC and upload progress plugin 0.2.1 - a 6 mongrels cluster - config/mongrel_upload_progress.conf: uri "/", :handler =>

I''m just wondering if anybody has got any experience in integrating Flex or OpenLaszlo with Rails and which people prefer. I''ve seen some of the tutorials but am pondering which one, if any, I should turn to: http://coenraets.com/tutorials/flexonrails/flexonrails.html http://www.liverail.net/articles/2006/04/16/rubyonrails-1-1-and-flex-2-0-pt-1

Whenever I tried to start mongrel_rails with the upload progress script, it would die with the following error: /usr/local/lib/ruby/1.8/drb/drb.rb:837:in `getaddrinfo'': getaddrinfo: No address associated with nodename (SocketError) from /usr/local/lib/ruby/1.8/drb/drb.rb:837:in `open_server_inaddr_any'' from /usr/local/lib/ruby/1.8/drb/drb.rb:860:in

I''ve just committed fastthread 0.5.3, which finally gives us a working SizedQueue (which hadn''t really ever worked in previous versions). Mostly it was just a matter of refactoring Queue and SizedQueue into a single class behind the scenes, so I could move the signalling of the SizedQueue-specific condition variable inside the queue''s critical section. Failing to do so

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

Hello, I''m trying to install the upload_progress gem and i can''t see the upload progress status. My config is : apache2 with mod_proxy mongrel rails upload.rb : ############## require ''rubygems'' require ''drb'' require ''gem_plugin'' GemPlugin::Manager.instance.load ''mongrel'' => GemPlugin::INCLUDE

Forms without explicit enctype are submitted as application/x-www-form- urlencoded. This is the default behaviour in Rails. However, this enctype does not allow transmission of binary data (files). Would it not make sense to specify the enctype multipart/form-data by default instead? i.e. all the form_for helpers would add this enctype to the form tag, unless overriden by the developer. This

i have a rails app with a form that allows uploading an image file. I take the image file and read it into rmagick to verify that it''s an image. For some reason I can''t catch an exception thrown by rmagick inside the app. After an invalid image file is uploaded the process just hangs. I have to kill mongrel and restart to use the app again. img =

Does anyone know whether the mongrel upload progress plugin works with nginx? It works fine for my app under pound, but not with nginx. I am using DRb to handle the uploads as detailed at http://mongrel.rubyforge.org/docs/upload_progress.html . If I am using pound I can see the uploads with irb -r lib/upload_client.rb , but cannot if I am using nginx. Does anyone know anything more about this