unicorn 5.1.0 → 5.2.0

data/ext/unicorn_http/unicorn_http_common.rl

@@ -4,7 +4,7 @@
 
 #### HTTP PROTOCOL GRAMMAR
 # line endings
-  CRLF = "\r\n";
+  CRLF = ("\r\n" | "\n");
 
 # character types
   CTL = (cntrl | 127);

data/lib/unicorn/configurator.rb

@@ -3,11 +3,11 @@
 
 # Implements a simple DSL for configuring a unicorn server.
 #
-# See http://unicorn.bogomips.org/examples/unicorn.conf.rb and
-# http://unicorn.bogomips.org/examples/unicorn.conf.minimal.rb
+# See https://bogomips.org/unicorn/examples/unicorn.conf.rb and
+# https://bogomips.org/unicorn/examples/unicorn.conf.minimal.rb
 # example configuration files.  An example config file for use with
 # nginx is also available at
-# http://unicorn.bogomips.org/examples/nginx.conf
+# https://bogomips.org/unicorn/examples/nginx.conf
 #
 # See the link:/TUNING.html document for more information on tuning unicorn.
 class Unicorn::Configurator

data/lib/unicorn/http_server.rb

@@ -6,7 +6,7 @@
 # forked worker children.
 #
 # Users do not need to know the internals of this class, but reading the
-# {source}[http://bogomips.org/unicorn.git/tree/lib/unicorn/http_server.rb]
+# {source}[https://bogomips.org/unicorn.git/tree/lib/unicorn/http_server.rb]
 # is education for programmers wishing to learn how unicorn works.
 # See Unicorn::Configurator for information on how to configure unicorn.
 class Unicorn::HttpServer

data/lib/unicorn/oob_gc.rb

@@ -43,8 +43,9 @@
 #     use Unicorn::OobGC, 2, %r{\A/(?:expensive/foo|more_expensive/foo)}
 #
 # Feedback from users of early implementations of this module:
-# * http://comments.gmane.org/gmane.comp.lang.ruby.unicorn.general/486
-# * http://article.gmane.org/gmane.comp.lang.ruby.unicorn.general/596
+# * https://bogomips.org/unicorn-public/0BFC98E9-072B-47EE-9A70-05478C20141B@lukemelia.com/
+# * https://bogomips.org/unicorn-public/AANLkTilUbgdyDv9W1bi-s_W6kq9sOhWfmuYkKLoKGOLj@mail.gmail.com/
+
 module Unicorn::OobGC
 
   # this pretends to be Rack middleware because it used to be

data/lib/unicorn/version.rb

@@ -1 +1 @@
-Unicorn::Const::UNICORN_VERSION = '5.1.0'
+Unicorn::Const::UNICORN_VERSION = '5.2.0'

data/man/man1/unicorn.1

@@ -1,19 +1,19 @@
-.TH UNICORN 1 "September 15, 2009" "Unicorn User Manual"
+.TH "UNICORN" "1" "September 15, 2009" "Unicorn User Manual" ""
 .SH NAME
 .PP
-unicorn - a rackup-like command to launch the Unicorn HTTP server
+unicorn \- a rackup\-like command to launch the Unicorn HTTP server
 .SH SYNOPSIS
 .PP
-unicorn [-c CONFIG_FILE] [-E RACK_ENV] [-D] [RACKUP_FILE]
+unicorn [\-c CONFIG_FILE] [\-E RACK_ENV] [\-D] [RACKUP_FILE]
 .SH DESCRIPTION
 .PP
-A rackup(1)-like command to launch Rack applications using Unicorn.
+A rackup(1)\-like command to launch Rack applications using Unicorn.
 It is expected to be started in your application root (APP_ROOT), but
 the "working_directory" directive may be used in the CONFIG_FILE.
 .PP
-While unicorn takes a myriad of command-line options for compatibility
+While unicorn takes a myriad of command\-line options for compatibility
 with ruby(1) and rackup(1), it is recommended to stick to the few
-command-line options specified in the SYNOPSIS and use the CONFIG_FILE
+command\-line options specified in the SYNOPSIS and use the CONFIG_FILE
 as much as possible.
 .SH RACKUP FILE
 .PP
