jun-puma 1.0.0-java → 1.0.2-java

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e6683b8acec0bb81cd1bf2f4a232e6944fe3a89e214c8d4956a28862042249e5
-  data.tar.gz: 3a9dec8bfe42969355a323f4aa7a84624d6e3dd363d5367a25393e33892c09ed
+  metadata.gz: 93729a2531af093dfe3a707a797c6937fc035fb41f48c23b66486e01f2c66b1c
+  data.tar.gz: 1d07eebd87f8f70834e7a208bbcd1ea9255b501e1405e7fd903e4c9055da2bca
 SHA512:
-  metadata.gz: b4137d5ade45a5e7c86886ac9e3fd775e39311371530b702413d7fb6715f3db02fbb57e920e3be03196de7c29621a66fd448b8473a13ec548b2a6b25adf994d2
-  data.tar.gz: e7be8a01d20f2baa4c52eb11f014a1a4d0f8335d3534bd59f419b8230ba0e26dfa4dcdadd1be7e220880804514205cb16979be45b21fca3f7e5f51eea6033b06
+  metadata.gz: 5b8f718c1105ba6d8586ab8f54c34810471580f11f3b7f6124dff04dbca5903025127e43a9df79fa3c68a507b30000cc31468c0428201a87156c4e758b81a32b
+  data.tar.gz: 123566fa15a0af5bbad37502698d04822d9a25ce2a91229dd4e5e6890fb50206fbb511ed6953578fe73edc54809e31cb79d8f581168460cb18a8c681010f1164

data/History.md

