2.16.2 - Fix WebSocket proxy URL construction and missing configuration parameter

What's Changed

Fix WebSocket proxy URL construction and missing configuration parameter by @Weixi779 in #160

Background

I noticed issue #147 regarding the incorrect WebSocket proxy URL construction. I also saw a similar solution proposed
in PR #149 by @GEverding, which correctly identified the root cause of the problem.

However, PR #149 received a change request from @0xTim asking for tests to verify the proxy URI generation. Since that
PR has not been updated, I have created this PR with the complete fix including the requested test modifications.

Changes

1. Fix proxy URL construction order - Fixes #147

• Changed URL format from ws://host/path:port to ws://host:port/path
• Updated test assertion in testProxy to expect the correct URL format
• Credit to @GEverding for identifying this issue in PR #149

2. Add missing configuration parameter

• Pass configuration parameter when connecting through proxy
• Ensures client configuration is properly forwarded to the underlying connection

3. Use correct URI form for wss + proxy connections

• For wss with proxy: use origin-form (/path) after CONNECT tunnel per RFC 7230
  …

Reviewers

Thanks to the reviewers for their help:

• @ptoffy

This patch was released by @0xTim

Full Changelog: 2.16.1...2.16.2

2.16.1 - Increase minimum required version of Swift-Nio to 2.78.0

What's Changed

Increase minimum required version of Swift-Nio to 2.78.0 by @robinkunde in #159

Recent changes make use of some methods that weren’t introduced to Swift-Nio until 2.78.0, so this package will not actually compile with anything older.

This patch was released by @gwynne

Full Changelog: 2.16.0...2.16.1

2.16.0 - Deal with Sendable and clean up package in general

What's Changed

Deal with Sendable and clean up package in general by @gwynne in #158

Covers fixing a bunch of Sendable things and does the usual round of package cleanup - bump the Swift minimum to 5.10, update the CI and the README, and so forth. Also fixes up some issues in the tests.

Reviewers

Thanks to the reviewers for their help:

• @MahdiBM

This patch was released by @gwynne

Full Changelog: 2.15.0...2.16.0

2.15.0 - Allow `send(_ binary:)` to accept `some DataProtocol`

What's Changed

Allow send(_ binary:) to accept some DataProtocol by @fizker in #146

This allows for passing in Data or ByteBufferView to send(_:), as well as the currently-supported [UInt8] type.

This patch was released by @0xTim

Full Changelog: 2.14.0...2.15.0

Pass a copy of the control frame buffer to ping/pong callbacks

This patch was authored by @tkrajacic and released by @0xTim.

This PR enables access to the data in the control frames handled via onPing/onPong via a new API with the existing onPing and onPong methods being deprecated.

Bump the swift-tools-version to 5.7

This patch was authored by @Joannis and released by @0xTim.

Set the minimum supported Swift version to 5.7. This is due to the usage of @preconcurrency

Revert Sendable Take 2

Reverts 2.12.0, in order to maintain compatibility with Swift 5.6 users.

Sendable Take 2

This patch was authored and released by @0xTim.

Adds Sendable annotations where possible. This time we're using @preconcurrency to suppress errors in unsafe code from downstream users

Revert "Add Sendable conformances to WebsocketKit (#131)"

This patch was authored and released by @gwynne.

Due to unforeseen source compatibility breakage, this backs out the changes from release 2.10.0 for now.

Add Sendable conformances to WebsocketKit

This patch was authored and released by @0xTim.

Bump minimum Swift version to 5.6 and add Sendable conformances where appropriate