Bump puma from 3.11.2 to 6.3.1 in /docs-book

[dependabot[bot]]

Bumps puma from 3.11.2 to 6.3.1.

Release notes

Sourced from puma's releases.

6.3.1

• Security
  • Address HTTP request smuggling vulnerabilities with zero-length Content Length header and trailer fields (GHSA-68xg-gqqm-vgj8)

6.3.0 - Mugi No Toki Itaru

Japan has 72 traditional microseasons. May 31 is the first day of 麦秋至, which means the time of the wheat/barley harvest.

• Features

  • Add dsl method supported_http_methods (#3106, #3014)
  • Puma error responses no longer have any fingerprints to indicate Puma (#3161, #3037)
  • Support decryption of SSL key (#3133, #3132)

• Bugfixes

  • Don't send 103 early hints response when only invalid headers are used (#3163)
  • Handle malformed request path (#3155, #3148)
  • Misc lib file fixes - trapping additional errors, CI helper (#3129)
  • Fixup req form data file upload with "r\n" line endings (#3137)
  • Restore rack 1.6 compatibility (#3156)

• Refactor

  • const.rb - Update Puma::HTTP_STATUS_CODES (#3162)
  • Clarify Reactor#initialize (#3151)

New Contributors

• @​severin made their first contribution in puma/puma#3156

Full Changelog: https://github.com/puma/puma/compare/v6.2.2...v6.3.0

6.2.2

• Bugfixes
  • Fix Rack-related NameError by adding :: operator (#3118, #3117)

6.2.1 / 2023-03-31

• Bugfixes
  • Fix java 8 compatibility (#3109, #3108)
  • Always write io_buffer when in "enum bodies" branch. (#3113, #3112)
  • Fix warn_if_in_single_mode incorrect message (#3111)

6.2 - Speaking of Now

Pat Metheny Group - Speaking of Now

• Features
  • Ability to supply a custom logger (#2770, #2511)
  • Warn when clustered-only hooks are defined in single mode (#3089)
  • Adds the on_booted event (#2709)

... (truncated)

Changelog

Sourced from puma's changelog.

6.3.1 / 2023-08-18

• Security
  • Address HTTP request smuggling vulnerabilities with zero-length Content Length header and trailer fields (GHSA-68xg-gqqm-vgj8)

6.3.0 / 2023-05-31

• Features

  • Add dsl method supported_http_methods (#3106, #3014)
  • Puma error responses no longer have any fingerprints to indicate Puma (#3161, #3037)
  • Support decryption of SSL key (#3133, #3132)

• Bugfixes

  • Don't send 103 early hints response when only invalid headers are used (#3163)
  • Handle malformed request path (#3155, #3148)
  • Misc lib file fixes - trapping additional errors, CI helper (#3129)
  • Fixup req form data file upload with "r\n" line endings (#3137)
  • Restore rack 1.6 compatibility (#3156)

• Refactor

  • const.rb - Update Puma::HTTP_STATUS_CODES (#3162)
  • Clarify Reactor#initialize (#3151)

6.2.2 / 2023-04-17

• Bugfixes
  • Fix Rack-related NameError by adding :: operator (#3118, #3117)

6.2.1 / 2023-03-31

• Bugfixes
  • Fix java 8 compatibility (#3109, #3108)
  • Always write io_buffer when in "enum bodies" branch. (#3113, #3112)
  • Fix warn_if_in_single_mode incorrect message (#3111)

6.2.0 / 2023-03-29

• Features

  • Ability to supply a custom logger (#2770, #2511)
  • Warn when clustered-only hooks are defined in single mode (#3089)
  • Adds the on_booted event (#2709)

• Bugfixes

  • Loggers - internal_write - catch Errno::EINVAL (#3091)
  • commonlogger.rb - fix HIJACK time format, use constants, not strings (#3074)
  • Fixed some edge cases regarding request hijacking (#3072)

6.1.1 / 2023-02-28

• Bugfixes

... (truncated)

Commits

• 72bdcd1 6.3.1
• ed0f2f9 Merge pull request from GHSA-68xg-gqqm-vgj8
• 763d1a1 6.3.0 (#3169)
• dfd33df Add dsl method supported_http_methods (#3106)
• a434005 Puma error responses - remove fingerprints to indicate Puma (#3161)
• 7b7774c Don't send 103 early hints response when only invalid headers are used (#3163)
• 2bb9143 const.rb - Update Puma::HTTP_STATUS_CODES (#3162)
• d244dc7 [CI] - Use RubyGems 3.3.26 for Ruby 2.4 thru 2.6 (was 3.3.14) (#3160)
• c467e57 [CI] test_redirect_io.rb - fixup for intermittent failures (#3157)
• b61bbc7 [CI] Use <<~ for heredocs (#3159)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/pivotal-cf/docs-splunk/network/alerts).

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.