@@ -21,12 +21,12 @@ This defaults to "config.ru" in APP_ROOT.
 It should be the same file used by rackup(1) and other Rack launchers,
 it uses the \f[I]Rack::Builder\f[] DSL.
 .PP
-Embedded command-line options are mostly parsed for compatibility with
+Embedded command\-line options are mostly parsed for compatibility with
 rackup(1) but strongly discouraged.
 .SH UNICORN OPTIONS
 .TP
-.B -c, --config-file CONFIG_FILE
-Path to the Unicorn-specific config file.
+.B \-c, \-\-config\-file CONFIG_FILE
+Path to the Unicorn\-specific config file.
 The config file is implemented as a Ruby DSL, so Ruby code may executed.
 See the RDoc/ri for the \f[I]Unicorn::Configurator\f[] class for the
 full list of directives available from the DSL.
@@ -36,7 +36,7 @@ output.
 .RS
 .RE
 .TP
-.B -D, --daemonize
+.B \-D, \-\-daemonize
 Run daemonized in the background.
 The process is detached from the controlling terminal and stdin is
 redirected to "/dev/null".
@@ -47,134 +47,135 @@ redirected to "/dev/null".
 .RS
 .RE
 .TP
-.B -E, --env RACK_ENV
+.B \-E, \-\-env RACK_ENV
 Run under the given RACK_ENV.
 See the RACK ENVIRONMENT section for more details.
 .RS
 .RE
 .TP
-.B -l, --listen ADDRESS
+.B \-l, \-\-listen ADDRESS
 Listens on a given ADDRESS.
 ADDRESS may be in the form of HOST:PORT or PATH, HOST:PORT is taken to
 mean a TCP socket and PATH is meant to be a path to a UNIX domain
 socket.
 Defaults to "0.0.0.0:8080" (all addresses on TCP port 8080) For
 production deployments, specifying the "listen" directive in CONFIG_FILE
-is recommended as it allows fine-tuning of socket options.
+is recommended as it allows fine\-tuning of socket options.
 .RS
 .RE
 .TP
-.B -N, --no-default-middleware
+.B \-N, \-\-no\-default\-middleware
 Disables loading middleware implied by RACK_ENV.
 This bypasses the configuration documented in the RACK ENVIRONMENT
 section, but still allows RACK_ENV to be used for
-application/framework-specific purposes.
+application/framework\-specific purposes.
 .RS
 .RE
 .SH RACKUP COMPATIBILITY OPTIONS
 .TP
-.B -o, --host HOST
+.B \-o, \-\-host HOST
 Listen on a TCP socket belonging to HOST, default is "0.0.0.0" (all
 addresses).
-If specified multiple times on the command-line, only the last-specified
-value takes effect.
+If specified multiple times on the command\-line, only the
+last\-specified value takes effect.
 This option only exists for compatibility with the rackup(1) command,
-use of "-l"/"--listen" switch is recommended instead.
+use of "\-l"/"\-\-listen" switch is recommended instead.
 .RS
 .RE
 .TP
-.B -p, --port PORT
+.B \-p, \-\-port PORT
 Listen on the specified TCP PORT, default is 8080.
-If specified multiple times on the command-line, only the last-specified
-value takes effect.
+If specified multiple times on the command\-line, only the
+last\-specified value takes effect.
 This option only exists for compatibility with the rackup(1) command,
-use of "-l"/"--listen" switch is recommended instead.
+use of "\-l"/"\-\-listen" switch is recommended instead.
 .RS
 .RE
 .TP
-.B -s, --server SERVER
-No-op, this exists only for compatibility with rackup(1).
+.B \-s, \-\-server SERVER
+No\-op, this exists only for compatibility with rackup(1).
 .RS
 .RE
 .SH RUBY OPTIONS
 .TP
-.B -e, --eval LINE
+.B \-e, \-\-eval LINE
 Evaluate a LINE of Ruby code.
-This evaluation happens immediately as the command-line is being parsed.
+This evaluation happens immediately as the command\-line is being
+parsed.
 .RS
 .RE
 .TP
