similar to: Small updates and release plan

* Apologies for starting a new thread; I just subscribed. Has anyone been able to make this exploit happen if requests are being proxied to Mongrel through Apache? I''ve been trying variations on the double-encoding thing and can''t trigger the exploit through Apache. Hitting Mongrel directly does expose the problem. I''ll still upgrade my servers, of course, but I

Hey so, People are asking about Mongrel Ruby 1.9 compatibility. Isn''t the point of 1.9 for library developers to have time to get ready for 2.0? It''s not like 1.9 is a production release. Evan -- Evan Weaver Cloudburst, LLC

FYI. -- - Brian Gupta http://opensolaris.org/os/project/nycosug/

Hi, I''ve started a new project that uses Mongrel. It basically lets you defer requests to it until other Mongrels in your (Rails) pool becomes free. Rubyforge project page: http://rubyforge.org/projects/qrp/ gems, tarballs and git repo in case they haven''t hit the mirrors yet: http://bogomips.org/ruby/ I should also add that nginx 0.6.7 or later is required for the

We have a load balancer sending requests to one of X boxes and one of N mongrel processes on that box. Since each mongrel processes is multi-threaded but it has a mutex around the section that calls rails, we end up with several requests queued up waiting when they could have gone to another box with a free process. For example, boxA, and boxB. boxA has mongrels 1 through 10 boxB has

I''m running jruby trunk which has integrated rubygems 1.0.0 and when I try and install mongrel with gem it blows up when the fastthread dependency tries to do a native compilation. I couldn''t find a copy of the gemspec in the svn checkout but looking at the one installed when gem installing mongrel didn''t show any platform differentiation. There is platform

I''m confused. Wasn''t threading fixed in 1.8.6, negating the need for fastthread? Why is fastthread still a requirement of Mongrel? Just curious. :)

Hi all, There is a bug with Mongrel on JRuby 1.0.3 that the JRuby guys want fixed before they release it. If it''s ok with people I''d like to fix that, revert (at least for now) the proxy response change, and tag that as 1.1.2 and release it. Anything wrong with this plan? Evan -- Evan Weaver Cloudburst, LLC

I have a periodically_call_remote call in a partial running at 0.20 times a second. <%= periodically_call_remote(:update => ''ack_distance_output'', :frequency => 0.2, :url=>{:action => :ackAdjustDistance}) %> the action looks like this def ackAdjustDistance @calMessage = Calibration.getMessage

All, Mongrel 1.1.3 Rails 2.0.2 Ruby 1.8.6 Windows XP SP2 When I issue the command "ruby script/server" from any of my Rails projects on v. 2.0.2, I get a Windows dialog with the error: "The application has failed to start because MSVCR80.dll was not found. Re-installing the application may fix this problem." I''ve gone through the process of attempting to introduce

Hello Guys, I''m reviewing the code for 1.9, and forgot about this when we first spoke on this subject. The current way we stop threads is using Thread#raise to spread StopServer exception, which will not work as expected in 1.9. 1.9 will treat raised exceptions as #kill, like JRuby does, so the worker threads will not finish serving the client and _then_ exiting, but will be

Hi, I''m trying to start a Mongrel (1.1.3) Server, running as a Windows Service, via mongrel_rails service::install -N FDS_Server_4001 -p 4001 -e production But I get the following error message : ERROR RUNNING ''service::install'': Plugin /service::install does not exist in category /commands I never had this problem before (Win XP, Vista), until I tried installing on

Guys, Subject says everything: http://www.frederico-araujo.com/2007/12/18/my-first-successful-booting-rails-2-0-2-ruby-1-9-attempt Even ActionView uses Proc.binding (which isn''t correctly supported in 1.9) it appears that lot of folks will try to put their hands in Ruby 1.9 when it comes out, and of course, try to get Rails with Mongrel running in it. Zed, Wayne, Evan and ry: maybe we

I am using Rspec 1.1.2 on Windows XP SP2 I am receiving the following error when I run ''rake spec'' from a brand new project: C:/SVN_Projects/rspec/vendor/plugins/rspec/lib/spec/runner/options.rb:107:in `colour='': You must gem install win32console to use colour on Windows (RuntimeError) I have the win32console gem installed and the error still occurs. It seems that the

Guys, Just for fun, I tried to see (I know, a silly way to test it) how much overhead we have calling the C functions of the extensions. the benchmark script and the results: http://pastie.caboo.se/128646 The naive C extension: http://pastie.caboo.se/128647 I compared 1.8.6 (VC6 and mingw builds) against a fresh checkout of ruby trunk. What I understand from that is 1.9 is slower than 1.8

Hello Mongrel Users, I''m writing a web server called Ebb. It''s written in C, makes use of the Mongrel HTTP parser, and uses libev its event loop. The goal is to be small, fast, and language independent server that can host web frameworks. I have written a small Ruby binding which provides a Rack handler - this will allow Ebb to host Rails, Merb, and other Ruby frameworks. In the

Something suddenly went wrong in my ruby install. When installing Mongrel on my Windows XP laptop, it incorrectly tries to build it as a native extension. I don''t even get the selection where I can choose to install a compiled version. I would appreciate any help/links or similar, as I frankly don''t understand what''s going on and why I dont get the usual selection box.

I am having a problem with mongrel just stopping inside a periodically_call_remote function so I ran mongrel with debug enabled Mongrel seg faults after a few minutes The mongrel filelog shows 5 files open when this happens. Same log files that are open all the time. Wed Dec 19 15:10:21 -0700 2007 FILES OPEN BEFORE REQUEST /calibration/ackAdjustDistance --- log/mongrel_debug/objects.log: 2

Hi all, I''m trying to run a Story Runner integration test that uploads a file through Attachment-fu. I''ve tried various ways of specifying the file data, from custom mocks: class MockFile < Struct.new (:original_filename, :read, :content_type); end fdata = MockFile.new "test_upload.txt", "Test Upload", "text/plain" to

Since there are so many efforts at the moment to port restful_authentication I figured I''d put a repo up so that it can be a collaborative effort. You can pick up a copy of the repo at git clone http://snatcht.com/git/merbful_authentication.git at the moment the app is in a branch. Not in the master. get the branch by git checkout -b remote/initial origin/inital_repo At the moment