puma 8.1.0-java → 8.1.1-java

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3e02c432552f5eaaac8c58b225f9f0dd3c22989934edd82cd1fb1bd29b5ba363
-  data.tar.gz: 64bc20c3349c3de9518aa40131410effa3d4bf7f7c6e5e761be5a1e9b13e0af9
+  metadata.gz: 0fba79f28dc2923378fa1d5d91982a60fa0f5fa040d372252413c6298b3ff14e
+  data.tar.gz: 536c3b67d879dd8df682ebb2d119649dbda647311a8e536d7c7acf1b68ab14db
 SHA512:
-  metadata.gz: 1ac59882efd8822b4f068fd0705cd30ca35cfff1a3d1a653c6c208793f60642ec5d0206ca002cb21253ebffc0fca01cda74dbc42be0c996d27ec131ab41fdb27
-  data.tar.gz: e52b5670782329d492c1a3c8a2811ef183f7c4f46bb66fb8e2b109cf190a23202efd246e9a4eafdc8a886aeca4587d6c02cfbc6c95bae1edfc3e00ec94bb0521
+  metadata.gz: ab93e52be84c22692b15f07eb777ed28b76b59d8d2bb7a356469748bedeb24830d62ca3d1722a1d5cdd73126f416dc7584ab08a69b83f5625026f2f0ce9bcc94
+  data.tar.gz: 9fe0219f02e03173abcc075296b40058468bbace111c37533f864d1ffda37a97ae8366e8765786e9ac20b6850a789c71eb4cbb7cd7a98b9306218f97a7fb7752

data/History.md

