One bug fix:

• #220 Incorrect forwarding of multiple cookies

This is intended to be the final release as https://github.com/microsoft/reverse-proxy is expected to be a release alongside .NET5.0 PR and they have introduced AspNet Core 3.1 support too.

• Fix for azure "bad gateway" #227

• Support netcoreapp3.1 and aspnet core3.1 #199

• [Bug] #179 Bad Gateway when trying to proxy to Azure (thanks to @kolomik for PR #189)

https://www.nuget.org/packages/ProxyKit/2.2.2

• Request bodies in GET, HEAD, DELETE are not ignored and just passed through if they exist. #168

• Supports AspNetCore 3.0 #165
• Continues to support AspNetCore 2.1 LTS.

https://www.nuget.org/packages/ProxyKit/2.2.0

• Read only streams should not be flushed #143

Removed usage of typed http client in favour of a named one #124 , #137

Available on nuget.org: https://www.nuget.org/packages/ProxyKit/2.1.2

Summary

This release contains 2 primary new features, support for WebSockets and Typed Handlers as well as fixes and documentation improvements.

WebSockets

WebSocket requests can now be forwarded to an upstream host. They are handled independently of HTTP requests do the different mechanism for customizing the initial upstream requests.

• Quickstart
• Recipe
• SignalR Recipe
• SIgnalR Runnable Example

Typed Handlers

As an alternative to the delegate approach, typed handlers allow you to inject services into you proxy handling code.

• PR #119
• Documentation

Fixes And others

• #75 Fix OptionsPattern For ProxyOptions
• A few fully runnable recipes added, Simple, TenantForwarding and SignalRSimpleChat

Contributors

Thanks to @datvm, @ChrisTorng, @samcov, @ben-foster-cko, for your reports, PRs and discussions 😄

• [Bug, Workaround] ASPNET Core can accept a requests that has a malformed User-Agent #55 . Thanks to @doggy8088 .