From: "nahi (Hiroshi Nakamura)" <nakahiro@...>
Date: 2012-04-12T06:00:27+09:00
Subject: [ruby-core:44292] [ruby-trunk - Feature #6236] WEBrick::HTTPServer swallows Exception


Issue #6236 has been updated by nahi (Hiroshi Nakamura).

Assignee changed from drbrain (Eric Hodel) to nahi (Hiroshi Nakamura)

WEBrick has a maintainer now :)
----------------------------------------
Feature #6236: WEBrick::HTTPServer swallows Exception
https://bugs.ruby-lang.org/issues/6236#change-25838

Author: regularfry (Alex Young)
Status: Closed
Priority: Normal
Assignee: nahi (Hiroshi Nakamura)
Category: lib
Target version: 2.0.0


At the moment when using WEBrick you've always got to remember to define a signal handler to be able to kill the server when you're done with it.  This is annoying and makes it more painful to use than it should be, because if you realise you've forgotten to define a trap("INT") handler after you've started the server, all you can do is kill -9 the process.  This also catches out people learning the library more than it should.  It shouldn't be the web server's job to take over process management, but that's what it ends up doing.

The reason this happens is because webrick/server.rb uses `rescue Exception` around its accept loop.  This is more broad than it should be.  The attached patch replaces this with a `rescue StandardError`, and causes other Exception subclasses to be logged and re-raised.  This makes WEBrick::HTTPServer somewhat more friendly to use at the command-line.

If you Ctrl-c out of a `server.start` loop with this patch applied, you can't restart the server because it leaves internal state lying around, but I think it's still an improvement over the current situation.


-- 
http://bugs.ruby-lang.org/