@@ -1,3 +1,10 @@
+## 8.1.1 / 2026-11-15
+
+* Bugfixes
+  * Fix `pumactl stop` and SIGINT hanging in cluster mode when an `after_stopped` hook owns child processes ([#4135])
+  * Fix TLS stream corruption on TruffleRuby when flushing to a full socket ([#4108])
+  * Stop shipping development-only files in the gem ([#4124])
+
 ## 8.1.0 / 2026-11-15
 
 * Features
@@ -2431,6 +2438,9 @@ be added back in a future date when a java Puma::MiniSSL is added.
 * Bugfixes
   * Your bugfix goes here <Most recent on the top, like GitHub> (#Github Number)
 
+[#4135]:https://github.com/puma/puma/pull/4135     "PR by Nate Berkopec, merged 2026-11-15"
+[#4108]:https://github.com/puma/puma/pull/4108     "PR by Nate Berkopec, merged 2026-11-15"
+[#4124]:https://github.com/puma/puma/pull/4124     "PR by Nate Berkopec, merged 2026-11-15"
 [#4059]:https://github.com/puma/puma/pull/4059     "PR by William T. Nelson, merged 2026-11-09"
 [#3976]:https://github.com/puma/puma/pull/3976     "PR by Maksim Romanov, merged 2026-10-02"
 [#4021]:https://github.com/puma/puma/pull/4021     "PR by Ted Ford, merged 2026-09-27"

data/README.md

@@ -95,355 +95,21 @@ You can also find several configuration examples as part of the
 For debugging purposes, you can set the environment variable `PUMA_LOG_CONFIG` with a value
 and the loaded configuration will be printed as part of the boot process.
 
-### Thread Pool
-
-Puma uses a thread pool. You can set the minimum and maximum number of threads that are available in the pool with the `-t` (or `--threads`) flag:
-
-```
-$ puma -t 8:32
-```
-
-Puma will automatically scale the number of threads, from the minimum until it caps out at the maximum, based on how much traffic is present. The current default is `0:16` and on MRI is `0:5`. Feel free to experiment, but be careful not to set the number of maximum threads to a large number, as you may exhaust resources on the system (or cause contention for the Global VM Lock, when using MRI).
-
-Be aware that additionally Puma creates threads on its own for internal purposes (e.g. handling slow clients). So, even if you specify -t 1:1, expect around 7 threads created in your application.
-
-### Cluster mode
-
-Puma also offers "cluster mode". Cluster mode `fork`s workers from a master process. Each child process still has its own thread pool. You can tune the number of workers with the `-w` (or `--workers`) flag:
-
-```
-$ puma -t 8:32 -w 3
-```
-
-Or with the `WEB_CONCURRENCY` environment variable:
-
-```
-$ WEB_CONCURRENCY=3 puma -t 8:32
-```
-
-When using a config file, most applications can simply set `workers :auto` (requires the `concurrent-ruby` gem) to match the number of worker processes to the available processors:
-
-```ruby
-# config/puma.rb
-workers :auto
-```
-
-See [`workers :auto` gotchas](lib/puma/dsl.rb).
-
-Note that threads are still used in cluster mode, and the `-t` thread flag setting is per worker, so `-w 2 -t 16:16` will spawn 32 threads in total, with 16 in each worker process.
-
-If `workers` is set to `:auto`, or the `WEB_CONCURRENCY` environment variable is set to `"auto"`, and the `concurrent-ruby` gem is available in your application, Puma will set the worker process count to the result of [available processors](https://msp-greg.github.io/concurrent-ruby/Concurrent.html#available_processor_count-class_method).
-
-For an in-depth discussion of the tradeoffs of thread and process count settings, [see our docs](docs/deployment.md).
-
-In cluster mode, Puma can "preload" your application. This loads all the application code *prior* to forking. Preloading reduces total memory usage of your application via an operating system feature called [copy-on-write](https://en.wikipedia.org/wiki/Copy-on-write).
-
-If the number of workers is greater than 1 (and `--prune-bundler` has not been specified), preloading will be enabled by default. Otherwise, you can use the `--preload` flag from the command line:
-
-```
-$ puma -w 3 --preload
-```
-
-Or, if you're using a configuration file, you can use the `preload_app!` method:
-
-```ruby
-# config/puma.rb
-workers 3
-preload_app!
-```
-
-Preloading can’t be used with phased restart, since phased restart kills and restarts workers one-by-one, and preloading copies the code of master into the workers.
-
-#### Cluster mode hooks
-
-When using clustered mode, Puma's configuration DSL provides `before_fork`, `before_worker_boot`, and `after_worker_shutdown`
-hooks to run code when the master process forks, the child workers are booted, and after each child worker exits respectively.
-
-It is recommended to use these hooks with `preload_app!`, otherwise constants loaded by your
-application (such as `Rails`) will not be available inside the hooks.
-
-```ruby
-# config/puma.rb
-before_fork do
-  # Add code to run inside the Puma master process before it forks a worker child.
-end
-
-before_worker_boot do
-  # Add code to run inside the Puma worker process after forking.
-end
-
-after_worker_shutdown do |worker_handle|
-  # Add code to run inside the Puma master process after a worker exits. `worker.process_status` can be used to get the
-  # `Process::Status` of the exited worker.
-end
-```
-
-In addition, there are `before_refork` and `after_refork` hooks which are used only in [`fork_worker` mode](docs/fork_worker.md),
-when the worker 0 child process forks a grandchild worker:
-
-```ruby
-before_refork do
-  # Used only when fork_worker mode is enabled. Add code to run inside the Puma worker 0
-  # child process before it forks a grandchild worker.
-end
-```
-
-```ruby
-after_refork do
-  # Used only when fork_worker mode is enabled. Add code to run inside the Puma worker 0
-  # child process after it forks a grandchild worker.
-end
-```
-
-Importantly, note the following considerations when Ruby forks a child process:
-
-1. File descriptors such as network sockets **are** copied from the parent to the forked
-   child process. Dual-use of the same sockets by parent and child will result in I/O conflicts
-   such as `SocketError`, `Errno::EPIPE`, and `EOFError`.
-2. Background Ruby threads, including threads used by various third-party gems for connection
-   monitoring, etc., are **not** copied to the child process. Often this does not cause
-   immediate problems until a third-party connection goes down, at which point there will
-   be no supervisor to reconnect it.
-
-Therefore, we recommend the following:
-
-1. If possible, do not establish any socket connections (HTTP, database connections, etc.)
-   inside Puma's master process when booting.
-2. If (1) is not possible, use `before_fork` and `before_refork` to disconnect the parent's socket
-   connections when forking, so that they are not accidentally copied to the child process.
-3. Use `before_worker_boot` to restart any background threads on the forked child.
-4. Use `after_refork` to restart any background threads on the parent.
-
-#### Master process lifecycle hooks
-
-Puma's configuration DSL provides master process lifecycle hooks `after_booted`, `before_restart`, and `after_stopped`
-which may be used to specify code blocks to run on each event:
-
-```ruby
-# config/puma.rb
-after_booted do
-  # Add code to run in the Puma master process after it boots,
-  # and also after a phased restart completes.
-end
-
-before_restart do
-  # Add code to run in the Puma master process when it receives
-  # a restart command but before it restarts.
-end
-
-after_stopped do
-  # Add code to run in the Puma master process after outstanding
-  # requests have finished and Puma has stopped.
-end
-```
-
-### Error handling
-
-If Puma encounters an error outside of the context of your application, it will respond with a 400/500 and a simple
-textual error message (see `Puma::Server#lowlevel_error` or [server.rb](https://github.com/puma/puma/blob/main/lib/puma/server.rb)).
-You can specify custom behavior for this scenario. For example, you can report the error to your third-party
-error-tracking service (in this example, [rollbar](https://rollbar.com)):
-
-```ruby
-lowlevel_error_handler do |e, env, status|
-  if status == 400
-    message = "The server could not process the request due to an error, such as an incorrectly typed URL, malformed syntax, or a URL that contains illegal characters.\n"
-  else
-    message = "An error has occurred, and engineers have been informed. Please reload the page. If you continue to have problems, contact support@example.com\n"
-    Rollbar.critical(e)
-  end
-
-  [status, {}, [message]]
-end
-```
-
-### Binding TCP / Sockets
-
-Bind Puma to a socket with the `-b` (or `--bind`) flag:
-
-```
-$ puma -b tcp://127.0.0.1:9292
-```
-
-When using a TCP socket on Linux, Puma will automatically skip requests whose connection has closed by the time it's taken from the queue. If you'd like to avoid wasting time on connections that are closing after your app starts handling them, you can call `env["puma.connection_closed?"]` at any time during the lifecycle of a request. A `false` result does not guarantee that the connection will remain open. Puma cannot check this for you during a request: it is waiting for your app to return a response.
-
-To use a UNIX Socket instead of TCP:
-
-```
-$ puma -b unix:///var/run/puma.sock
-```
-
-If you need to change the permissions of the UNIX socket, just add a umask parameter:
-
-```
-$ puma -b 'unix:///var/run/puma.sock?umask=0111'
-```
-
-Need a bit of security? Use SSL sockets:
-
-```
-$ puma -b 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert'
-```
-#### Self-signed SSL certificates (via the [`localhost`] gem, for development use):
-
-Puma supports the [`localhost`] gem for self-signed certificates. This is particularly useful if you want to use Puma with SSL locally, and self-signed certificates will work for your use-case. Currently, the integration can only be used in MRI.
-
-Puma automatically configures SSL when the [`localhost`] gem is loaded in a `development` environment:
-
-Add the gem to your Gemfile:
-```ruby
-group(:development) do
-  gem 'localhost'
-end
-```
-
-And require it implicitly using bundler:
-```ruby
-require "bundler"
-Bundler.require(:default, ENV["RACK_ENV"].to_sym)
-```
-
-Alternatively, you can require the gem in your configuration file, either `config/puma/development.rb`, `config/puma.rb`, or set via the `-C` cli option:
-```ruby
-require 'localhost'
-# configuration methods (from Puma::DSL) as needed
-```
-
-Additionally, Puma must be listening to an SSL socket:
-
-```shell
-$ puma -b 'ssl://localhost:9292' -C config/use_local_host.rb
-
-# The following options allow you to reach Puma over HTTP as well:
-$ puma -b ssl://localhost:9292 -b tcp://localhost:9393 -C config/use_local_host.rb
-```
-
-[`localhost`]: https://github.com/socketry/localhost
-
-#### Controlling SSL Cipher Suites
-
-To use or avoid specific SSL ciphers for TLSv1.2 and below, use `ssl_cipher_filter` or `ssl_cipher_list` options.
-
-##### Ruby:
-
-```
-$ puma -b 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert&ssl_cipher_filter=!aNULL:AES+SHA'
-```
-
-##### JRuby:
-
-```
-$ puma -b 'ssl://127.0.0.1:9292?keystore=path_to_keystore&keystore-pass=keystore_password&ssl_cipher_list=TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA'
-```
-
-To configure the available TLSv1.3 ciphersuites, use `ssl_ciphersuites` option (not available for JRuby).
-
-##### Ruby:
-
-```
-$ puma -b 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert&ssl_ciphersuites=TLS_AES_256_GCM_SHA384:TLS_AES_128_GCM_SHA256'
-```
-
-See https://www.openssl.org/docs/man1.1.1/man1/ciphers.html for cipher filter format and full list of cipher suites.
-
-Disable TLS v1 with the `no_tlsv1` option:
-
-```
-$ puma -b 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert&no_tlsv1=true'
-```
-
-#### Controlling OpenSSL Verification Flags
-
-To enable verification flags offered by OpenSSL, use `verification_flags` (not available for JRuby):
-
-```
-$ puma -b 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert&verification_flags=PARTIAL_CHAIN'
-```
-
-You can also set multiple verification flags (by separating them with a comma):
-
-```
-$ puma -b 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert&verification_flags=PARTIAL_CHAIN,CRL_CHECK'
-```
-
-List of available flags: `USE_CHECK_TIME`, `CRL_CHECK`, `CRL_CHECK_ALL`, `IGNORE_CRITICAL`, `X509_STRICT`, `ALLOW_PROXY_CERTS`, `POLICY_CHECK`, `EXPLICIT_POLICY`, `INHIBIT_ANY`, `INHIBIT_MAP`, `NOTIFY_POLICY`, `EXTENDED_CRL_SUPPORT`, `USE_DELTAS`, `CHECK_SS_SIGNATURE`, `TRUSTED_FIRST`, `SUITEB_128_LOS_ONLY`, `SUITEB_192_LOS`, `SUITEB_128_LOS`, `PARTIAL_CHAIN`, `NO_ALT_CHAINS`, `NO_CHECK_TIME`
-(see https://www.openssl.org/docs/manmaster/man3/X509_VERIFY_PARAM_set_hostflags.html#VERIFICATION-FLAGS).
-
-#### Controlling OpenSSL Password Decryption
-
-To enable runtime decryption of an encrypted SSL key (not available for JRuby), use `key_password_command`:
-
-```
-$ puma -b 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert&key_password_command=/path/to/command.sh'
-```
-
-`key_password_command` must:
-
-1. Be executable by Puma.
-2. Print the decryption password to stdout.
-
- For example:
-
-```shell
-#!/bin/sh
-
-echo "this is my password"
-```
-
-`key_password_command` can be used with `key` or `key_pem`. If the key
-is not encrypted, the executable will not be called.
-
-### Control/Status Server
-
-Puma has a built-in status and control app that can be used to query and control Puma.
-
-```
-$ puma --control-url tcp://127.0.0.1:9293 --control-token foo
-```
-
-Puma will start the control server on localhost port 9293. All requests to the control server will need to include a control token (in this case, `token=foo`) as a query parameter. This allows for simple authentication. Check out `Puma::App::Status` or [status.rb](https://github.com/puma/puma/blob/main/lib/puma/app/status.rb) to see what the status app has available.
-
-You can also interact with the control server via `pumactl`. This command will restart Puma:
-
-```
-$ pumactl --control-url 'tcp://127.0.0.1:9293' --control-token foo restart
-```
-
-To see a list of `pumactl` options, use `pumactl --help`.
-
-### Configuration File
-
-You can also provide a configuration file with the `-C` (or `--config`) flag:
-
-```
-$ puma -C /path/to/config
-```
-
-If no configuration file is specified, Puma will look for a configuration file at `config/puma.rb`. If an environment is specified (via the `--environment` flag or through the `APP_ENV`, `RACK_ENV`, or `RAILS_ENV` environment variables) Puma looks for a configuration file at `config/puma/<environment_name>.rb` and then falls back to `config/puma.rb`.
-
-If you want to prevent Puma from looking for a configuration file in those locations, include the `--no-config` flag:
-
-```
-$ puma --no-config
-
-# or
-
-$ puma -C "-"
-```
-
-The other side-effects of setting the environment are whether to show stack traces (in `development` or `test`), and setting RACK_ENV may potentially affect middleware looking for this value to change their behavior. The default puma RACK_ENV value is `development`. You can see all config default values in `Puma::Configuration#puma_default_options` or [configuration.rb](https://github.com/puma/puma/blob/61c6213fbab/lib/puma/configuration.rb#L182-L204).
-
-Check out `Puma::DSL` or [dsl.rb](https://github.com/puma/puma/blob/main/lib/puma/dsl.rb) to see all available options.
-
-## Restart
-
-Puma includes the ability to restart itself. When available (MRI, Rubinius, JRuby), Puma performs a "hot restart". This is the same functionality available in *Unicorn* and *NGINX* which keep the server sockets open between restarts. This makes sure that no pending requests are dropped while the restart is taking place.
-
-For more, see the [Restart documentation](docs/restart.md).
-
-## Signals
-
-Puma responds to several signals. A detailed guide to using UNIX signals with Puma can be found in the [Signals documentation](docs/signals.md).
+## Documentation
+
+* [Configuration](docs/configuration.md)
+* [Cluster mode](docs/cluster_mode.md)
+* [Binding TCP / Sockets and SSL](docs/binding.md)
+* [Control/Status Server and stats](docs/control_server.md)
+* [Restart](docs/restart.md)
+* [Signals](docs/signals.md)
+* [Plugins](docs/plugins.md)
+* [Deployment](docs/deployment/README.md)
+* [Running Puma in Rails development mode](docs/rails_dev_mode.md)
+* [Compile options](docs/compile_options.md) and [Java options](docs/java_options.md)
+* [Architecture](docs/architecture.md)
+* [Support policy](docs/puma_support.md)
+* [Upgrade guides](docs/upgrading)
 
 ## Platform Constraints
 
@@ -451,38 +117,7 @@ Some platforms do not support all Puma features.
 
   * **JRuby**, **Windows**: server sockets are not seamless on restart, they must be closed and reopened. These platforms have no way to pass descriptors into a new process that is exposed to Ruby. Also, cluster mode is not supported due to a lack of fork(2).
   * **Windows**: Cluster mode is not supported due to a lack of fork(2).
-  * **Kubernetes**: The way Kubernetes handles pod shutdowns interacts poorly with server processes implementing graceful shutdown, like Puma. See the [kubernetes section of the documentation](docs/kubernetes.md) for more details.
-
-## Deployment
-
- * Puma has support for Capistrano with an [external gem](https://github.com/seuros/capistrano-puma).
-
- * Additionally, Puma has support for built-in daemonization via the [puma-daemon](https://github.com/kigster/puma-daemon) ruby gem. The gem restores the `daemonize` option that was removed from Puma starting version 5, but only for MRI Ruby.
-
-
-It is common to use process monitors with Puma. Modern process monitors like systemd or rc.d
-provide continuous monitoring and restarts for increased reliability in production environments:
-
-* [rc.d](docs/jungle/rc.d/README.md)
-* [systemd](docs/systemd.md)
-
-Community guides:
-
-* [Deploying Puma on OpenBSD using relayd and httpd](https://gist.github.com/anon987654321/4532cf8d6c59c1f43ec8973faa031103)
-
-## Community Extensions
-
-### Plugins
-
-* [puma-metrics](https://github.com/harmjanblok/puma-metrics) — export Puma metrics to Prometheus
-* [puma-plugin-statsd](https://github.com/yob/puma-plugin-statsd) — send Puma metrics to statsd
-* [puma-plugin-systemd](https://github.com/sj26/puma-plugin-systemd) — deeper integration with systemd for notify, status and watchdog. Puma 5.1.0 integrated notify and watchdog, which probably conflicts with this plugin. Puma 6.1.0 added status support which obsoletes the plugin entirely.
-* [puma-plugin-telemetry](https://github.com/babbel/puma-plugin-telemetry) - telemetry plugin for Puma offering various targets to publish
-* [puma-acme](https://github.com/anchordotdev/puma-acme) - automatic SSL/HTTPS certificate provisioning and setup
-
-### Monitoring
-
-* [puma-status](https://github.com/ylecuyer/puma-status) — Monitor CPU/Mem/Load of running puma instances from the CLI
+  * **Kubernetes**: The way Kubernetes handles pod shutdowns interacts poorly with server processes implementing graceful shutdown, like Puma. See the [kubernetes section of the documentation](docs/deployment/kubernetes.md) for more details.
 
 ## Merchandise
 

data/docs/binding.md

@@ -0,0 +1,135 @@
+# Binding TCP / Sockets
+
+Bind Puma to a socket with the `-b` (or `--bind`) flag:
+
+```
+$ puma -b tcp://127.0.0.1:9292
+```
+
+When using a TCP socket on Linux, Puma will automatically skip requests whose connection has closed by the time it's taken from the queue. If you'd like to avoid wasting time on connections that are closing after your app starts handling them, you can call `env["puma.connection_closed?"]` at any time during the lifecycle of a request. A `false` result does not guarantee that the connection will remain open. Puma cannot check this for you during a request: it is waiting for your app to return a response.
+
+To use a UNIX Socket instead of TCP:
+
+```
+$ puma -b unix:///var/run/puma.sock
+```
+
+If you need to change the permissions of the UNIX socket, just add a umask parameter:
+
+```
+$ puma -b 'unix:///var/run/puma.sock?umask=0111'
+```
+
+Need a bit of security? Use SSL sockets:
+
+```
+$ puma -b 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert'
+```
+## Self-signed SSL certificates (via the [`localhost`] gem, for development use):
+
+Puma supports the [`localhost`] gem for self-signed certificates. This is particularly useful if you want to use Puma with SSL locally, and self-signed certificates will work for your use-case. Currently, the integration can only be used in MRI.
+
+Puma automatically configures SSL when the [`localhost`] gem is loaded in a `development` environment:
+
+Add the gem to your Gemfile:
+```ruby
+group(:development) do
+  gem 'localhost'
+end
+```
+
+And require it implicitly using bundler:
+```ruby
+require "bundler"
+Bundler.require(:default, ENV["RACK_ENV"].to_sym)
+```
+
+Alternatively, you can require the gem in your configuration file, either `config/puma/development.rb`, `config/puma.rb`, or set via the `-C` cli option:
+```ruby
+require 'localhost'
+# configuration methods (from Puma::DSL) as needed
+```
+
+Additionally, Puma must be listening to an SSL socket:
+
+```shell
+$ puma -b 'ssl://localhost:9292' -C config/use_local_host.rb
+
+# The following options allow you to reach Puma over HTTP as well:
+$ puma -b ssl://localhost:9292 -b tcp://localhost:9393 -C config/use_local_host.rb
+```
+
+[`localhost`]: https://github.com/socketry/localhost
+
+## Controlling SSL Cipher Suites
+
+To use or avoid specific SSL ciphers for TLSv1.2 and below, use `ssl_cipher_filter` or `ssl_cipher_list` options.
+
+### Ruby:
+
+```
+$ puma -b 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert&ssl_cipher_filter=!aNULL:AES+SHA'
+```
+
+### JRuby:
+
+```
+$ puma -b 'ssl://127.0.0.1:9292?keystore=path_to_keystore&keystore-pass=keystore_password&ssl_cipher_list=TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA'
+```
+
+To configure the available TLSv1.3 ciphersuites, use `ssl_ciphersuites` option (not available for JRuby).
+
+### Ruby:
+
+```
+$ puma -b 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert&ssl_ciphersuites=TLS_AES_256_GCM_SHA384:TLS_AES_128_GCM_SHA256'
+```
+
+See https://www.openssl.org/docs/man1.1.1/man1/ciphers.html for cipher filter format and full list of cipher suites.
+
+Disable TLS v1 with the `no_tlsv1` option:
+
+```
+$ puma -b 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert&no_tlsv1=true'
+```
+
+## Controlling OpenSSL Verification Flags
+
+To enable verification flags offered by OpenSSL, use `verification_flags` (not available for JRuby):
+
+```
+$ puma -b 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert&verification_flags=PARTIAL_CHAIN'
+```
+
+You can also set multiple verification flags (by separating them with a comma):
+
+```
+$ puma -b 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert&verification_flags=PARTIAL_CHAIN,CRL_CHECK'
+```
+
+List of available flags: `USE_CHECK_TIME`, `CRL_CHECK`, `CRL_CHECK_ALL`, `IGNORE_CRITICAL`, `X509_STRICT`, `ALLOW_PROXY_CERTS`, `POLICY_CHECK`, `EXPLICIT_POLICY`, `INHIBIT_ANY`, `INHIBIT_MAP`, `NOTIFY_POLICY`, `EXTENDED_CRL_SUPPORT`, `USE_DELTAS`, `CHECK_SS_SIGNATURE`, `TRUSTED_FIRST`, `SUITEB_128_LOS_ONLY`, `SUITEB_192_LOS`, `SUITEB_128_LOS`, `PARTIAL_CHAIN`, `NO_ALT_CHAINS`, `NO_CHECK_TIME`
+(see https://www.openssl.org/docs/manmaster/man3/X509_VERIFY_PARAM_set_hostflags.html#VERIFICATION-FLAGS).
+
+## Controlling OpenSSL Password Decryption
+
+To enable runtime decryption of an encrypted SSL key (not available for JRuby), use `key_password_command`:
+
+```
+$ puma -b 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert&key_password_command=/path/to/command.sh'
+```
+
+`key_password_command` must:
+
+1. Be executable by Puma.
+2. Print the decryption password to stdout.
+
+ For example:
+
+```shell
+#!/bin/sh
+
+echo "this is my password"
+```
+
+`key_password_command` can be used with `key` or `key_pem`. If the key
+is not encrypted, the executable will not be called.