Bump react/http from 0.8.4 to 1.4.0

[dependabot-preview]

Bumps react/http from 0.8.4 to 1.4.0.

Release notes

Sourced from react/http's releases.

v1.4.0

A major new feature release, see release announcement.

• Feature: Simplify usage by supporting new default loop. (#410 by @​clue)

  // old (still supported)
  $browser = new React\Http\Browser($loop);
  $server = new React\Http\Server($loop, $handler);
  // new (using default loop)
  $browser = new React\Http\Browser();
  $server = new React\Http\Server($handler);

v1.3.0

• Feature: Support persistent connections (Connection: keep-alive). (#405 by @​clue)

  This shows a noticeable performance improvement especially when benchmarking using persistent connections (which is the default pretty much everywhere). Together with other changes in this release, this improves benchmarking performance by around 100%.

• Feature: Require Host request header for HTTP/1.1 requests. (#404 by @​clue)

• Minor documentation improvements. (#398 by @​fritz-gerneth and #399 and #400 by @​pavog)

• Improve test suite, use GitHub actions for continuous integration (CI). (#402 by @​SimonFrings)

v1.2.0

• Feature: Keep request body in memory also after consuming request body. (#395 by @​clue)

  This means consumers can now always access the complete request body as detailed in the documentation. This allows building custom parsers and more advanced processing models without having to mess with the default parsers.

v1.1.0

• Feature: Support upcoming PHP 8 release, update to reactphp/socket v1.6 and adjust type checks for invalid chunk headers. (#391 by @​clue)

• Feature: Consistently resolve base URL according to HTTP specs. (#379 by @​clue)

• Feature / Fix: Expose Transfer-Encoding: chunked response header and fix chunked responses for HEAD requests.

... (truncated)

Changelog

Sourced from react/http's changelog.

1.4.0 (2021-07-11)

A major new feature release, see release announcement.

• Feature: Simplify usage by supporting new default loop. (#410 by @​clue)

  // old (still supported)
  $browser = new React\Http\Browser($loop);
  $server = new React\Http\Server($loop, $handler);
  // new (using default loop)
  $browser = new React\Http\Browser();
  $server = new React\Http\Server($handler);

1.3.0 (2021-04-11)

• Feature: Support persistent connections (Connection: keep-alive). (#405 by @​clue)

  This shows a noticeable performance improvement especially when benchmarking using persistent connections (which is the default pretty much everywhere). Together with other changes in this release, this improves benchmarking performance by around 100%.

• Feature: Require Host request header for HTTP/1.1 requests. (#404 by @​clue)

• Minor documentation improvements. (#398 by @​fritz-gerneth and #399 and #400 by @​pavog)

• Improve test suite, use GitHub actions for continuous integration (CI). (#402 by @​SimonFrings)

1.2.0 (2020-12-04)

• Feature: Keep request body in memory also after consuming request body. (#395 by @​clue)

  This means consumers can now always access the complete request body as detailed in the documentation. This allows building custom parsers and more advanced processing models without having to mess with the default parsers.

1.1.0 (2020-09-11)

• Feature: Support upcoming PHP 8 release, update to reactphp/socket v1.6 and adjust type checks for invalid chunk headers. (#391 by @​clue)

... (truncated)

Commits

• b008fb8 Prepare v1.4.0 release
• f37c964 Merge pull request #410 from clue-labs/default-loop
• d9401a5 Work around failing tests on legacy PHP 5.3
• 6b1a826 Update to stable reactphp/event-loop v1.2.0 & updated stream and socket
• 5417e83 Simplify usage by supporting new default loop
• bc53727 Prepare v1.3.0 release
• c22fde6 Merge pull request #404 from clue-labs/require-host
• c919cb7 Merge pull request #405 from clue-labs/keepalive
• 84fbe78 Improve benchmarking instructions and dangling memory references
• 7aa08f0 Support persistent connections (Connection: keep-alive)
• 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 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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)