Softpedia >Mac >Business >Phusion Passenger >  Changelog

Phusion Passenger Changelog

What's new in Phusion Passenger 5.0.29

Jun 22, 2016
  • Fixes the FreeBSD build breaking due to the `-ldl` flag introduced by the LVE integration patch (5.0.28). Closes GH-1805.
  • Fixes per-application interpreter override (ruby, node, python) being ignored in mass deployment mode. Closes GH-1818.
  • Fixes incomplete refactor from 5.0.27 that could, under specific conditions, lead to a Passenger crash. Closes GH-1794.
  • [Apache] Remove unused code that caused a crash in configurations with thousands of VirtualHost entries. Closes GH-1676.
  • [Nginx] Fixes use of invalid logfile name (memory already released) in backup log redirection code. Possibly related to GH-1774.
  • [Nginx] The preferred Nginx version is now 1.10.1 (previously 1.10.0).
  • [Nginx] The preferred PCRE version is now 8.39 (previously 8.34).
  • [Standalone] Passenger Standalone now supports /dev/stdout and /dev/stderr as log file path (via `--log-file` or Passengerfile.json). This is especially useful in Docker containers. In previous versions logging to those paths did not work, resulting in nothing getting logged at all.

New in Phusion Passenger 5.0.24 (Feb 1, 2016)

  • Fixes a crash when the new `force_max_concurrent_requests_per_process` option (5.0.22) was used for non-Node.js apps (e.g. Ruby). Closes GH-1720.
  • Fixes Solaris compilation. This was a regression due to the patch for GH-1643 in 5.0.22. Closes GH-1694, GH-1701.
  • Logs for [Union Station](https://www.unionstationapp.com) provide more information about request queueing. Closes GH-1633.
  • Also log HTTP headers to Union Station for HTTP 4xx responses (extends the header logging for HTTP 5xx that was added in 5.0.22)
  • Fixes cases where compilation failure of (optional) native utils was not reported.
  • On Ruby, no longer traps SIGEXIT. This fixes erroneously setting `$ERROR_INFO` in `at_exit` callbacks. Closes GH-1730.
  • Fixes a wrong loop exit condition that could cause a deadlock with 100% CPU usage by Passenger core. Closes GH-1709, GH-1732.
  • Adds `socket_backlog` option to configure the Passenger Core socket backlog. For use with e.g. "Resource temporarily unavailable while connecting to upstream" errors. Closes GH-1726.
  • [Nginx] The preferred Nginx version is now 1.8.1 (previously 1.8.0).
  • [Standalone] Fixes the default value of the `load_shell_envvars` option. It's supposed to be disabled by default, but due to a typo it was enabled by default.

New in Phusion Passenger 5.0.23 (Feb 1, 2016)

  • Fixes the request acceptor error handling timeout. When an error occurs while Passenger is accepting a request (for example, when Passenger has run out of file descriptors), Passenger is supposed to wait for 3 seconds before trying again. Because of a typo, Passenger actually waited 3 milliseconds.
  • [Enterprise] Fixed a regression in the Passenger Standalone Nginx config template that breaks the Mass Deployment feature.
  • The mime type for serving static XHTML files is updated. We no longer use the mobile profile, so it is recognized by desktop browsers. Closes GH-1695.
  • Improves error messages about Ruby native support to indicate the optional nature. Passenger is able to operate even without the native support extension, but that wasn't clear enough to some users, causing them to think of the old messages as errors.
  • [Standalone, Nginx] When using the new `abort_websockets_on_process_shutdown` configuration option, Passenger waited for the app to close without signaling it that shutdown was in progress. Node.js apps now get a SIGINT. Closes GH-1702.
  • With friendly error pages off Passenger would still show a trace (referencing only Passenger code) for unusual spawn errors. This has been changed to a generic error message. Closes GH-1704.

New in Phusion Passenger 5.0.22 (Dec 21, 2015)

  • [Apache] Fixes compatibility with Apache 2.4.17's mod_autoindex. Fix contributed by Eric Covener. Closes GH-1642.
  • [Standalone] Passenger Standalone now [accepts configuration options from environment variables](https://www.phusionpassenger.com/library/config/standalone/intro.html). This makes using Passenger Standalone significantly easier on Heroku or on systems that follow the 12-factor principle. Closes GH-1661.
  • [Standalone] The Nginx configuration template has been cleaned up. It is now significantly easier to edit the Nginx configuration template without breaking compatibility with future versions.
  • [Standalone] The `passenger start` command now performs a sanity check on the internally generated Nginx configuration file and advises you accordingly when there is a problem.
  • [Standalone] The `passenger status` and `passenger stop` commands now respect Passengerfile.json. Closes GH-1593.
  • [Standalone] Passenger Standalone on Solaris now properly tails the application log file.
  • [Standalone] Fixes a problem with Passenger Standalone's builtin engine exiting at startup when run on Solaris.
  • [Standalone] `passenger start` now accepts the `--envvar` command line option for passing environment variables to the application.
  • [Standalone] `passenger start` now accepts the `--memory-limit` configuration option.
  • [Standalone] `passenger start` now accepts the `--max-request-queue-size` configuration option.
  • [Standalone] `passenger start` now accepts the `--debug-nginx-config` configuration option. This option allows you to view the Nginx configuration file that Passenger Standalone generates internally.
  • [Standalone, Nginx] Introduces a new configuration option: `abort_websockets_on_process_shutdown`. By default, when Passenger shuts down or restarts an application process, it will abort associated Websocket connections. This option allows you to disable that behavior. Closes GH-1686.
  • Introduces a new configuration option: `force_max_concurrent_requests_per_process`. This option is mostly useful for making dynamic process scaling work in Node.js and Meteor apps.
  • Various administration tools, such as `passenger-status`, no longer raise an flock EBADF error on Solaris. Closes GH-1643.
  • The `passenger-config reopen-logs` command, when used in combination with Passenger Standalone and the Nginx engine, now also instructs Nginx to reopen its log files. Closes GH-1674.
  • Fixes Passenger erroneously adding a `Content-Length` or `Transfer-Encoding` header to Ruby HTTP 204 No Content responses. Closes GH-1595.
  • Fixes Union Station logging of Rack response body actions.
  • The `passenger-config restart-app` command, when given `--ignore-app-not-running`, now properly exits with a zero status when one or more applications are running, but none of them belonging to the invoking user. Closes GH-1655.
  • The `passenger-config validate-install` command no longer prints false warnings about duplicate Passenger installs on systems that use RBenv. Closes GH-1627.
  • Fixes race conditions in the automatic building of the Ruby native support extension. Closes GH-1570.
  • [Enterprise] Fixes compatibility with byebug 7.0. Closes GH-1662.
  • Support Union Station logging for Node.js applications, with Express/MongoDB automatically supported.
  • The Ruby Union Station hooks no longer abort with a fatal error when the application does not call the Union Station initializer method during startup. The error is now only logged.
  • In case of an error response (HTTP 5xx), Union Station logging will also contain request headers.
  • The Union Station hooks are now more resilient against environment variable problems.

New in Phusion Passenger 5.0.20 (Oct 20, 2015)

  • Fixes memory management bugs in Union Station support.
  • Improves the error handling in Union Station support.
  • `passenger-config validate-install` now properly handles CR characters in Apache configuration files.

New in Phusion Passenger 5.0.15 (Aug 15, 2015)

  • Support SHA256 digests for the Rails asset pipeline, as used by Sprockets 3.x.
  • Support for JRuby 9.0.0.0. Closes GH-1562.
  • Fixes some bugs in Union Station support, which causes some data (such as controller information and exceptions) to not be logged.
  • The old Users Guides have been deprecated in favor of the [Passenger Library](https://www.phusionpassenger.com/library/). The Users Guides now redirect to appropriate sections in the Passenger Library.

New in Phusion Passenger 5.0.11 (Jun 23, 2015)

  • In 5.0.10, admin tools such as `passenger-status` and `passenger-config restart-app` display an authorization error if they are run without sudo, while at the same time Passenger isn't serving any applications. Since this is confusing, they have now been modified to display a more appropriate error message.

New in Phusion Passenger 5.0.10 (Jun 17, 2015)

  • It is now possible to run `passenger-status`, `passenger-config restart-app` and other admin commands without using sudo. When run without sudo, these admin commands will allow you to operate on apps and processes that are owned by the user that invoked the admin command. Closes GH-1392.
  • Fixes a crash introduces in 5.0.9 due to not properly initializing a variable. Closes GH-1530.
  • The `passenger-config reopen-logs` command now works by instructing the Watchdog process to reopen the log file, while instructing the other Passenger processes to re-inerhit the log file from the Watchdog instead of trying to reopen the log file on their own. This makes log file reopening more robust. Closes GH-1452.
  • `passenger-config restart-app` no longer leaves the terminal in a state with black background. Closes GH-1526.
  • `passenger-config admin-command` has been renamed to `passenger-config api-call` in order to avoid confusion with any potential admin interfaces that we will introduce in the future.
  • If Union Station support is enabled, process and system metrics weren't being sent correctly to Union Station. This has been fixed.
  • [Enterprise] Fixes the fact that the Passenger Enterprise RPM didn't correctly set SELinux permissions on its own files.
  • [Apache] passenger-install-apache2-module no longer aborts with an error if the Apache configuration file contains errors. Closes GH-1525.
  • [Apache] Fixes a typo that would cause passenger-install-apache2-module to crash on Red Hat and CentOS systems on which the SELinux command line tools are not installed. Closes GH-1527.

New in Phusion Passenger 5.0.7 (Apr 29, 2015)

  • Supports changed way of specifying settings for (non-bundled) Meteor apps. Closes GH-1403.
  • Fixes an integer-to-string conversion bug in the code responsible for buffering chunked request bodies. This bug could cause the PassengerAgent to crash due to an exception. Thanks to Marcus Rückert of SUSE for reporting this.
  • Request-specific environment variables are no longer cached. This fixes a number of issues, such as Shibboleth not working properly and conflicts between HTTPS and non-HTTPS virtual hosts. Closes GH-1472.
  • Fixes a memory corruption bug that would be triggered when using `passenger_base_uri`. The memory corruption bug resided in the code for resolving symlinks. Closes GH-1388.
  • Re-introduced signal catchers during shutdown, to allow clean shutdown in Foreman. Closes GH-1454.
  • `passenger-status --show=xml` no longer outputs the non-XML header by default. This fixes a regression as reported in a comment in GH-1136.
  • Passenger now prefers to load Rack and Bundler from RubyGems instead of from `vendor_ruby`. This solves some issues with Rack and Bundler on Debian systems. Closes GH-1480 and GH-1478.
  • The turbocache no longer caches responses that contain the `X-Sendfile` or the `X-Accel-Redirect` header.
  • The preferred Nginx version has been upgraded to 1.6.3.
  • The logging agent no longer aborts with an error if one of the Passenger root directory's parent directories is not world-executable. Closes GH-1487.
  • [Standalone] It is now possible to configure the Ruby, Node.js and Python executable to use in Passenger Standalone through the command line options --ruby, --nodejs and --python. Closes GH-1442.
  • [Standalone] Running `passenger start --engine=builtin --daemonize` would fail with a timeout error. This has been fixed.
  • [Standalone] Running `passenger start --nginx-version=XXX` would crash. This has been fixed. Closes GH-1490.
  • [Apache] Fixed some issues with X-Sendfile. Closes GH-1376.
  • [Apache] If the installer fails to autodetect Apache while the installer is running as a normal user, it will now ask you to give it root privileges. Closes GH-1289.
  • [Nginx] Introduces the `passenger_read_timeout` option for rare cases when server needs more than the default 10 minute timeout. Contributed by pkmiec. Closes [GH-PR-34](https://github.com/phusion/passenger/pull/34).
  • [Nginx] The Nginx module now looks for index.html if the path ends in / so that it works intuitively, without needing to use try_files.
  • Fixes wrong memory address display in crash dumps. Thanks to thoughtpolice for pointing it out.
  • Fixes an ugly backtrace that would be shown if an invalid request is made to an application process using the private HTTP interface. Contributed by jbergler. Closes GH-1311.
  • Various documentation improvements. Closes [GH-PR-1332](https://github.com/phusion/passenger/pull/1332), [GH-PR-1354](https://github.com/phusion/passenger/pull/1354), [GH-PR-1216](https://github.com/phusion/passenger/pull/1216), [GH-PR-1385](https://github.com/phusion/passenger/pull/1385), [GH-PR-1302](https://github.com/phusion/passenger/pull/1302).

New in Phusion Passenger 5.0.6 (Mar 31, 2015)

  • The turbocache no longer caches responses for which the Cache-Control header contains "no-cache". Please note that "no-cache" does not mean "do not cache this response". Instead, it means "any caching servers may only serve the cached response after validating it". Since the turbocache does not support validation, we've chosen to skip caching instead.
  • Fixes a number of memory leaks. Memory was leaked upon processing a request with multiple headers, upon processing a response with multiple headers, and upon processing a response with Set-Cookie headers. Every time such a request or response was processed, 512 bytes of memory was leaked due to improperly dereferencing relevant memory buffers. Closes GH-1455.
  • Fixes various bugs related to Union Station data collection.
  • Fixes a Union Station-related file descriptor leak. Closes GH-1439.
  • Fixes some bugs w.r.t. use of uninitialized memory.
  • More informative error message if a support binary is not found, including a resolution hint. Closes GH-1395.
  • [Apache] `SetEnv` variables are now passed as Rack/CGI/request variables. This was also the case in Passenger 4, but not in Passenger 5.0.0-5.0.5. We've restored the old behavior because the behavior in 5.0.0-5.0.5 breaks certain Apache modules such as Shibboleth. Closes GH-1446.
  • [Standalone] PID and log files now correctly created if user specifies relative path.

New in Phusion Passenger 5.0.5 (Mar 24, 2015)

  • Fixes various crashes due to use of uninitialized memory. One such crash is documented in GH-1431.
  • Fixes a connection stall in the Apache module. Closes GH-1425.
  • Fixes a potential read-past-buffer bug in string-to-integer conversion routines. Thanks to dcb314 for spotting this. Closes GH-1441.
  • There is now an API endpoint for force disconnecting a client: `passenger-config admin-command DELETE /server/.json`. Closes GH-1246.
  • Fixes some file descriptor leaks. These leaks were caused by the fact that keep-alive connections with application processes were not being closed properly. Closes GH-1439.
  • In order to more easily debug future file descriptor leaks, we've introduced the `PassengerFileDescriptorLogFile` (Apache) and `passenger_file_descriptor_log_file` (Nginx) config options. This allows Passenger to log all file descriptor open/close activity to a specific log file.
  • The `PassengerDebugLogFile` (Apache) and `passenger_debug_log_file` (Nginx) configuration options have been renamed to `PassengerLogFile` and `passenger_log_file`, respectively. The old name is support supported for backward compatibility reasons.
  • [Enterprise] Fixes a bug in Flying Passenger's `--instance-registry-dir` command line parameter. This command line parameter didn't do anything.
  • [Enterprise] The Flying Passenger daemon no longer supports the `--max-preloader-idle-time` config option. This is because the config option never worked. The correct way to set the max preloader idle time is through the Nginx config option, but this was wrongly documented, so the documentation has been fixed.

New in Phusion Passenger 5.0.2 (Mar 10, 2015)

  • Fixes a connection freeze that could occur when processing large responses. This would manifest itself under the error message "This website is under heavy load" or "Request queue is full, returning an error". Closes GH-1404.
  • When `passenger-config restart-app` is run interactively, if Passenger is not serving any applications, then the command now prints an error message instead of showing a menu with only a "Cancel" option.
  • Fixes a compilation problem on FreeBSD 10 (contributed by: clemensg). Closes GH-1401.
  • [Standalone] Fixes a crash that would occur if you use the `--ctl` parameter.
  • [Enterprise] The `--max-request-time` option has been added to Passenger Standalone.
  • [Enterprise] The `max_request_time_reached` hook has been introduced. This hook allows you to run diagnostics on a process that that took too long to respond to a request.

New in Phusion Passenger 5.0.0 RC 2 (Feb 23, 2015)

  • Fixes an installation problem with the Ruby gem due to incorrect Makefile generation. Closes GH-1382.
  • More helpful message when request queue is full. Closes GH-1375.

New in Phusion Passenger 5.0.0 RC 1 (Feb 23, 2015)

  • Fixed Date headers not being formatted in the GMT timezone. Closes GH-1367.
  • Fixed Passengerfile.json/passenger-standalone.json not being properly loaded in Passenger Standalone.
  • Fixed support for sticky sessions.
  • Fixed an infinite loop if the ApplicationPool garbage collector fails due to an exception. Closes GH-1360.
  • Fixed Passenger Standalone exiting prematurely when the HelperAgent crashes. Exiting prematurely is not supposed to happen because the watchdog will restart the HelperAgent. Closes GH-1339.
  • Fixed a crash that occurs when using a non-standard startup file value. Closes GH-1378.
  • When dumping system metrics during error page generation, the `passenger-config` command is now invoked under the same Ruby interpreter as the app, instead of the one in PATH. Closes GH-1381.
  • When a Ruby process crashes due to an uncaught exception, this fact is now properly logged.
  • Specifying 0 for the `max_pool_size` config option no longer results in a crash. Closes GH-1334.
  • The timeouts when downloading Passenger Standalone binaries and source files are now customizable. Closes GH-1295.
  • The `envvars` option is now supported in Passengerfile.json, for passing environment variables to the application. Closes GH-1377.
  • Introduced `hook_queue_full_error` for request queue overflows. Closes GH-1358.
  • [Ruby] Fixed handling of "transfer-encoding chunked" response bodies which contain zero-sized chunks.
  • [Nginx] It is no longer necessary to re-specify `passenger_enabled` in `location` contexts. Closes GH-1338.
  • [Enterprise] Fixed a bug in mass deployment reloading.
  • [Enterprise] Fixed a bug in mass deployment daemonization.
  • [Enterprise] The mass deployment mode now supports the `app_type` and `startup_file` configuration options in Passengerfile.json/passenger-standalone.json. Closes GH-1366.

New in Phusion Passenger 4.0.59 (Feb 10, 2015)

  • [Enterprise] Fixed support for free-style Node.js apps.

New in Phusion Passenger 5.0.0 Beta 3 (Feb 10, 2015)

  • The turbocache has received major updates and fixes based on excellent feedback Chris Heald and the community. First, several bugs w.r.t. the handling of caching headers have been fixed. Second, the turbocache has become slightly more conservative for security reasons. In previous versions, default cacheable responses (as defined by RFC 7234) were cached unless caching headers tell us not to. Now, default cacheable responses are only cached if caching headers explicitly tell us to. This change was introduced because there are many applications that set incorrect caching headers on private responses. This new behavior is currently not configurable, but there are plans to make it configurable in 5.0.0 release candidate 1.
  • Introduced a new configuration option, `passenger_response_buffer_high_watermark` (Nginx) and `PassengerResponseBufferHighWatermark` (Apache), for configuring the behavior of the response buffering system. Closes GH-1300.
  • Fixed more cookie handling issues. Closes GH-1310.
  • Fixed various WebSocket issues. Closes GH-1306.
  • Fixed some crashes caused by race conditions. Closes GH-1326.
  • Fixed issues with handling POST data. Closes GH-1331.
  • Fixed some issues on Heroku. Closes GH-1329.
  • Fixed some integer overflows. Fix contributed by Go Maeda. Closes GH-1357.
  • Fixed the `passenger-status --show=union_station` command. Closes GH-1336.
  • Nginx versions earlier than 1.6 are no longer supported.
  • Improved state introspection.

New in Phusion Passenger 4.0.58 (Jan 23, 2015)

  • [Enterprise] Fixed a bug in the Debian packages which caused Flying Passenger to break when used with non-system Rubies.

New in Phusion Passenger 4.0.57 (Jan 3, 2015)

  • Fixed a native extension compatibility problem with Ruby 2.2. Closes [ruby-core:67152](https://bugs.ruby-lang.org/issues/10656).
  • Fixed compatibility with Nginx 1.7.9. Closes GH-1335.

New in Phusion Passenger 4.0.56 (Dec 29, 2014)

  • Fixed a file descriptor leak that manifests when an error page is shown. Contributed by Paul Bonaud, closes GH-1325.
  • Improved Node.js request load balancing. Closes GH-1322. Thanks to Charles Vallières for the analysis.

New in Phusion Passenger 5.0.0 Beta 2 (Dec 16, 2014)

  • Fixed handling of multiple Set-Cookie headers. Closes GH-1296.
  • `passenger-config system-metrics` now works properly if the agent is installed in ~/.passenger. Closes GH-1304.
  • Documentation enhancements by Igor Vuk. Closes GH-1318.
  • Fixed some crasher bugs.
  • [Standalone] User switching is now correctly disabled.
  • [Apache] IPs set by mod_remoteip are now respected. Closes GH-1284.

New in Phusion Passenger 4.0.55 (Dec 16, 2014)

  • Supports Ruby 2.2. Closes GH-1314.
  • Fixed Linux OS name detection.

New in Phusion Passenger 5.0.0 Beta 1 (Nov 25, 2014)

  • Major changes and notable breakages are:
  • Performance has been much improved. This is thanks to months of optimization work. You can learn more at www.rubyraptor.org.
  • We've published a [server optimization guide](https://www.phusionpassenger.com/documentation/ServerOptimizationGuide.html) for those who are interested in tuning Phusion Passenger.
  • Support for Rails 1.2 - 2.2 has been removed, for performance reasons. Rails 2.3 is still supported.
  • Phusion Passenger now supports integrated HTTP caching, which we call turbocaching. If your app sets the right HTTP headers then Phusion Passenger can tremendously accelerate your app. It is enabled by default, but you can disable it with `--disable-turbocaching` (Standalone), `PassengerTurbocaching off` (Apache), or 'passenger_turbocaching off' (Nginx).
  • Touching restart.txt will no longer restart your app immediately. This is because, for performance reasons, the stat throttle rate now defaults to 10. You can still get back the old behavior by setting `PassengerStatThrottleRate 0` (Apache) or `passenger_stat_throttle_rate 0` (Nginx), but this is not encouraged. Instead, we encourage you to use the `passenger-config restart-app` tool to initiate restarts, which has immediate effect.
  • Websockets are now properly disconnected on application restarts.
  • The Phusion Passneger log levels have been completely revamped. If you were setting a log level before (e.g. through `passenger_log_level`), please read the latest documentation to learn about the new log levels.
  • If you use out-of-band garbage collection, beware that the `X-Passenger-Request-OOB-Work` header has now been renamed to `!~Request-OOB-Work`.
  • When using Rack's full socket hijacking, you must now output an HTTP status line.
  • [Nginx] The `passenger_set_cgi_param` option has been removed and replaced by `passenger_set_header` and `passenger_env_var`.
  • [Nginx] `passenger_show_version_in_header` is now only valid in the `http` context.
  • [Apache] The `PassengerStatThrottleRate` option is now global.
  • Minor changes:
  • The minimum required Nginx version is now 1.6.0.
  • The instance directory is now touched every hour instead of every 6 hours. This should hopefully prevent more problems with /tmp cleaner daemons.
  • Applications are not grouped not only on the application root path, but also on the environment. For example, this allows you to run the same app in both production and staging mode, with only a single directory, without further configuration. Closes GH-664.
  • The `passenger_temp_dir` option (Nginx) and the `PassengerTempDir` option (Apache) have been replaced by two config options. On Nginx they are `passenger_instance_registry_dir` and `passenger_data_buffer_dir`. On Apache they are `PassengerInstanceRegistryDir` and `PassengerDataBufferDir`. On Apache, `PassengerUploadBufferDir` has been replaced by `PassengerDataBufferDir`.
  • Command line tools no longer respect the `PASSENGER_TEMP_DIR` environment variable. Use `PASSENGER_INSTANCE_REGISTRY_DIR` instead.
  • `passenger-status --show=requests` has been deprecated in favor of `passenger-status --show=connections`.
  • Using the SIGUSR1 signal to restart a Ruby app without dropping connections, is no longer supported. Instead, use `passenger-config detach-process`.
  • Introduced the `passenger-config reopen-logs` command, which instructs all Phusion Passenger agent processes to reopen their log files. You should call this after having rotated the web server logs.
  • [Standalone] The Phusion Passenger Standalone config template has changed. Users are encouraged to update it.
  • [Standalone] `passenger-standalone.json` has been renamed to `Passengerfile.json`.
  • [Standalone] `passenger-standalone.json`/`Passengerfile.json` no longer overrides command line options. Instead, command line options now have the highest priority.

New in Phusion Passenger 4.0.53 (Oct 1, 2014)

  • Upgraded the preferred Nginx version to 1.6.2.
  • Improved RVM gemset autodetection.
  • Fixed some Ruby 2.2 compatibility issues.

New in Phusion Passenger 4.0.52 (Sep 24, 2014)

  • Fixed a null termination bug when autodetecting application types.
  • Node.js apps can now also trigger the inverse port binding mechanism by passing `'/passenger'` as argument. This was introduced in order to be able to support the Hapi.js framework. Please read http://stackoverflow.com/questions/20645231/phusion-passenger-error-http-server-listen-was-called-more-than-once/20645549 for more information regarding Hapi.js support.
  • It is now possible to abort Node.js WebSocket connections upon application restart. Please refer to https://github.com/phusion/passenger/wiki/Phusion-Passenger:-Node.js-tutorial#restarting_apps_that_serve_long_running_connections for more information. Closes GH-1200.
  • Passenger Standalone no longer automatically resolves symlinks in its paths.
  • `passenger-config system-metrics` no longer crashes when the system clock is set to a time in the past. Closes GH-1276.
  • `passenger-status`, `passenger-memory-stats`, `passenger-install-apache2-module` and `passenger-install-nginx-module` no longer output ANSI color codes by default when STDOUT is not a TTY. Closes GH-487.
  • `passenger-install-nginx-module --auto` is now all that's necessary to make it fully non-interactive. It is no longer necessary to provide all the answers through command line parameters. Closes GH-852.
  • Minor contribution by Alessandro Lenzen.

New in Phusion Passenger 4.0.50 (Sep 4, 2014)

  • Fixed a potential heap corruption bug.
  • Added Union Station support for Rails 4.1.

New in Phusion Passenger 4.0.49 (Sep 4, 2014)

  • Upgraded the preferred Nginx version to 1.6.1.
  • Fixed a crash that may be triggered by the `passenger_max_requests` feature.
  • Introduced the `spawn_failed` hook, which is called when an application process fails to spawn. You could use this hook to setup an error notification system. Closes GH-1252.
  • Fonts, RSS and XML are now gzip-compressed by default in Phusion Passenger Standalone. Thanks to Jacob Elder. Closes GH-1254.
  • Fixed some user and group information lookup issues. Closes GH-1253.
  • Fixed some request handling crashes. Closes GH-1250.
  • Fixed some compilation problems on Gentoo. Closes GH-1261.
  • Fixed some compilation problems on Solaris. Closes GH-1260.

New in Phusion Passenger 4.0.48 (Jul 25, 2014)

  • Fixed a race condition while determining what user an application should be executed as. This bug could lead to applications being run as the wrong user. Closes GH-1241.
  • [Standalone] Improved autodetection of Rails asset pipeline files. This prevents Standalone from incorrectly setting caching headers on non-asset pipeline files. Closes GH-1225.
  • Fixed compilation problems on CentOS 5. Thanks to J. Smith. Closes GH-1247.
  • Fixed compilation problems on OpenBSD.
  • Fixed compatibility with Ruby 1.8.5.

New in Phusion Passenger 4.0.46 (Jul 15, 2014)

  • Further improved Node.js and Socket.io compatibility.
  • Sticky session cookies have been made more reliable.
  • Fixed WebSocket upgrade issues on Firefox. Closes GH-1232.
  • The Python application loader now inserts the application root into `sys.path`. The fact that this was not done previously caused a lot of confusion amongst Python users, who wondered why their `passenger_wsgi.py` could not import any modules from the same directory.
  • Fixed a compatibility problem with Django, which could cause Django apps to freeze indefinitely. Closes GH-1215.
  • Logging of application spawning errors has been much improved. Full details about the error, such as environment variables, are saved to a private log file. In the past, these details were only viewable in the browser. This change also fixes a bug on Phusion Passenger Enterprise, where enabling Deployment Error Resistance causes error messages to get lost. Closes GH-1021 and GH-1175.
  • Fixed a regression in Node.js support. When a Node.js app is deployed on a HTTPS host, the `X-Forwarded-Proto` header wasn't set in 4.0.45. Closes GH-1231.
  • Passenger Standalone no longer, by default, loads shell startup files before loading the application. This is because Passenger Standalone is often invoked from the shell anyway. Indeed, loading shell startup files again can interfere with any environment variables already set in the invoking shell. You can still tell Passenger Standalone to load shell startup files by passing `--load-shell-envvars`. Passenger for Apache and Passenger for Nginx still load shell startup files by default.
  • Passenger Standalone now works properly when the HOME environment variable isn't set. Closes GH-713.
  • Passenger Standalone's `package-runtime` command has been removed. It has been broken for a while and has nowadays been obsolete by our automatic [binary generation system](https://github.com/phusion/passenger_autobuilder). Closes GH-1133.
  • The `passenger_startup_file` option now also works on Python apps. Closes GH-1233.
  • If you are a [Union Station](https://www.unionstationapp.com) customer, then Phusion Passenger will now also log application spawning errors to Union Station. This data isn't shown in the Union Station interface yet, but it will be implemented in the future.
  • Fixed compilation problems on OmniOS and OpenIndiana. Closes GH-1212.
  • Fixed compilation problems when Nginx is configured with OpenResty. Thanks to Yichun Zhang. Closes GH-1226.
  • Fixed Nginx HTTP POST failures on ARM platforms. Thanks to nocelic for the fix. Closes GH-1151.
  • Documentation contributions by Tim Bishop and Tugdual de Kerviler.
  • Minor Nginx bug fix by Feng Gu. Closes GH-1235.

New in Phusion Passenger 4.0.45 (Jun 12, 2014)

  • Major improvements in Node.js and Meteor compatibility. Older Phusion Passenger versions implemented Node.js support by emulating Node.js' HTTP library. This approach was found to be unsustainable, so we've abandoned that approach and replaced it with a much simpler approach that does not involve emulating the HTTP library.
  • Introduced support for sticky sessions. Sticky sessions are useful -- or even required -- for apps that store state inside process memory. Prominent examples include SockJS, Socket.io, faye-websocket and Meteor. Sticky sessions are required to make the aforementioned examples work in multi-process scenarios. By introducing sticky sessions support, we've much improved WebSocket support and support for the aforementioned libraries and frameworks.
  • Due to user demand, GET requests with request bodies are once again supported. Support for these kinds of requests was removed in 4.0.42 in an attempt to increase the strictness and robustness of our request handling code. It has been determined that GET requests with request bodies can be adequately supported without degrading robustness in Phusion Passenger. However, GET requests with both request bodies and WebSocket upgrade headers are unsupported. Fixes issue #1092.
  • [Enterprise] The [Flying Passenger](http://www.modrails.com/documentation/Users guide Apache.html#flying_passenger) feature is now also available on Apache.
  • Fixed some issues with RVM mixed mode support, issue #1121.
  • Fixed Passenger Standalone complaining about not finding PassengerHelperAgent during startup.
  • Fixed various minor issues such as #1190 and #1197.
  • The download timeout for passenger-install-nginx-module has been increased.

New in Phusion Passenger 4.0.44 (May 30, 2014)

  • The issue tracker has now been moved from Google Code to Github. Before version 4.0.44 (May 29 2014, commit 3dd0964c9f4), all issue numbers referred to Google Code. From now on, all issue numbers will refer to Github Issues.
  • Fixed compilation problems on OS X Lion and OS X Mountain Lion.
  • On Ruby, fixed `nil` being frozen on accident in some cases.

New in Phusion Passenger 4.0.43 (May 29, 2014)

  • Introduced a new command `passenger-config list-instances`, which prints all running Phusion Passenger instances.
  • Introduced a new command `passenger-config system-metrics, which displays metrics about the system such as the total CPU and memory usage.
  • Fixed some compilation problems caused by the compiler capability autodetector.
  • System metrics such as total CPU usage and memory usage, are now sent to [Union Station](https://www.unionstationapp.com) in preparation for future features.

New in Phusion Passenger 4.0.42 Beta (May 7, 2014)

  • [Nginx] Upgraded the preferred Nginx version to 1.6.0.
  • [Nginx] Fixed compatibility with Nginx 1.7.0.
  • [Standalone] The MIME type for .woff files has been changed to application/font-woff. Fixes issue #1071.
  • There are now APT packages for Ubuntu 14.04. At the same time, packages for Ubuntu 13.10 have been abandoned.
  • Introduced a new command, `passenger-config build-native-support`, for ensuring that the native_support library for the current Ruby interpreter is built. This is useful in system provisioning scripts.
  • For security reasons, friendly error pages (those black/purple pages that shows the error message, backtrace and environment variable dump when an application fails to start) are now disabled by default when the application environment is set to 'staging' or 'production'. Fixes issue #1063.
  • Fixed some compilation warnings on Ubuntu 14.04.
  • Fixed some compatibility problems with Rake 10.2.0 and later. See [Rake issue 274](https://github.com/jimweirich/rake/issues/274).
  • Improved error handling in [Union Station](https://www.unionstationapp.com) support.
  • Data is now sent to Union Station on a more frequent basis, in order to make new data show up more quickly.
  • Information about the code revision is now sent to Union Station, which will be used in the upcoming deployment tracking feature in Union Station 2.

New in Phusion Passenger 4.0.41 (Apr 14, 2014)

  • Fixed some issues with printing UTF-8 log files on Heroku.
  • Added a new flag `--ignore-app-not-running` to `passenger-config restart-app`. When this flag is given, `passenger-config restart-app` will exit successfully when the specified application is not running, instead of exiting with an error.
  • Our precompiled Passenger Standalone binaries have been upgraded to use OpenSSL 1.0.1g, which fixes [the OpenSSL Heartbleed vulnerability](http://heartbleed.com/). Users who are using Passenger Standalone with SSL enabled are vulnerable, and should upgrade immediately. Users who do not use Passenger Standalone, users who use Passenger Standalone without SSL, or users who use Passenger Standalone with SSL behind another SSL-enabled reverse proxy, are not vulnerable.

New in Phusion Passenger 4.0.40 (Mar 20, 2014)

  • Upgraded preferred Nginx version to 1.4.7. This Nginx version fixes a buffer overflow. Users are strongly urged to upgrade Nginx as soon as possible.

New in Phusion Passenger 4.0.39 (Mar 18, 2014)

  • Fixed a crash that could happen if the client disconnects while a chunked response is being sent. Fixes issue #1062.
  • In Phusion Passenger Standalone, it is now possible to customize the Nginx configuration file on Heroku. It is now also possible to permanently apply changes to the Nginx configuration file, surviving upgrades. Please refer to the "Advanced configuration" section of the Phusion Passenger Standalone manual for more information.
  • The programming language selection menu in passenger-install-apache2-module and passenger-install-nginx-module only works on terminals that support UTF-8 and that have a UTF-8 capable font. To cater to users who cannot meet these requirements (e.g. PuTTY users using any of the default Windows fonts), it is now possible to switch the menu to a plain text mode by pressing '!'. Fixes issue #1066.
  • Fixed printing UTF-8 characters in log files in Phusion Passenger Standalone.
  • It is now possible to dump live backtraces of Python apps through the 'SIGABRT' signal.
  • Fixed closing of file descriptors on OS X 10.9.
  • Fixed compilation problems with Apple Clang 503.0.38 on OS X.
  • Fixed compilation of native_support on Rubinius.

New in Phusion Passenger 4.0.38 (Mar 11, 2014)

  • Added support for the new Ruby 2.1.0 out-of-band garbage collector. This can much improve garbage collection performance, and drastically reduce request times.
  • Fixed a symlink-related security vulnerability.
  • Passenger Standalone is now compatible with IPv6.
  • Fixed some compilation problems on Solaris. See issue #1047.
  • passenger-install-apache2-module and passenger-install-nginx-module now automatically run in `--auto` mode if stdin is not a TTY. Fixes issue #1030.
  • Fixed an issue with non-bundled Meteor apps not correctly running in production mode.
  • The `PassengerPreStart` option is now compatible with IPv6 server sockets.
  • When running Python WSGI apps, `wsgi.run_once` is now set to False. This should improve the performance of certain apps and frameworks.
  • When handling HTTP requests with chunked transfer encoding, the 'Transfer-Encoding' header is no longer passed to the application. This is because the web server already buffers and dechunks the request body.
  • Fixed a possible hang in Phusion Passenger for Nginx when Nginx is instructed to reload or reopen log files. Thanks to Feng Gu, [pull request #97](https://github.com/phusion/passenger/pull/97).
  • The preferred Nginx version has been upgraded to 1.4.6.
  • Fixed a problem with running passenger-install-apache2-module and passenger-install-nginx-module on JRuby. They were not able to accept any terminal input after displaying the programming language menu.

New in Phusion Passenger 4.0.37 (Jan 29, 2014)

  • Improved Node.js compatibility. Calling on() on the request object now returns the request object itself. This fixes some issues with Express, Connect and Formidable. Furthermore, some WebSocket-related issues have been fixed.
  • Improved Meteor support. Meteor application processes are now shut down quicker. Previously, they linger around for 5 seconds while waiting for all connections to terminate, but that didn't work well because WebSocket connections were kept open indefinitely. Also, some WebSocket-related issues have been fixed.
  • Introduced a new tool `passenger-config detach-process` for gracefully detaching an application process from the process pool. Has a similar effect to killing the application process directly with `kill `, but killing directly may cause the HTTP client to see an error, while using this command guarantees that clients see no errors.
  • Fixed a crash occurs when an application fails to spawn, but the HTTP client disconnects before the error page is generated. Fixes issue #1028.
  • Fixed a symlink-related security vulnerability.

New in Phusion Passenger 4.0.36 (Jan 25, 2014)

  • [Enterprise] Fixed some Mass Deployment bugs.
  • [Enterprise] Fixed a bug that causes an application group to be put into Deployment Error Resistance Mode if rolling restarting fails while deployment error resistance is off. Deployment Error Resistance Mode is now only activated if it's explicitly turned on.
  • Passenger Standalone now gzips JSON responses.
  • Fixed some cases in which Passenger Standalone does not to properly cleanup its temporary files.

New in Phusion Passenger 4.0.35 (Jan 25, 2014)

  • Fixed some unit tests.

New in Phusion Passenger 4.0.34 (Jan 16, 2014)

  • The Node.js loader code now sets the `isApplicationLoader` attribute on the bootstrapping module. This provides a way for apps and frameworks that check for `module.parent` to check whether the current file is loaded by Phusion Passenger, or by other software that work in a similar way.
  • Improved support for Meteor in development mode. Terminating Phusion Passenger now leaves less garbage Meteor processes behind.
  • It is now possible to disable the usage of the Ruby native extension by setting the environment variable `PASSENGER_USE_RUBY_NATIVE_SUPPORT=0`.
  • Fixed incorrect detection of the Apache MPM on Ubuntu 13.10.
  • When using RVM, if you set PassengerRuby/passenger_ruby to the raw Ruby binary instead of the wrapper script, Phusion Passenger will now print an error.
  • Added support for RVM >= 1.25 wrapper scripts.
  • Fixed loading passenger_native_support on Ruby 1.9.2.
  • The Union Station analytics code now works even without native_support.
  • Fixed `passenger-install-apache2-module` and `passenger-install-nginx-module` in Homebrew.
  • Binaries are now downloaded from an Amazon S3 mirror if the main binary server is unavailable.
  • And finally, although this isn't really a change in 4.0.34, it should be noted. In version 4.0.33 we changed the way Phusion Passenger's own Ruby source files are loaded, in order to fix some Debian and RPM packaging issues.

New in Phusion Passenger 4.0.33 (Jan 6, 2014)

  • Fixed a compatibility problem in passenger-install-apache2-module with Ruby 1.8. The language selection menu didn't work properly.

New in Phusion Passenger 4.0.29 (Dec 13, 2013)

  • Fixed a compilation problem on OS X Mavericks.

New in Phusion Passenger 4.0.28 (Dec 13, 2013)

  • Introduced a workaround for a GCC 4.6 bug. This bug could cause Phusion Passsenger to crash during startup. Affected operating systems include Ubuntu 12.04 and Amazon Linux 2013.09.01, though not every machine with this OS installed exhibits the problem. See issue #902.
  • Improved Node.js support: the Sails framework is now supported.
  • Improved Node.js support: the streams2 API is now supported.
  • Introduced support for hooks, allowing users to easily extend Phusion Passenger's behavior.
  • Fixed a bug in the `passenger start -R` option. It was broken because of a change introduced in 4.0.25.
  • Fixed a bug in PassengerMaxInstancesPerApp. Fixes issue #1016.
  • Fixed compilation problems on Solaris.
  • Fixed an encoding problem in the Apache autodetection code. Fixes issue #1026.
  • The Debian packages no longer depend on libruby.
  • Application stdout and stderr are now printed without normal Phusion Passenger debugging information, making them easier to read.

New in Phusion Passenger 4.0.27 (Dec 6, 2013)

  • [Apache] Fixed a bug in the Apache module which could lock up the Apache process or thread. This is a regression introduced in version 4.0.24.
  • Node.js application processes now have friendly process titles.

New in Phusion Passenger 4.0.26 (Nov 28, 2013)

  • Introduced the `PassengerBufferUpload` option for Apache. This option allows one to disable upload buffering, e.g. in order to be able to track upload progress.
  • [Nginx] The `HTTPS` variable is now set correctly for HTTPS connections, even without setting `ssl on`. Fixes issue #401.
  • [Standalone] It is now possible to listen on both a normal HTTP and an HTTPS port.
  • [Enterprise] The `passenger-status` tool now displays rolling restart status.

New in Phusion Passenger 4.0.25 (Nov 21, 2013)

  • The `PassengerEnv`/`passenger_env`/`--environment` option now also sets NODE_ENV, so that Node.js frameworks like Connect can properly respond to the environment.
  • Fixed a bug in our Debian/Ubuntu packages causing `passenger-install-nginx-module`not to be able to compile Nginx.
  • Arbitrary Node.js application structures are now supported.
  • [Nginx] Introduced the `passenger_restart_dir` option.
  • [Nginx] Upgraded preferred Nginx version to 1.4.4 because of CVE-2013-4547.

New in Phusion Passenger 4.0.24 (Nov 14, 2013)

  • Introduced the `PassengerNodejs` (Apache) and `passenger_nodejs` (Nginx) configuration options.
  • [Apache] Introduced the `PassengerErrorOverride` option, so that HTTP error responses generated by applications can be intercepted by Apache and customized using the `ErrorDocument` directive.
  • [Standalone] It is now possible to specify some configuration options in a configuration file `passenger-standalone.json`. When Passenger Standalone is used in Mass Deployment mode, this configuration file can be used to customize settings on a per-application basis.
  • [Enterprise] Fixed a potential crash when a rolling restart is triggered while a process is already shutting down.
  • [Enterprise] Fixed Mass Deployment support for Node.js and Meteor.

New in Phusion Passenger 4.0.23 (Nov 2, 2013)

  • Fixed compilation problems on GCC 4.8.2 (e.g. Arch Linux 2013-10-27).
  • Fixed a compatibility problem with Solaris /usr/ccs/bin/make: issue #999.
  • Support for the Meteor Javascript framework has been open sourced.

New in Phusion Passenger 4.0.22 (Nov 2, 2013)

  • [Enterprised] Fixed compilation problems on OS X Mavericks.

New in Phusion Passenger 4.0.21 (Oct 25, 2013)

  • [Nginx] Upgraded the preferred Nginx version to 1.4.3.
  • Prelimenary OS X Mavericks support.
  • Work around an Apache packaging bug in CentOS 5.
  • Various user friendliness improvements in the documentation and the installers.
  • Fixed a bug in the always_restart.txt support. Phusion Passenger was looking for it in the wrong directory.
  • Many Solaris and Sun Studio compatibility fixes. Special thanks to "mark" for his extensive assistance.
  • [Standalone] The --temp-dir command line option has been introduced.

New in Phusion Passenger 4.0.20 (Oct 9, 2013)

  • Fixed a bug in Phusion Passenger Standalone's daemon mode. When in daemon mode, the Nginx temporary directory was deleted prematurely, causing some POST requests to fail. This was a regression that was introduced in 4.0.15 as part of an optimization.
  • Fixed compilation problems on Solaris 10 with Sun Studio 12.3.
  • Improved detection of RVM problems.
  • It is now possible to log the request method to Union Station.
  • Introduced a new option, `PassengerLoadShellEnvvars` (Apache) and `passenger_load_shell_envvars` (Nginx). This allows enabling or disabling the loading of bashrc before spawning the application.
  • [Enterprise] Fixed a packaging problem which caused the flying-passenger executable not to be properly included in the bin path.
  • [Enterprise] Fixed a race condition which sometimes causes the Flying Passenger socket to be deleted after a restart. Fixes issue #939.
  • [Enterprise] The `byebug` gem is now supported for debugging on Ruby 2.0. The byebug gem requires a patch before this works: https://github.com/deivid-rodriguez/byebug/pull/29

New in Phusion Passenger 4.0.19 (Sep 24, 2013)

  • Fixed a problem with response buffering. Application processes are now properly marked available for request processing immediately after they're done sending the response, instead of after having sent the entire response to the client.
  • The "processed" counter in `passenger-status` is now bumped after the process has handled a request, not at the beginning.
  • [Enterprise] Fixed an off-by-one bug in the `passenger_max_processes` setting.

New in Phusion Passenger 4.0.18 (Sep 18, 2013)

  • The Enterprise variant of Phusion Passenger Standalone now supports customizing the concurrency model and thread count from the command line.
  • On Nginx, the Enterprise license is now only checked if Phusion Passenger is enabled in Nginx. This allows you to deploy Nginx binaries, that have Phusion Passenger Enterprise compiled in, to servers that are not actually running Phusion Passenger Enterprise.
  • Fixed a performance bug in the Union Station support code. In certain cases where a lot of data must be sent to Union Station, the code is now over 100 times faster.
  • `passenger-status --show=union_station` now displays all clients that are connected to the LoggingAgent.
  • Added a workaround for Heroku so that exited processes are properly detected as such.
  • When using Phusion Passenger Standalone with Foreman, pressing Ctrl-C in Foreman no longer results in runaway Nginx processes.
  • Fixed backtraces in the Apache module.

New in Phusion Passenger 4.0.17 (Sep 10, 2013)

  • Fixed compilation problems on GCC 4.8 systems, such as Arch Linux 2013.04. Fixes issue #941.
  • Fixed some deprecation warnings when compiling the Ruby native extension on Ruby 2.0.0.
  • Fixed some Union Station-related stability issues.

New in Phusion Passenger 4.0.16 (Sep 6, 2013)

  • Allow Phusion Passenger to work properly on systems where the user's GID does not have a proper entry in /etc/group, such as Heroku.

New in Phusion Passenger 4.0.15 (Sep 6, 2013)

  • Out-of-band work has been much improved. The number of processes which may perform out-of-band work concurrently has been limited to 1. Furthermore, processes which are performing out-of-band work are now included in the max pool size constraint calculation. However, this means that in order to use out-of-band work, you need to have at least 2 application processes running. Out-of-band work will never be triggered if you just have 1 process. Partially fixes issue #892.
  • Phusion Passenger now displays an error message to clients if too many requests are queued up. By default, "too many" is 100. You may customize this with `PassengerMaxRequestQueueSize` (Apache) or `passenger_max_request_queue_size` (Nginx).
  • A new configuration option, `PassengerStartTimeout` (Apache) and `passenger_start_timeout` (Nginx), has been added. This option allows you to specify a timeout for application startup. The startup timeout has exited since version 4.0.0, but before version 4.0.15 it was hardcoded at a value of 90 seconds. Now it is customizable. Fixes issue #936.
  • [Enterprise] The `PassengerMaxRequestTime`/`passenger_max_request_time` feature is now available for Python and Node.js as well, and is no longer limited to just Ruby. Fixes issue #938.
  • [Nginx] Introduced a configuration option `passenger_intercept_errors`, which decides if Nginx will intercept responses with HTTP status codes of 400 and higher. Its effect is similar to `proxy_intercept_errors`.
  • [Standalone] Memory usage optimization: when `passenger start` is run with `--daemonize`, the frontend exits after starting the Nginx core. This saves ~20 MB of memory per `passenger start` instance.
  • [Standalone] Phusion Passenger Standalone is now also packaged in the Debian packages.
  • [Standalone] Fix a problem with the `passenger stop` command on Ruby 1.8.7. The 'thread' library was not properly required, causing a crash.
  • [Standalone] There is now builtin support for SSL.
  • Fix a crash when multiple `passenger_pass_header` directives are set. Fixes issue #934.
  • Permissions on the server instance directory are now explicitly set with chmod, so that permissions are correct on systems with a non-default umask. Fixes issue #928.
  • Fix permission problems when running `passenger start` with `--user`.
  • `passenger-config --detect-apache2` now correctly detects the eror log filename on Amazon Linux. Fixes issue #933.
  • An environment variable `PASSENGER_THREAD_LOCAL_STORAGE` has been added to the build system for forcefully disabling the use of thread-local storage within the Phusion Passenger codebase. This flag useful on systems that have broken support for thread-local storage, despite passing our build system's check for proper thread-local storage support. At the time of writing, one user has reported that Ubuntu 12.04 32-bit has broken thread-local storage report although neither the reporter nor us were able to reproduce the problem on any other systems running Ubuntu 12.04 32-bit. Note that this flag has no effect on non-Phusion Passenger code. Fixes issue #937.
  • It is now possible to preprocess events before they are sent to Union Station.

New in Phusion Passenger 4.0.14 (Sep 4, 2013)

  • Fixed a bug in Passenger Standalone's source compiler, for the specific case when the downloaded Nginx binary doesn't work, and compilation of the Nginx binary did not succeed the first time (e.g. because of missing dependencies).
  • Precompiled Ruby native extensions are now automatically downloaded.

New in Phusion Passenger 4.0.13 (Aug 16, 2013)

  • Updated preferred Nginx version to 1.4.2.
  • Worked around the fact that FreeBSD 9.1 has a broken C++ runtime. Patch contributed by David Keller.
  • Autogenerated HTTP Date headers are now in UTC instead of local time. This could cause cookies to have the wrong expiration time. Fixes issue #913.
  • Fixed compatibility problems with Ruby 1.8.6 (issue #924).
  • Introduced a tool, `passenger-config --detect-apache2`, which autodetects all Apache installations on the system along with their parameters (which apachectl command to run, which log file to read, which config file to edit). The tool advises users about how to use that specific Apache installation. Useful if the user has multiple Apache installations but don't know about it, or when the user doesn't know how to work with multiple Apache installations.
  • Added an API for better Rack socket hijacking support.
  • Added a hidden configuration option for customizing the application start timeout. A proper configuration option will be introduced in the future.
  • Added autodetection support for Amazon Linux.
  • Fixed process metrics collection on some operating systems. Some systems' 'ps' command expect no space between -p and the list of PIDs.

New in Phusion Passenger 4.0.10 (Jul 17, 2013)

  • Fixed a crash in PassengerWatchdog which occurs on some OS X systems.
  • Fixed exception reporting to Union Station.
  • Improved documentation.

New in Phusion Passenger 4.0.9 (Jul 17, 2013)

  • [Enterprise] Fixed a problem with passenger-irb.

New in Phusion Passenger 4.0.8 (Jul 9, 2013)

  • Fixed a problem with graceful web server restarts. When you gracefully restart the web server, it would cause Phusion Passenger internal sockets to be deleted, thus causing Phusion Passenger to go down. This problem was introduced in 4.0.6 during the attempt to fix issue #910.
  • The PassengerRestartDir/passenger_restart_dir now accepts relative filenames again, just like in Phusion Passenger 3.x. Patch contributed by Ryan Schwartz.
  • Documentation updates contributed by Gokulnath Manakkattil.
  • [Enterprise] Fixed a license key checking issue on some operating systems, such as CentOS 6.

New in Phusion Passenger 4.0.7 (Jul 5, 2013)

  • There was a regression in 4.0.6 that sometimes prevents PassengerLoggingAgent from starting up. Unfortunately this slipped our release testing. This regression has been fixed and we've updated our test suite to check for these kinds of regressions.

New in Phusion Passenger 4.0.6 (Jul 5, 2013)

  • Fixed a potential 100% CPU lock up in the crash handler, which only occurs on OS X. Fixes issue #908.
  • Fixed a crash in request handling, when certain events are trigger after the client has already disconnected. Fixes issue #889.
  • Phusion Passenger will no longer crash when the Phusion Passenger native_support Ruby extension cannot be compiled, e.g. because the Ruby development headers are not installed or because the current user has no permission to save the native extension file. Fixes issue #890.
  • Fixed OS X 10.9 support. Fixes issue #906.
  • Removed dependency on bash, so that Phusion Passenger works out of the box on BSD platforms without installing/configuring bash. Fixes issue #911.
  • Fix 'PassengerPoolIdleTime 0' not being respected correctly. Issue #904.
  • Admin tools improvement: it is now possible to see all currently running requests by invoking `passenger-status --show=requests`.
  • A new feature called Flying Passenger allows you to decouple the life time of Phusion Passenger from the web server, so that both can be restarted indepedently from each other. Please refer to http://blog.phusion.nl/2013/07/03/technology-preview-introducing-flying-passenger/ for an introduction.
  • [Apache] Fixed compatibility with Apache pipe logging. Previously this would cause Phusion Passenger to lock up with 100% CPU during Apache restart.
  • [Nginx] The Nginx configure script now checks whether 'ruby' is in $PATH. Previously, if 'ruby' is not in $PATH, then the compilation process fails with an obscure error.
  • [Nginx] passenger-install-nginx-module now works properly even when Phusion Passenger is installed through the Debian packages. Before, the installer would tell you to install Phusion Passenger through the gem or tarball instead.
  • [Enterprise] Added pretty printing helpers to the Live IRB Console.
  • Fixed permissions on a subdirectory in the server instance directory. The server instance directory is a temporary directory that Phusion Passenger uses to store working files, and is deleted after Phusion Passenger exits. A subdirectory inside it is world-writable (but not world-readable) and is used for storing Unix domain sockets created by different apps, which may run as different users. These sockets had long random filenames to prevent them from being guessed. However because of a typo, this subdirectory was created with the setuid bit, when it should have sticky bit (to prevent existing files from being deleted or renamed by a user that doesn't own the file). This has now been fixed.
  • If the server instance directory already exists, it will now be removed first in order get correct directory permissions. If the directory still exists after removal, Phusion Passenger aborts to avoid writing to a directory with unexpected permissions. Fixes issue #910.
  • The installer now checks whether the system has enough virtual memory, and prints a helpful warning if it doesn't.
  • Linux/AArch64 compatibility fixes. Patch contributed by Dirk Mueller.
  • Improved documentation.

New in Phusion Passenger 4.0.5 (May 30, 2013)

  • [Standalone] Fixed a regression that prevented Passenger Standalone from starting. Fixes issue #899.
  • Fixed security vulnerability CVE-2013-2119.

New in Phusion Passenger 4.0.4 (May 28, 2013)

  • Fixed auto-detection of noexec-mount /tmp directory. Fixes issue #850 and issue #625.
  • Fixed a WSGI bug. wsgi.input was a file object opened in text mode, but should be opened in binary mode. Fixes issue #881.
  • Fixed a potential crash in Out-of-Band Work. Fixes issue #894.
  • Fixed a potential crash in rolling restarting, which only occurs if a process was also being spawned at the same time. Fixes issue #896.
  • [Apache] The RailsBaseURI and RackBaseURI directives have been unified. For a long time, RailsBaseURI told Phusion Passenger that the given sub-URI belongs to a **Rails 2** application. Attempt to use this directive with Rails 3 or with Rack applications would result in an error. Because this confused users, RailsBaseURI and RackBaseURI have now been unified and can now be used interchangably. Phusion Passenger will automatically detect what kind of application it is. The Nginx version already worked like this. Fixes issue #882.
  • [Standalone] The Passenger Standalone temp directory and PassengerWatchdog server instance directory have been unified. PassengerWatchdog already automatically updates the timestamps of all files in its server instance directory every 6 hours to prevent /tmp cleaners from deleting the directory. Therefore this unification prevents the Passenger Standalone temp directory to be deleted by /tmp cleaners as well. Fixes issue #654.
  • [Standalone] types_hash_max_size has been increased from 1024 to 2048. This solves a problem that causes Nginx not to start on some platforms. Contributed by Jan-Willem Koelewijn.

New in Phusion Passenger 4.0.3 (May 25, 2013)

  • Better protection is now provided against application processes that are stuck and refuse to shut down cleanly. Since version 4.0.0, Phusion Passenger already forcefully shuts down all processes during web server shutdown. In addition to this, 4.0.3 now also forcefully shuts down processes that take more than 1 minute to shut down, even outside the context of web server shutdowns. This feature does not, however, protect against requests that take too long. Use PassengerMaxRequestTime (Apache) or passenger_max_request_time (Nginx) for that.
  • Fixed a crash in the HelperAgent which results in frequent process restarts in some traffic patterns. Fixes issue #862.
  • Fixed a problem that prevents processes from being spawned correctly if the user's bashrc changes working directory. Fixes issue #851.
  • passenger-status now also displays CPU usage.
  • The installer now checks for checksums when automatically downloading PCRE and Nginx. Contributed by Joshua Lund.
  • An error is now printed when trying to daemonize Phusion Passenger Standalone on Ruby implementations that don't support forking. Contributed by Benjamin Fleischer.
  • Although Phusion Passenger already supported JRuby, *installing* Phusion Passenger with JRuby was not possible. This has been fixed.
  • Various other minor bug fixes.

New in Phusion Passenger 4.0.2 (May 8, 2013)

  • Bumped the preferred Nginx version to 1.4.1 because of a critical Nginx security vulnerability, CVE-2013-2028. Users are advised to upgrade immediately.

New in Phusion Passenger 4.0.1 (May 7, 2013)

  • Fixed a crasher bug in the Deployment Error Resistance feature.
  • Fixed a bug in PassengerDefaultUser and PassengerDefaultGroup.
  • Fixed a bug which could cause application processes to exit before they've finished their request.
  • Fixed some small file descriptor leaks.
  • Bumped the preferred Nginx version to 1.4.0.
  • Editing the Phusion Passenger Standalone Nginx config template is no longer discouraged.
  • Improved documentation.

New in Phusion Passenger 4.0 RC 6 (Apr 9, 2013)

  • The default config snippet for Apache has changed! It must now contain a PassengerDefaultRuby option. The installer has been updated to output this option. The PassengerRuby option still exists, but it’s only used for configuring different Ruby interpreters in different contexts. Please refer to the manual for more information.
  • We now provide GPG digital signatures for all file releases by Phusion. More information can be found in the manual.
  • WebSocket support on Nginx. Requires Nginx >= 1.3.15.
  • passenger-status now displays process memory usage and time when it was last used. The latter fixes issue #853.
  • Exceptions in Rack application objects are now caught to prevent application processes from exiting.
  • The passenger-config tool now supports the --ruby-command argument, which helps the user with figuring out the correct Ruby command to use in case s/he wants to use multiple Ruby interpreters. The manual has also been updated to mention this tool.
  • Fixed streaming responses on Apache.
  • Worked around an OS X Unix domain socket bug. Fixes issue #854.
  • Out-of-Band Garbage Collection now works properly when the application has disabled garbage collection. Fixes issue #859.
  • Fixed support for /usr/bin/python on OS X. Fixes issue #855.
  • Fixed looping-without-sleeping in the ApplicationPool garbage collector if PassengerPoolIdleTime is set to 0. Fixes issue #858.
  • Fixed some process memory usage measurement bugs.
  • Fixed process memory usage measurement on NetBSD. Fixes issue #736.
  • Fixed a file descriptor leak in the Out-of-Band Work feature. Fixes issue #864.
  • The PassengerPreStart helper script now uses the default Ruby interpreter specified in the web server configuration, and no longer requires a ruby command to be in $PATH.
  • Updated preferred PCRE version to 8.32.
  • Worked around some RVM bugs and generally improved RVM support.
  • The ngx_http_stub_status_module is now enabled by default.
  • Performance optimizations.

New in Phusion Passenger 3.0.19 (Apr 9, 2013)

  • Nginx security fix: do not display Nginx version when server_tokens are off.
  • Fixed compilation problems on some systems.
  • Fixed some Union Station-related bugs.