@@ -1,42 +1,20 @@
-## 6.4.3 / 2024-09-19
-
-* Security
-  * Discards any headers using underscores if the non-underscore version also exists. Without this, an attacker could overwrite values set by intermediate proxies (e.g. X-Forwarded-For). ([CVE-2024-45614](https://github.com/puma/puma/security/advisories/GHSA-9hf4-67fc-4vf4)/GHSA-9hf4-67fc-4vf4)
-
-## 6.4.2 / 2024-01-08
-
-* Security
-  * Limit the size of chunk extensions. Without this limit, an attacker could cause unbounded resource (CPU, network bandwidth) consumption. ([GHSA-c2f4-cvqm-65w2](https://github.com/puma/puma/security/advisories/GHSA-c2f4-cvqm-65w2))
-
-## 6.4.1 / 2024-01-03
+## 6.4.1 / 2023-10-18
 
 * Bugfixes
   * DSL#warn_if_in_single_mode - fixup when workers set via CLI ([#3256])
-  * Fix `idle-timeout` not working in cluster mode ([#3235], [#3228], [#3282], [#3283])
+  * Fix `idle-timeout` not working in cluster mode ([#3235], [#3228])
   * Fix worker 0 timing out during phased restart ([#3225], [#2786])
   * context_builder.rb - require openssl if verify_mode != 'none' ([#3179])
-  * Make puma cluster process suitable as PID 1 ([#3255])
-  * Improve Puma::NullIO consistency with real IO ([#3276])
-  * extconf.rb - fixup to detect openssl info in Ruby build ([#3271], [#3266])
-  * MiniSSL.java - set serialVersionUID, fix RaiseException deprecation ([#3270])
-  * dsl.rb - fix warn_if_in_single_mode when WEB_CONCURRENCY is set ([#3265], [#3264])
+  * Fix bug in tests re: TestPuma::HOST4 ([#3254])
 
 * Maintenance
   * LOTS of test refactoring to make tests more stable and easier to write - thanks to @MSP-Greg!
-  * Fix bug in tests re: TestPuma::HOST4 ([#3254])
-  * Dockerfile for minimal repros: use Ruby 3.2, expect bundler installed ([#3245])
-  * fix define_method calls, use Symbol parameter instead of String ([#3293])
-
-* Docs
-  * README.md - add the puma-acme plugin ([#3301])
-  * Remove `--keep-file-descriptors` flag from systemd docs ([#3248])
-  * Note symlink mechanism in restart documentation for hot restart ([#3298])
 
 ## 6.4.0 / 2023-09-21
 
 * Features
   * on_thread_exit hook ([#2920])
-  * on_thread_start_hook ([#3195])
+  * on_thread_start_hook ([#3195]) 
   * Shutdown on idle ([#3209], [#2580])
   * New error message when control server port taken ([#3204])
 
@@ -46,13 +24,13 @@
 
 * Bugfixes
   * Bring the cert_pem: parameter into parity with the cert: parameter to ssl_bind. ([#3174])
-  * Fix using control server with IPv6 host ([#3181])
+  * Fix using control server with IPv6 host ([#3181]) 
   * control_cli.rb - add require_relative 'log_writer' ([#3187])
   * Fix cases where fallback Rack response wasn't sent to the client ([#3094])
-
+  
 ## 6.3.1 / 2023-08-18
 
-* Security
+* Security 
   * Address HTTP request smuggling vulnerabilities with zero-length Content Length header and trailer fields ([GHSA-68xg-gqqm-vgj8](https://github.com/puma/puma/security/advisories/GHSA-68xg-gqqm-vgj8))
 
 ## 6.3.0 / 2023-05-31
@@ -126,12 +104,12 @@
   * Refactor const.rb - freeze ([#3016])
 
 ## 6.0.1 / 2022-12-20
-
+ 
 * Bugfixes
   * Handle waking up a closed selector in Reactor#add ([#3005])
   * Fixup response processing, enumerable bodies ([#3004], [#3000])
   * Correctly close app body for all code paths ([#3002], [#2999])
-* Refactor
+* Refactor 
   * Add IOBuffer to Client, remove from ThreadPool thread instances ([#3013])
 
 ## 6.0.0 / 2022-10-14
@@ -160,12 +138,12 @@
   * Allow header values to be arrays (Rack 3) ([#2936], [#2931])
   * Export Puma/Ruby versions in /stats ([#2875])
   * Allow configuring request uri max length & request path max length ([#2840])
-  * Add a couple of public accessors ([#2774])
+  * Add a couple of public accessors ([#2774]) 
   * Log entire backtrace when worker start fails ([#2891])
   * [jruby] Enable TLSv1.3 support ([#2886])
   * [jruby] support setting TLS protocols + rename ssl_cipher_list ([#2899])
   * [jruby] Support a truststore option ([#2849], [#2904], [#2884])
-
+  
 * Bugfixes
   * Load the configuration before passing it to the binder ([#2897])
   * Do not raise error raised on HTTP methods we don't recognize or support, like CONNECT ([#2932], [#1441])
@@ -178,22 +156,9 @@
   * Ruby 3.2 will have native IO#wait_* methods, don't require io/wait ([#2903])
   * Various internal API refactorings ([#2942], [#2921], [#2922], [#2955])
 
-## 5.6.9 / 2024-09-19
-
-* Security
-  * Discards any headers using underscores if the non-underscore version also exists. Without this, an attacker could overwrite values set by intermediate proxies (e.g. X-Forwarded-For). ([CVE-2024-45614](https://github.com/puma/puma/security/advisories/GHSA-9hf4-67fc-4vf4)/GHSA-9hf4-67fc-4vf4)
-* JRuby
-  * Must use at least Java >= 9 to compile. You can no longer build from source on Java 8.
-
-
-## 5.6.8 / 2024-01-08
-
-* Security
-  * Limit the size of chunk extensions. Without this limit, an attacker could cause unbounded resource (CPU, network bandwidth) consumption. ([GHSA-c2f4-cvqm-65w2](https://github.com/puma/puma/security/advisories/GHSA-c2f4-cvqm-65w2))
-
 ## 5.6.7 / 2023-08-18
 
-* Security
+* Security 
   * Address HTTP request smuggling vulnerabilities with zero-length Content Length header and trailer fields ([GHSA-68xg-gqqm-vgj8](https://github.com/puma/puma/security/advisories/GHSA-68xg-gqqm-vgj8))
 
 ## 5.6.6 / 2023-06-21
@@ -2079,24 +2044,10 @@ be added back in a future date when a java Puma::MiniSSL is added.
 [#3256]:https://github.com/puma/puma/pull/3256     "PR by @MSP-Greg, merged 2023-10-16"
 [#3235]:https://github.com/puma/puma/pull/3235     "PR by @joshuay03, merged 2023-10-03"
 [#3228]:https://github.com/puma/puma/issues/3228   "Issue by @davidalejandroaguilar, closed 2023-10-03"
-[#3282]:https://github.com/puma/puma/issues/3282   "Issue by @bensheldon, closed 2024-01-02"
-[#3283]:https://github.com/puma/puma/pull/3283     "PR by @joshuay03, merged 2024-01-02"
 [#3225]:https://github.com/puma/puma/pull/3225     "PR by @joshuay03, merged 2023-09-27"
 [#2786]:https://github.com/puma/puma/issues/2786   "Issue by @vitiokss, closed 2023-09-27"
 [#3179]:https://github.com/puma/puma/pull/3179     "PR by @MSP-Greg, merged 2023-09-26"
-[#3255]:https://github.com/puma/puma/pull/3255     "PR by @casperisfine, merged 2023-10-19"
-[#3276]:https://github.com/puma/puma/pull/3276     "PR by @casperisfine, merged 2023-11-16"
-[#3271]:https://github.com/puma/puma/pull/3271     "PR by @MSP-Greg, merged 2023-10-30"
-[#3266]:https://github.com/puma/puma/issues/3266   "Issue by @Dragonicity, closed 2023-10-30"
-[#3270]:https://github.com/puma/puma/pull/3270     "PR by @MSP-Greg, merged 2023-10-30"
-[#3265]:https://github.com/puma/puma/pull/3265     "PR by @MSP-Greg, merged 2023-10-25"
-[#3264]:https://github.com/puma/puma/issues/3264   "Issue by @dentarg, closed 2023-10-25"
 [#3254]:https://github.com/puma/puma/pull/3254     "PR by @casperisfine, merged 2023-10-11"
-[#3245]:https://github.com/puma/puma/pull/3245     "PR by @olleolleolle, merged 2023-10-02"
-[#3293]:https://github.com/puma/puma/pull/3293     "PR by @MSP-Greg, merged 2023-12-21"
-[#3301]:https://github.com/puma/puma/pull/3301     "PR by @benburkert, merged 2023-12-29"
-[#3248]:https://github.com/puma/puma/pull/3248     "PR by @dentarg, merged 2023-10-04"
-[#3298]:https://github.com/puma/puma/pull/3298     "PR by @til, merged 2023-12-26"
 [#2920]:https://github.com/puma/puma/pull/2920     "PR by @biinari, merged 2023-07-11"
 [#3195]:https://github.com/puma/puma/pull/3195     "PR by @binarygit, merged 2023-08-15"
 [#3209]:https://github.com/puma/puma/pull/3209     "PR by @joshuay03, merged 2023-09-04"
@@ -2281,7 +2232,7 @@ be added back in a future date when a java Puma::MiniSSL is added.
 [#2563]:https://github.com/puma/puma/pull/2563     "PR by @MSP-Greg, merged 2021-03-06"
 [#2504]:https://github.com/puma/puma/issues/2504   "Issue by @fsateler, closed 2021-03-06"
 [#2591]:https://github.com/puma/puma/pull/2591     "PR by @MSP-Greg, merged 2021-05-05"
-[#2572]:https://github.com/puma/puma/issues/2572   "Issue by @josef-krabath, closed 2021-05-05"
+[#2572]:https://github.com/puma/puma/issues/2572   "Issue by @josefbilendo, closed 2021-05-05"
 [#2613]:https://github.com/puma/puma/pull/2613     "PR by @smcgivern, merged 2021-04-27"
 [#2605]:https://github.com/puma/puma/pull/2605     "PR by @pascalbetz, merged 2021-04-26"
 [#2584]:https://github.com/puma/puma/issues/2584   "Issue by @kaorihinata, closed 2021-04-26"
@@ -2597,7 +2548,7 @@ be added back in a future date when a java Puma::MiniSSL is added.
 [#1110]:https://github.com/puma/puma/pull/1110     "PR by @montdidier, merged 2016-12-12"
 [#1135]:https://github.com/puma/puma/pull/1135     "PR by @jkraemer, merged 2016-11-19"
 [#1081]:https://github.com/puma/puma/pull/1081     "PR by @frodsan, merged 2016-09-08"
-[#1138]:https://github.com/puma/puma/pull/1138     "PR by @skull-squadron, merged 2016-12-13"
+[#1138]:https://github.com/puma/puma/pull/1138     "PR by @steakknife, merged 2016-12-13"
 [#1118]:https://github.com/puma/puma/pull/1118     "PR by @hiroara, merged 2016-11-20"
 [#1075]:https://github.com/puma/puma/issues/1075   "Issue by @pvalena, closed 2016-09-06"
 [#932]:https://github.com/puma/puma/issues/932     "Issue by @everplays, closed 2016-07-24"

data/README.md

@@ -12,7 +12,7 @@ Puma is a **simple, fast, multi-threaded, and highly parallel HTTP 1.1 server fo
 
 ## Built For Speed & Parallelism
 
-Puma is a server for [Rack](https://github.com/rack/rack)-powered HTTP applications written in Ruby.  It is:
+Puma is a server for [Rack](https://github.com/rack/rack)-powered HTTP applications written in Ruby.  It is: 
 * **Multi-threaded**. Each request is served in a separate thread. This helps you serve more requests per second with less memory use.
 * **Multi-process**. "Pre-forks" in cluster mode, using less memory per-process thanks to copy-on-write memory.
 * **Standalone**. With SSL support, zero-downtime rolling restarts and a built-in request bufferer, you can deploy Puma without any reverse proxy.
@@ -138,93 +138,51 @@ 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.
 
-#### Clustered mode hooks
-
-When using clustered mode, Puma's configuration DSL provides `before_fork` and `on_worker_boot`
-hooks to run code when the master process forks and child workers are booted 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.
+When using clustered mode, you can specify a block in your configuration file that will be run on boot of each worker:
 
 ```ruby
 # config/puma.rb
-before_fork do
-  # Add code to run inside the Puma master process before it forks a worker child.
-end
-
 on_worker_boot do
-  # Add code to run inside the Puma worker process after forking.
+  # configuration here
 end
 ```
 
-In addition, there is an `on_refork` hook which is used only in [`fork_worker` mode](docs/fork_worker.md),
-when the worker 0 child process forks a grandchild worker:
+This code can be used to setup the process before booting the application, allowing
+you to do some Puma-specific things that you don't want to embed in your application.
+For instance, you could fire a log notification that a worker booted or send something to statsd. This can be called multiple times.
+
+Constants loaded by your application (such as `Rails`) will not be available in `on_worker_boot`
+unless preloading is enabled.
+
+You can also specify a block to be run before workers are forked, using `before_fork`:
 
 ```ruby
-on_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.
+# config/puma.rb
+before_fork do
+  # configuration here
 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 `on_refork` to disconnect the parent's socket
-   connections when forking, so that they are not accidentally copied to the child process.
-3. Use `on_worker_boot` to restart any background threads on the forked child.
-
-#### Master process lifecycle hooks
-
-Puma's configuration DSL provides master process lifecycle hooks `on_booted`, `on_restart`, and `on_stopped`
-which may be used to specify code blocks to run on each event:
+You can also specify a block to be run after puma is booted using `on_booted`:
 
 ```ruby
 # config/puma.rb
 on_booted do
-  # Add code to run in the Puma master process after it boots,
-  # and also after a phased restart completes.
-end
-
-on_restart do
-  # Add code to run in the Puma master process when it receives
-  # a restart command but before it restarts.
-end
-
-on_stopped do
-  # Add code to run in the Puma master process when it receives
-  # a stop command but before it shuts down.
+  # configuration here
 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
+If puma encounters an error outside of the context of your application, it will respond with a 500 and a simple
 textual error message (see `Puma::Server#lowlevel_error` or [server.rb](https://github.com/puma/puma/blob/master/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]]
+lowlevel_error_handler do |e|
+  Rollbar.critical(e)
+  [500, {}, ["An error has occurred, and engineers have been informed. Please reload the page. If you continue to have problems, contact support@example.com\n"]]
 end
 ```
 
@@ -291,7 +249,7 @@ $ puma -b ssl://localhost:9292 -b tcp://localhost:9393 -C config/use_local_host.
 
 #### 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.
+To use or avoid specific SSL cipher suites, use `ssl_cipher_filter` or `ssl_cipher_list` options.
 
 ##### Ruby:
 
@@ -305,14 +263,6 @@ $ puma -b 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert&ssl_cipher_fil
 $ 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:
@@ -329,7 +279,7 @@ To enable verification flags offered by OpenSSL, use `verification_flags` (not a
 $ 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):
+You can also set multiple verification flags (by separating them with coma):
 
 ```
 $ puma -b 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert&verification_flags=PARTIAL_CHAIN,CRL_CHECK'
@@ -460,7 +410,6 @@ Community guides:
 * [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
 

data/ext/puma_http11/extconf.rb

@@ -10,13 +10,14 @@ end
 
 unless ENV["PUMA_DISABLE_SSL"]
   # don't use pkg_config('openssl') if '--with-openssl-dir' is used
-  has_openssl_dir = dir_config('openssl').any? ||
-    RbConfig::CONFIG['configure_args']&.include?('openssl')
-
-  found_pkg_config = !has_openssl_dir && pkg_config('openssl')
+  has_openssl_dir = dir_config('openssl').any?
+  # macOS TruffleRuby problem
+  found_pkg_config = RUBY_ENGINE == 'truffleruby' &&
+      RUBY_PLATFORM.include?('darwin') && ENV['GITHUB_ACTIONS'] == 'true' ?
+    false : !has_openssl_dir && pkg_config('openssl')
 
   found_ssl = if !$mingw && found_pkg_config
-    puts '──── Using OpenSSL pkgconfig (openssl.pc) ────'
+    puts 'using OpenSSL pkgconfig (openssl.pc)'
     true
   elsif have_library('libcrypto', 'BIO_read') && have_library('libssl', 'SSL_CTX_new')
     true
@@ -31,27 +32,22 @@ unless ENV["PUMA_DISABLE_SSL"]
   if found_ssl
     have_header "openssl/bio.h"
 
-    ssl_h = "openssl/ssl.h".freeze
-
-    puts "\n──── Below are yes for 1.0.2 & later ────"
-    have_func "DTLS_method"                            , ssl_h
-    have_func "SSL_CTX_set_session_cache_mode(NULL, 0)", ssl_h
-
-    puts "\n──── Below are yes for 1.1.0 & later ────"
-    have_func "TLS_server_method"                      , ssl_h
-    have_func "SSL_CTX_set_min_proto_version(NULL, 0)" , ssl_h
+    # below is  yes for 1.0.2 & later
+    have_func "DTLS_method"                            , "openssl/ssl.h"
+    have_func "SSL_CTX_set_session_cache_mode(NULL, 0)", "openssl/ssl.h"
 
-    puts "\n──── Below is yes for 1.1.0 and later, but isn't documented until 3.0.0 ────"
-    # https://github.com/openssl/openssl/blob/OpenSSL_1_1_0/include/openssl/ssl.h#L1159
-    have_func "SSL_CTX_set_dh_auto(NULL, 0)"           , ssl_h
+    # below are yes for 1.1.0 & later
+    have_func "TLS_server_method"                      , "openssl/ssl.h"
+    have_func "SSL_CTX_set_min_proto_version(NULL, 0)" , "openssl/ssl.h"
 
-    puts "\n──── Below is yes for 1.1.1 & later ────"
-    have_func "SSL_CTX_set_ciphersuites(NULL, \"\")"   , ssl_h
+    have_func "X509_STORE_up_ref"
+    have_func "SSL_CTX_set_ecdh_auto(NULL, 0)"         , "openssl/ssl.h"
 
-    puts "\n──── Below is yes for 3.0.0 & later ────"
-    have_func "SSL_get1_peer_certificate"              , ssl_h
+    # below exists in 1.1.0 and later, but isn't documented until 3.0.0
+    have_func "SSL_CTX_set_dh_auto(NULL, 0)"           , "openssl/ssl.h"
 
-    puts ''
+    # below is yes for 3.0.0 & later
+    have_func "SSL_get1_peer_certificate"              , "openssl/ssl.h"
 
     # Random.bytes available in Ruby 2.5 and later, Random::DEFAULT deprecated in 3.0
     if Random.respond_to?(:bytes)

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: jun-puma
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.0.2
 platform: java
 authors:
 - Evan Phoenix
@@ -17,18 +17,17 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '2.0'
   name: nio4r
-  prerelease: false
   type: :runtime
+  prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '2.0'
-description: |
-  Puma is a simple, fast, multi-threaded, and highly parallel HTTP 1.1 server
-  for Ruby/Rack applications. Puma is intended for use in both development and
-  production environments. It's great for highly parallel Ruby implementations such as
-  JRuby and TruffleRuby as well as as providing process worker support to support CRuby well.
+description: Puma is a simple, fast, threaded, and highly parallel HTTP 1.1 server
+  for Ruby/Rack applications. Puma is intended for use in both development and production
+  environments. It's great for highly parallel Ruby implementations such as Rubinius
+  and JRuby as well as as providing process worker support to support CRuby well.
 email:
 - evan@phx.io
 executables:
@@ -41,87 +40,9 @@ files:
 - LICENSE
 - README.md
 - bin/puma
-- bin/puma-wild
 - bin/pumactl
-- docs/architecture.md
-- docs/compile_options.md
-- docs/deployment.md
-- docs/fork_worker.md
-- docs/images/puma-connection-flow-no-reactor.png
-- docs/images/puma-connection-flow.png
-- docs/images/puma-general-arch.png
-- docs/jungle/README.md
-- docs/jungle/rc.d/README.md
-- docs/jungle/rc.d/puma
-- docs/jungle/rc.d/puma.conf
-- docs/kubernetes.md
-- docs/nginx.md
-- docs/plugins.md
-- docs/rails_dev_mode.md
-- docs/restart.md
-- docs/signals.md
-- docs/stats.md
-- docs/systemd.md
-- docs/testing_benchmarks_local_files.md
-- docs/testing_test_rackup_ci_files.md
-- ext/puma_http11/PumaHttp11Service.java
-- ext/puma_http11/ext_help.h
 - ext/puma_http11/extconf.rb
-- ext/puma_http11/http11_parser.c
-- ext/puma_http11/http11_parser.h
-- ext/puma_http11/http11_parser.java.rl
-- ext/puma_http11/http11_parser.rl
-- ext/puma_http11/http11_parser_common.rl
-- ext/puma_http11/mini_ssl.c
-- ext/puma_http11/no_ssl/PumaHttp11Service.java
-- ext/puma_http11/org/jruby/puma/Http11.java
-- ext/puma_http11/org/jruby/puma/Http11Parser.java
-- ext/puma_http11/org/jruby/puma/MiniSSL.java
-- ext/puma_http11/puma_http11.c
-- lib/puma.rb
-- lib/puma/app/status.rb
-- lib/puma/binder.rb
-- lib/puma/cli.rb
-- lib/puma/client.rb
-- lib/puma/cluster.rb
-- lib/puma/cluster/worker.rb
-- lib/puma/cluster/worker_handle.rb
-- lib/puma/commonlogger.rb
-- lib/puma/configuration.rb
-- lib/puma/const.rb
-- lib/puma/control_cli.rb
-- lib/puma/detect.rb
-- lib/puma/dsl.rb
-- lib/puma/error_logger.rb
-- lib/puma/events.rb
-- lib/puma/io_buffer.rb
-- lib/puma/jruby_restart.rb
-- lib/puma/json_serialization.rb
-- lib/puma/launcher.rb
-- lib/puma/launcher/bundle_pruner.rb
-- lib/puma/log_writer.rb
-- lib/puma/minissl.rb
-- lib/puma/minissl/context_builder.rb
-- lib/puma/null_io.rb
-- lib/puma/plugin.rb
-- lib/puma/plugin/systemd.rb
-- lib/puma/plugin/tmp_restart.rb
 - lib/puma/puma_http11.jar
-- lib/puma/rack/builder.rb
-- lib/puma/rack/urlmap.rb
-- lib/puma/rack_default.rb
-- lib/puma/reactor.rb
-- lib/puma/request.rb
-- lib/puma/runner.rb
-- lib/puma/sd_notify.rb
-- lib/puma/server.rb
-- lib/puma/single.rb
-- lib/puma/state_file.rb
-- lib/puma/thread_pool.rb
-- lib/puma/util.rb
-- lib/rack/handler/puma.rb
-- tools/Dockerfile
-- tools/trickletest.rb
 homepage: https://puma.io
 licenses:
 - BSD-3-Clause
@@ -149,5 +70,6 @@ requirements: []
 rubygems_version: 3.3.26
 signing_key:
 specification_version: 4
-summary: A Ruby/Rack web server built for parallelism.
+summary: Puma is a simple, fast, threaded, and highly parallel HTTP 1.1 server for
+  Ruby/Rack applications
 test_files: []

data/bin/puma-wild

@@ -1,25 +0,0 @@
-#!/usr/bin/env ruby
-#
-# Copyright (c) 2014 Evan Phoenix
-#
-
-require 'rubygems'
-
-cli_arg = ARGV.shift
-
-inc = ""
-
-if cli_arg == "-I"
-  inc = ARGV.shift
-  $LOAD_PATH.concat inc.split(":")
-end
-
-module Puma; end
-
-Puma.const_set(:WILD_ARGS, ["-I", inc])
-
-require 'puma/cli'
-
-cli = Puma::CLI.new ARGV
-
-cli.run

data/docs/architecture.md

@@ -1,74 +0,0 @@
-# Architecture
-
-## Overview
-
-![https://bit.ly/2iJuFky](images/puma-general-arch.png)
-
-Puma is a threaded Ruby HTTP application server processing requests across a TCP
-and/or UNIX socket.
-
-
-Puma processes (there can be one or many) accept connections from the socket via
-a thread (in the [`Reactor`](../lib/puma/reactor.rb) class). The connection,
-once fully buffered and read, moves into the `todo` list, where an available
-thread will pick it up (in the [`ThreadPool`](../lib/puma/thread_pool.rb)
-class).
-
-Puma works in two main modes: cluster and single. In single mode, only one Puma
-process boots. In cluster mode, a `master` process is booted, which prepares
-(and may boot) the application and then uses the `fork()` system call to create
-one or more `child` processes. These `child` processes all listen to the same
-socket. The `master` process does not listen to the socket or process requests -
-its purpose is primarily to manage and listen for UNIX signals and possibly kill
-or boot `child` processes.
-
-We sometimes call `child` processes (or Puma processes in `single` mode)
-_workers_, and we sometimes call the threads created by Puma's
-[`ThreadPool`](../lib/puma/thread_pool.rb) _worker threads_.
-
-## How Requests Work
-
-![https://bit.ly/2zwzhEK](images/puma-connection-flow.png)
-
-* Upon startup, Puma listens on a TCP or UNIX socket.
-  * The backlog of this socket is configured with a default of 1024, but the
-    actual backlog value is capped by the `net.core.somaxconn` sysctl value.
-    The backlog determines the size of the queue for unaccepted connections. If
-    the backlog is full, the operating system is not accepting new connections.
-  * This socket backlog is distinct from the `backlog` of work as reported by
-    `Puma.stats` or the control server. The backlog that `Puma.stats` refers to
-    represents the number of connections in the process' `todo` set waiting for
-    a thread from the [`ThreadPool`](../lib/puma/thread_pool.rb).
-* By default, a single, separate thread (created by the
-  [`Reactor`](../lib/puma/reactor.rb) class) reads and buffers requests from the
-  socket.
-  * When at least one worker thread is available for work, the reactor thread
-    listens to the socket and accepts a request (if one is waiting).
-  * The reactor thread waits for the entire HTTP request to be received.
-    * Puma exposes the time spent waiting for the HTTP request body to be
-      received to the Rack app as `env['puma.request_body_wait']`
-      (milliseconds).
-  * Once fully buffered and received, the connection is pushed into the "todo"
-    set.
-* Worker threads pop work off the "todo" set for processing.
-  * The worker thread processes the request via `call`ing the configured Rack
-    application. The Rack application generates the HTTP response.
-  * The worker thread writes the response to the connection. While Puma buffers
-    requests via a separate thread, it does not use a separate thread for
-    responses.
-  * Once done, the thread becomes available to process another connection in the
-    "todo" set.
-
-### `queue_requests`
-
-![https://bit.ly/2zxCJ1Z](images/puma-connection-flow-no-reactor.png)
-
-The `queue_requests` option is `true` by default, enabling the separate reactor
-thread used to buffer requests as described above.
-
-If set to `false`, this buffer will not be used for connections while waiting
-for the request to arrive.
-
-In this mode, when a connection is accepted, it is added to the "todo" queue
-immediately, and a worker will synchronously do any waiting necessary to read
-the HTTP request from the socket.