similar to: how to use upload progress?

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 =>

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

Hey all, First off, thanks to Rick Olson and whoever else was involved with this plugin... It''s been amazingly easy to implement. I''ve got a question about the path_info parameter, though... It seems that unless the request PATH_INFO exactly matches the path_info passed in to the plugin at inclusion, it won''t actually trigger Add and add the upload to the list of

Hi, I''m trying to write a file upload monitor for mongrel that uses juggernaut to alert the browser of a change. I''m writing a plugin that uses Mongrel::HttpHandlerPlugin but it looks like the only method that gets called is process and that is only when the upload has finished. I''m setting the following: @request_notify = true But I am still only getting process to

I ma trying to get this upload working, http://mongrel.rubyforge.org/docs/upload_progress.html, ....after starting from the command line, mongrel_rails start -d -p 3001 -S config/mongrel_upload_progress.conf I get this eror in the browser, NameError uninitialized constant UploadProgressRailsController RAILS_ROOT: /usr/opt/tomcat/workspace/upload/config/.. Application Trace | Framework Trace

Hey Folks, There''s a nasty little bug in 0.3.13.3 when running in development mode which could cause all sorts of problems. Please grab the pre-release of 0.3.13.4 and tell me if it works for you: gem install mongrel --source=http://mongrel.rubyforge.org/releases/ Thanks! -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need

mongreleers, This is a hack for adding basic upload progress support to Mongrel. Currently, you can monitor the upload of any POST. I''m sure some work needs to be done to get it functioning with Rails. Save as lib/mongrel/progress. Anyway, here''s how to start Mongrel with it: require ''mongrel'' require ''mongrel/camping'' require

Howdy. I''m working on a RoR CMS and need cached pages to all be in public/cache rather than public [in order to set svn:ignore on all the files properly]. I can get page_cache_directory set correctly and the pages are cached in the right place but Mongrel isn''t serving them because it''s only looking for them in public. During development I know I can set -r public/cache

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 just found a vulnerability in one of my web apps that was running Mongrel 1.1.2 where I could go to URIs like /.%252e/.%252e/.%252e/.%252e/.%252e/.%252e/.%252e/etc/passwd and it would serve the actual /etc/passwd file. The issue seems to be in lib/mongrel/handlers.rb in the change from 1.0.3 to 1.0.4 req_path = HttpRequest.unescape(path_info) - if @path - req_path =

Hello, So, I grabbed the mongrel_upload_progress code from subversion because I really need something similar for a project I am working on. Anyway, I installed the gem and can''t figure out a few things. 1) I''m not sure what Upload < GemPlugin::Plugin "/handlers" is for 2) How to call the Progress < GemPlugin::Plugin "/handlers" handler. While I

Hello All, I''m putting out a quick half-release because there''s some work on the MIME types I''ve included that needs to be done by all of you. Read at the end to understand your role in what you started. This release features two major capitulations on Mongrel''s stance of not being a full web server. The first is Mongrel now sports a YAML file with 739 MIME

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

Hi, I''m halfway developing a tiny plugin that allows people to scrub flash video files. I''ve got my plugin setup to monitor a directory /movies. Whenever a .flv file is requested within that directory, some stuff should happen, if not, the request should be processed as usual. I don''t know how to do the latter.. require ''mongrel'' require

Thanks to all concerned with the implementation of the Upload Progress plugin, it works really well. I want to limit the size of files to be uploaded to say 10Mb. Is there any way for Mongrel to ''refuse'' to upload files over a certain size and then pass an error onto Rails in order to display feedback to the user? I don''t really want to have to upload the whole

I''m wondering if it''s possible to setup mongrel to have multiple document roots? The use case I''m trying to solve is one where I have a library of shared CSS/JS/Images and would like multiple rails application to use them. I have written a proxy controller and added some routes to serve the static files and it works reasonably well, but is extremely slow, because

Hello, I have a cluster of three Mongrels running behind Pound. All is running well except when I restart the cluster (mongrel_rails cluster::restart) any in progress file uploads (handled through mongrel_upload_progress) stop uploading. That is, if I''m uploading a file (via a web app being served by the mongrel cluster) during a restart, my browser will indefinitely pause as if it is

Hey Folks, Another announcement of Mongrel -- the fastest little web server library for Ruby yet. This release is nice in that it should build on win32 better and it now sports a small DirHandler that can serve directories and files. This means Mongrel is closer to replacing WEBrick as a Rails debug runner. You can get the releases and information from: *

I started actually using the upload progress handler, and noticed it was leaking memory over time. Looking at the code, I noticed that cancelled uploads weren''t being cleaned up. I bugged Zed about adding a request_abort callback to handlers, but I found a simple way to monkey patch that in: # config/mongrel_upload_progress.conf # yes, this file is being used with -S meaning