-.B -d, --debug
+.B \-d, \-\-debug
 Turn on debug mode, the $DEBUG variable is set to true.
 .RS
 .RE
 .TP
-.B -w, --warn
+.B \-w, \-\-warn
 Turn on verbose warnings, the $VERBOSE variable is set to true.
 .RS
 .RE
 .TP
-.B -I, --include PATH
-specify $LOAD_PATH.
-PATH will be prepended to $LOAD_PATH.
+.B \-I, \-\-include PATH
+specify
+\f[I]L\f[]\f[I]O\f[]\f[I]A\f[]\f[I]D\f[]~\f[I]P\f[]~\f[I]A\f[]\f[I]T\f[]\f[I]H\f[].\f[I]P\f[]\f[I]A\f[]\f[I]T\f[]\f[I]H\f[]\f[I]w\f[]\f[I]i\f[]\f[I]l\f[]\f[I]l\f[]\f[I]b\f[]\f[I]e\f[]\f[I]p\f[]\f[I]r\f[]\f[I]e\f[]\f[I]p\f[]\f[I]e\f[]\f[I]n\f[]\f[I]d\f[]\f[I]e\f[]\f[I]d\f[]\f[I]t\f[]\f[I]o\f[]LOAD_PATH.
 The \[aq]:\[aq] character may be used to delimit multiple directories.
 This directive may be used more than once.
 Modifications to $LOAD_PATH take place immediately and in the order they
-were specified on the command-line.
+were specified on the command\-line.
 .RS
 .RE
 .TP
-.B -r, --require LIBRARY
+.B \-r, \-\-require LIBRARY
 require a specified LIBRARY before executing the application.
 The "require" statement will be executed immediately and in the order
-they were specified on the command-line.
+they were specified on the command\-line.
 .RS
 .RE
 .SH SIGNALS
 .PP
 The following UNIX signals may be sent to the master process:
 .IP \[bu] 2
-HUP - reload config file, app, and gracefully restart all workers
+HUP \- reload config file, app, and gracefully restart all workers
 .IP \[bu] 2
-INT/TERM - quick shutdown, kills all workers immediately
+INT/TERM \- quick shutdown, kills all workers immediately
 .IP \[bu] 2
-QUIT - graceful shutdown, waits for workers to finish their current
+QUIT \- graceful shutdown, waits for workers to finish their current
 request before finishing.
 .IP \[bu] 2
-USR1 - reopen all logs owned by the master and all workers See
+USR1 \- reopen all logs owned by the master and all workers See
 Unicorn::Util.reopen_logs for what is considered a log.
 .IP \[bu] 2
-USR2 - reexecute the running binary.
+USR2 \- reexecute the running binary.
 A separate QUIT should be sent to the original process once the child is
 verified to be up and running.
 .IP \[bu] 2
-WINCH - gracefully stops workers but keep the master running.
+WINCH \- gracefully stops workers but keep the master running.
 This will only work for daemonized processes.
 .IP \[bu] 2
-TTIN - increment the number of worker processes by one
+TTIN \- increment the number of worker processes by one
 .IP \[bu] 2
-TTOU - decrement the number of worker processes by one
+TTOU \- decrement the number of worker processes by one
 .PP
