Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/dotnet/yarp/releases below:

Releases · dotnet/yarp · GitHub

Releases · dotnet/yarp

This release supports .NET 8.0 and newer. See Getting Started.
Note that while this version also includes targets for .NET 6 and .NET 7, those runtimes are no longer supported.

The Yarp.ReverseProxy packages are available on NuGet.org.

• More errors triggered by the client disconnecting are now logged under a Debug severity (#2765 by @MihaZupan).
  • ForwarderError.ResponseBodyCanceled and UpgradeResponseCanceled are no longer logged with a Warning severity.
  • This is a continuation of a change we've made in 2.2 where we've done the same with RequestCanceled, RequestBodyCanceled, and UpgradeRequestCanceled.
• Replacing the HttpRequestMessage.Content property in a request transform will throw an exception (#2722 by @MihaZupan).
  • While setting the property may have appeared to work during limited testing, it could lead to various issues as YARP internally relies on the property remaining unchanged. See the pull request for more context on this change.
• We now always enforce the HttpVersionPolicy during HTTP version negotiation (#2729 by @MihaZupan).
  • It was previously possible for YARP to initiate HTTP/1.1 connections for WebSocket and SPDY requests even if the specified HttpVersionPolicy disallowed it. This was breaking scenarios such as outgoing HTTP/2 WebSockets without TLS.
  • If the policy disallows the use of outbound HTTP/1.1, SPDY requests will not be proxied and will instead return a RequestCreation error.
  • This does not affect the default YARP configuration, which is Version=2.0, Policy=RequestVersionOrLower.

• YARP has always logically been a part of .NET and we have now moved the repository from the microsoft to the dotnet organization.
  • The license has been updated to the .NET foundation, but remains MIT as before (#2738 by @adityamandaleeka).
  • As part of the repository move, we have moved the documentation to learn.microsoft.com.
• We've created a JSON schema for YARP configuration! Editing now comes with validation and autocompletions (#2758 by @MihaZupan).
• We've started shipping a minimal YARP container image at mcr.microsoft.com (#2710 by @benjaminpetit).
  • More functionality will be added to the image over time.

• We've added optional parameters to AddForwarded and AddXForwarded request transforms that allow you to opt-out of removing the other variant of the header (#2728 by @rkargMsft).

  ctx.AddForwarded(removeAllXForwardedHeaders: false);
  ctx.AddXForwarded(removeForwardedHeader: false);

• Improved HttpSysDelegator logging and retry logic (#2671 by @NGloreous).
• YARP can now be published with NativeAOT when targetting .NET 8.0 again (#2759 by @MihaZupan).
• We've added a workaround for an error in .NET builds from the Ubuntu package feed (#2673 by @MihaZupan).
  • See dotnet/aspnetcore#59166 for more information.

• @xtqqczze made their first contribution in #2748

For a full list of changes see here.

This release supports .NET 6.0 and .NET 8.0. See Getting Started.

The Yarp.ReverseProxy packages are available on NuGet.org.

• There are no breaking changes between YARP 2.2.0-preview.1 and 2.2.0.
• See 2.2.0-preview.1 release notes for the list of breaking changes between YARP 2.1 and 2.2.

• The Forwarded transform now prefers the IPv4 form for dual-mode sockets (#2509 by @rkargMsft).
  • E.g. 127.0.0.1 is used instead of ::ffff:127.0.0.1.
  • A similar change was already made for X-Forwarded-For in 2.2.0-preview.1 (#2400).
• Added a missing WebSocketCloseReason.ActivityTimeout enum value (#2571 by @MihaZupan).
• Added a TlsFrameHelper.ParsingStatus API (#2587 by @wfurt).
  • This information can be used to distinguish between Invalid and Incomplete frames.
• Removed one async state machine allocation when forwarding a request (#2586 by @MihaZupan).
• Several documentation improvements.

• @rkargMsft made their first contribution in #2509
• @nigma143 made their first contribution in #2535
• @mroberts91 made their first contribution in #2530
• @t0mll made their first contribution in #2547
• @fnuttens made their first contribution in #2558

For a full list of changes see here.

This release supports .NET 6.0 and .NET 8.0. See Getting Started.

The Yarp.ReverseProxy packages are available on NuGet.org.

• HeaderMatchMode.NotExists now also matches headers with an empty value (#2412 by @qianyuansun).
  • This makes NotExists exactly the opposite of Exists. Previously, empty values would not match either mode.
• Errors triggered by the client disconnecting are now logged under a Debug severity (#2503 by @MihaZupan).
  • ForwarderError.RequestCanceled, RequestBodyCanceled, and UpgradeRequestCanceled are now logged under a new ILogger event with a Debug severity. Other errors continue to be logged under the existing event with a Warning severity.
  • How errors are mapped to different ForwarderErrors remains the same.

• Added support for Kestrel Start/Stop events on IKestrelTelemetryConsumer (#2360 by @ajay-sainy).
• Added support for controlling OutputCachePolicy in the route configuration (#2328 by @witskeeper).
  • See the Output Caching documentation for more details.
• X-Forwarded-For now prefers the IPv4 form for dual-mode sockets (#2400 by @hacst).
  • E.g. 127.0.0.1 is used instead of ::ffff:127.0.0.1.
• Fixed a bug where active health checks would consider new destinations as Healthy instead of Unknown (#2415 by @robbieknuth).
  • Destinations now remain as Unknown until enough health probes have been sent.
• Added a new Query property to active health check configuration (#2421 by @robbieknuth).
  • Previously, only Path could have been specified, and ? would be escaped to %3F.
• Added support to HttpSysDelegator for detaching from and re-initializing queues (#2426 by @NGloreous).
• Fixed a race condition reliability bug in HttpSysDelegator (#2487 by @NGloreous).
• OperationCanceledExceptions thrown by response transforms as part of error handling are now ignored (#2452 by @MihaZupan).
• Fixed a bug where YARP validation of UseRequestTimeouts was too strict (#2501 by @MihaZupan).
• Reduced the performance overhead of updating the activity timeout timer (#2475 by @MihaZupan).
• Many documentation improvements.

• @larsbj1988 made their first contribution in #2293
• @Bambi-pa-hal-is made their first contribution in #2350
• @ajay-sainy made their first contribution in #2360
• @joegoldman2 made their first contribution in #2381
• @hacst made their first contribution in #2400
• @allantargino made their first contribution in #2411
• @robbieknuth made their first contribution in #2415
• @qianyuansun made their first contribution in #2412
• @jsedlak-microsoft made their first contribution in #2436
• @jamesmontemagno made their first contribution in #2433
• @eltociear made their first contribution in #2456

For a full list of changes see here.

This release supports .NET 6.0 and .NET 7.0. See Getting Started.

The Yarp.ReverseProxy packages are available on NuGet.org.

• Existing HttpTransformer overloads that don't accept a CancellationToken have been marked as obsolete (#2016).
  • If you have created a custom class that derives from HttpTransformer, you should update the implementation to override the overloads which accept the CancellationToken instead.
  • Existing implementations that only override the obsolete overloads will continue working for the time being, but these overloads may be removed in a future major release.
• See 2.0.0-RC.1 release notes for the rest of the breaking changes between YARP 1.1 and 2.0.

• Added a new enum value ForwarderError.RequestCreation that is reported if a request transform throws an exception (#2016).
• Fixed a bug introduced in RC1 where custom response transform callbacks were not called on errors (when ProxyResponse is null) (#2016).
• Fixed a bug where a request cancellation triggered by the manual CancellationToken (parameter to IHttpForwarder.SendAsync) was reported as RequestTimedOut instead of RequestCanceled (#2016).

For a full list of changes see here.

This release supports .NET 6.0 and .NET 7.0. See Getting Started.

The Yarp.ReverseProxy packages are available on NuGet.org.

• We dropped support for .NET Core 3.1 and .NET 5.0 as they are no longer supported.
  • YARP 2.0 targets .NET 6 and .NET 7.
• The default session affinity policy has been changed from Cookie to HashCookie (#1989).
  • This policy provides fewer security guarantees about the protection level of the key data - the destination ids. On the other hand, it allows for multiple YARP instances to share session affinity cookies without the need to configure ASP.NET Core Data Protection.
  • For more details, see the Session Affinity documentation.
• YARP now sets the SocketsHttpHandler.ConnectTimeout by default (#1991). You may observe different exceptions being reported by the proxy in failure scenarios when destination servers aren't responding. See #1678 for more context on this change.
• The name of the enum value TlsHandshakeType.KeyEpdate has been corrected to KeyUpdate (#1614).

• Added support for WebSockets over HTTP/2 (#1978).
  • Protocol upgrades and downgrades are automatic. You can mix different protocol versions on both incoming and outgoing sides.
  • This feature is available on .NET 7.0 and newer only. To accept HTTP/2 WebSockets, you must use Kestrel.
  • See the YARP WebSockets documentation for more details.
• Request transforms can now short-circuit requests and avoid proxying (#1923).
  • If you set the status code on the response to something other than 200 OK, or if you start writing to the response body, forwarding will be skipped.
  • See the Request Transforms documentation for more details.

• You can specify the RateLimiterPolicy on a route from the configuration (#1967). See the Rate Limiting documentation for more details.
• You can specify the MaxRequestBodySize on a route from the configuration (#1947).
• We exposed the InMemoryConfigProvider as a built-in API (#1732). You no longer have to copy the implementation from the samples :)
• Added an IConfigChangeListener interface you can implement to receive notifications when and if configuration has been applied (#1734).
• Added an IHttpForwarder.SendAsync overload that accepts a cancellation token (#1985).
• Added async APIs to ISessionAffinityPolicy (#1990).
• Added an overload of ReassignProxyRequest that also accepts a route (#1760).
• Added a HeaderMatchMode.NotExists mode to header routing (#1806).
• Added an AddMetricsConsumer helper method to make it easier to register a consumer with multiple IMetricsConsumers (#1899).
• We report a warning early if you define multiple routes with the same ID (#1831).
• We throw if you use a custom IForwarderHttpClientFactory and also call ConfigureHttpClient as the two are mutually exclusive (#1805).
• We no longer restore the Upgrade response header unless there is a matching entry in the Connection header (#1731).
• We remove the Content-Length: 0 header on responses that don't allow bodies (#1813).
• We no longer proxy the Strict-Transport-Security header (#1984).

For a full list of changes see here.

This release supports .NET Core 3.1, .NET 5.0, and .NET 6.0. See Getting Started.

The Yarp.ReverseProxy packages are available on NuGet.org.

Changes:

• A fix for issue #1770 which was causing WebSockets to close abortively rather than gracefully.

You can’t perform that action at this time.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4