-See the SIGNALS (http://unicorn.bogomips.org/SIGNALS.html) document for
+See the SIGNALS (https://bogomips.org/unicorn/SIGNALS.html) document for
 full description of all signals used by Unicorn.
 .SH RACK ENVIRONMENT
 .PP
 Accepted values of RACK_ENV and the middleware they automatically load
 (outside of RACKUP_FILE) are exactly as those in rackup(1):
 .IP \[bu] 2
-development - loads Rack::CommonLogger, Rack::ShowExceptions, and
+development \- loads Rack::CommonLogger, Rack::ShowExceptions, and
 Rack::Lint middleware
 .IP \[bu] 2
-deployment - loads Rack::CommonLogger middleware
+deployment \- loads Rack::CommonLogger middleware
 .IP \[bu] 2
-none - loads no middleware at all, relying entirely on RACKUP_FILE
+none \- loads no middleware at all, relying entirely on RACKUP_FILE
 .PP
 All unrecognized values for RACK_ENV are assumed to be "none".
 Production deployments are strongly encouraged to use "deployment" or
 "none" for maximum performance.
 .PP
-As of Unicorn 0.94.0, RACK_ENV is exported as a process-wide environment
-variable as well.
+As of Unicorn 0.94.0, RACK_ENV is exported as a process\-wide
+environment variable as well.
 While not current a part of the Rack specification as of Rack 1.0.1,
 this has become a de facto standard in the Rack world.
 .PP
@@ -185,8 +186,8 @@ If needed, they must be individually specified in the RACKUP_FILE, some
 frameworks do not require them.
 .SH ENVIRONMENT VARIABLES
 .PP
-The RACK_ENV variable is set by the aforementioned -E switch.
-All application or library-specific environment variables (e.g.
+The RACK_ENV variable is set by the aforementioned \-E switch.
+All application or library\-specific environment variables (e.g.
 TMPDIR) may always be set in the Unicorn CONFIG_FILE in addition to the
 spawning shell.
 When transparently upgrading Unicorn, all environment variables set in
@@ -194,7 +195,7 @@ the old master process are inherited by the new master process.
 Unicorn only uses (and will overwrite) the UNICORN_FD environment
 variable internally when doing transparent upgrades.
 .PP
-UNICORN_FD is a comma-delimited list of one or more file descriptors
+UNICORN_FD is a comma\-delimited list of one or more file descriptors
 used to implement USR2 upgrades.
 Init systems may bind listen sockets itself and spawn unicorn with
 UNICORN_FD set to the file descriptor numbers of the listen socket(s).
@@ -209,7 +210,7 @@ the unicorn config file.
 .IP \[bu] 2
 \f[I]Unicorn::Configurator\f[] ri/RDoc
 .IP \[bu] 2
-Unicorn RDoc (http://unicorn.bogomips.org/)
+Unicorn RDoc (https://bogomips.org/unicorn/)
 .IP \[bu] 2
 Rack RDoc (http://www.rubydoc.info/github/rack/rack/)
 .IP \[bu] 2

data/man/man1/unicorn_rails.1

@@ -1,13 +1,13 @@
-.TH UNICORN_RAILS 1 "September 17, 2009" "Unicorn User Manual"
+.TH "UNICORN_RAILS" "1" "September 17, 2009" "Unicorn User Manual" ""
 .SH NAME
 .PP
-unicorn_rails - unicorn launcher for Rails 1.x and 2.x users
+unicorn_rails \- unicorn launcher for Rails 1.x and 2.x users
 .SH SYNOPSIS
 .PP
-unicorn_rails [-c CONFIG_FILE] [-E RAILS_ENV] [-D] [RACKUP_FILE]
+unicorn_rails [\-c CONFIG_FILE] [\-E RAILS_ENV] [\-D] [RACKUP_FILE]
 .SH DESCRIPTION
 .PP
-A rackup(1)-like command to launch Rails applications using Unicorn.
+A rackup(1)\-like command to launch Rails applications using Unicorn.
 It is expected to be started in your Rails application root
 (RAILS_ROOT), but the "working_directory" directive may be used in the
 CONFIG_FILE.
@@ -23,14 +23,14 @@ The outward interface resembles rackup(1), the internals and default
 middleware loading is designed like the \f[C]script/server\f[] command
 distributed with Rails.
 .PP
-While Unicorn takes a myriad of command-line options for compatibility
+While Unicorn takes a myriad of command\-line options for compatibility
 with ruby(1) and rackup(1), it is recommended to stick to the few
-command-line options specified in the SYNOPSIS and use the CONFIG_FILE
+command\-line options specified in the SYNOPSIS and use the CONFIG_FILE
 as much as possible.
 .SH UNICORN OPTIONS
 .TP
-.B -c, --config-file CONFIG_FILE
-Path to the Unicorn-specific config file.
+.B \-c, \-\-config\-file CONFIG_FILE
+Path to the Unicorn\-specific config file.
 The config file is implemented as a Ruby DSL, so Ruby code may executed.
 See the RDoc/ri for the \f[I]Unicorn::Configurator\f[] class for the
 full list of directives available from the DSL.
@@ -40,7 +40,7 @@ output.
 .RS
 .RE
 .TP
-.B -D, --daemonize
+.B \-D, \-\-daemonize
 Run daemonized in the background.
 The process is detached from the controlling terminal and stdin is
 redirected to "/dev/null".
@@ -57,7 +57,7 @@ Unicorn config file.
 .RS
 .RE
 .TP
-.B -E, --env RAILS_ENV
+.B \-E, \-\-env RAILS_ENV
 Run under the given RAILS_ENV.
 This sets the RAILS_ENV environment variable.
 Acceptable values are exactly those you expect in your Rails
@@ -65,38 +65,38 @@ application, typically "development" or "production".
 .RS
 .RE
 .TP
-.B -l, --listen ADDRESS
+.B \-l, \-\-listen ADDRESS
 Listens on a given ADDRESS.
 ADDRESS may be in the form of HOST:PORT or PATH, HOST:PORT is taken to
 mean a TCP socket and PATH is meant to be a path to a UNIX domain
 socket.
 Defaults to "0.0.0.0:8080" (all addresses on TCP port 8080).
 For production deployments, specifying the "listen" directive in
-CONFIG_FILE is recommended as it allows fine-tuning of socket options.
+CONFIG_FILE is recommended as it allows fine\-tuning of socket options.
 .RS
 .RE
 .SH RACKUP COMPATIBILITY OPTIONS
 .TP
-.B -o, --host HOST
+.B \-o, \-\-host HOST
 Listen on a TCP socket belonging to HOST, default is "0.0.0.0" (all
 addresses).
-If specified multiple times on the command-line, only the last-specified
-value takes effect.
+If specified multiple times on the command\-line, only the
+last\-specified value takes effect.
 This option only exists for compatibility with the rackup(1) command,
-use of "-l"/"--listen" switch is recommended instead.
+use of "\-l"/"\-\-listen" switch is recommended instead.
 .RS
 .RE
 .TP
-.B -p, --port PORT
+.B \-p, \-\-port PORT
 Listen on the specified TCP PORT, default is 8080.
-If specified multiple times on the command-line, only the last-specified
-value takes effect.
+If specified multiple times on the command\-line, only the
+last\-specified value takes effect.
 This option only exists for compatibility with the rackup(1) command,
-use of "-l"/"--listen" switch is recommended instead.
+use of "\-l"/"\-\-listen" switch is recommended instead.
 .RS
 .RE
 .TP
-.B --path PATH
+.B \-\-path PATH
 Mounts the Rails application at the given PATH (instead of "/").
 This is equivalent to setting the RAILS_RELATIVE_URL_ROOT environment
 variable.
@@ -105,38 +105,39 @@ This is only supported under Rails 2.3 or later at the moment.
 .RE
 .SH RUBY OPTIONS
 .TP
-.B -e, --eval LINE
+.B \-e, \-\-eval LINE
 Evaluate a LINE of Ruby code.
-This evaluation happens immediately as the command-line is being parsed.
+This evaluation happens immediately as the command\-line is being
+parsed.
 .RS
 .RE
 .TP
-.B -d, --debug
+.B \-d, \-\-debug
 Turn on debug mode, the $DEBUG variable is set to true.
 For Rails >= 2.3.x, this loads the \f[I]Rails::Rack::Debugger\f[]
 middleware.
 .RS
 .RE
 .TP
-.B -w, --warn
+.B \-w, \-\-warn
 Turn on verbose warnings, the $VERBOSE variable is set to true.
 .RS
 .RE
 .TP
-.B -I, --include PATH
-specify $LOAD_PATH.
-PATH will be prepended to $LOAD_PATH.
+.B \-I, \-\-include PATH
+specify
+\f[I]L\f[]\f[I]O\f[]\f[I]A\f[]\f[I]D\f[]~\f[I]P\f[]~\f[I]A\f[]\f[I]T\f[]\f[I]H\f[].\f[I]P\f[]\f[I]A\f[]\f[I]T\f[]\f[I]H\f[]\f[I]w\f[]\f[I]i\f[]\f[I]l\f[]\f[I]l\f[]\f[I]b\f[]\f[I]e\f[]\f[I]p\f[]\f[I]r\f[]\f[I]e\f[]\f[I]p\f[]\f[I]e\f[]\f[I]n\f[]\f[I]d\f[]\f[I]e\f[]\f[I]d\f[]\f[I]t\f[]\f[I]o\f[]LOAD_PATH.
 The \[aq]:\[aq] character may be used to delimit multiple directories.
 This directive may be used more than once.
 Modifications to $LOAD_PATH take place immediately and in the order they
-were specified on the command-line.
+were specified on the command\-line.
 .RS
 .RE
 .TP
-.B -r, --require LIBRARY
+.B \-r, \-\-require LIBRARY
 require a specified LIBRARY before executing the application.
 The "require" statement will be executed immediately and in the order
-they were specified on the command-line.
+they were specified on the command\-line.
 .RS
 .RE
 .SH RACKUP FILE
@@ -148,15 +149,16 @@ Unlike many other Rack applications, RACKUP_FILE is completely
 \f[I]optional\f[] for Rails, but may be used to disable some of the
 default middleware for performance.
 .PP
-Embedded command-line options are mostly parsed for compatibility with
+Embedded command\-line options are mostly parsed for compatibility with
 rackup(1) but strongly discouraged.
 .SH ENVIRONMENT VARIABLES
 .PP
-The RAILS_ENV variable is set by the aforementioned -E switch.
-The RAILS_RELATIVE_URL_ROOT is set by the aforementioned --path switch.
+The RAILS_ENV variable is set by the aforementioned \-E switch.
+The RAILS_RELATIVE_URL_ROOT is set by the aforementioned \-\-path
+switch.
 Either of these variables may also be set in the shell or the Unicorn
 CONFIG_FILE.
-All application or library-specific environment variables (e.g.
+All application or library\-specific environment variables (e.g.
 TMPDIR, RAILS_ASSET_ID) may always be set in the Unicorn CONFIG_FILE in
 addition to the spawning shell.
 When transparently upgrading Unicorn, all environment variables set in
@@ -167,28 +169,28 @@ variable internally when doing transparent upgrades.
 .PP
 The following UNIX signals may be sent to the master process:
 .IP \[bu] 2
-HUP - reload config file, app, and gracefully restart all workers
+HUP \- reload config file, app, and gracefully restart all workers
 .IP \[bu] 2
-INT/TERM - quick shutdown, kills all workers immediately
+INT/TERM \- quick shutdown, kills all workers immediately
 .IP \[bu] 2
-QUIT - graceful shutdown, waits for workers to finish their current
+QUIT \- graceful shutdown, waits for workers to finish their current
 request before finishing.
 .IP \[bu] 2
-USR1 - reopen all logs owned by the master and all workers See
+USR1 \- reopen all logs owned by the master and all workers See
 Unicorn::Util.reopen_logs for what is considered a log.
 .IP \[bu] 2
-USR2 - reexecute the running binary.
+USR2 \- reexecute the running binary.
 A separate QUIT should be sent to the original process once the child is
 verified to be up and running.
 .IP \[bu] 2
-WINCH - gracefully stops workers but keep the master running.
+WINCH \- gracefully stops workers but keep the master running.
 This will only work for daemonized processes.
 .IP \[bu] 2
-TTIN - increment the number of worker processes by one
+TTIN \- increment the number of worker processes by one
 .IP \[bu] 2
-TTOU - decrement the number of worker processes by one
+TTOU \- decrement the number of worker processes by one
 .PP
-See the SIGNALS (http://unicorn.bogomips.org/SIGNALS.html) document for
+See the SIGNALS (https://bogomips.org/unicorn/SIGNALS.html) document for
 full description of all signals used by Unicorn.
 .SH SEE ALSO
 .IP \[bu] 2
@@ -198,7 +200,7 @@ unicorn(1)
 .IP \[bu] 2
 \f[I]Unicorn::Configurator\f[] ri/RDoc
 .IP \[bu] 2
-Unicorn RDoc (http://unicorn.bogomips.org/)
+Unicorn RDoc (https://bogomips.org/unicorn/)
 .IP \[bu] 2
 Rack RDoc (http://www.rubydoc.info/github/rack/rack/)
 .IP \[bu] 2