23.3.3

Technical release, version 23.3.3

Features in Release 23.3.3

_{8c0180a by Raman Maksimchuk on Tuesday, June 11 at 16:00 →}
Pre-Release 23.3.3 artifacts | +semver: patch

23.3.0

Spring 2024 (version 23.3.0) aka Twilight Texas release

Codenamed: Twilight Texas
Read the Docs: Ocelot 23.3

What's new?

• Service Discovery: Introducing a new feature for "Customization of services creation" in two primary service discovery providers: Consul and Kubernetes, developed by @raman-m.
  The customization for both Consul and Kube providers in service creation is achieved through the overriding of virtual methods in default implementations. The recommendation was to separate the provider's logic and introduce public virtual and protected virtual methods in concrete classes, enabling:

  • The use of public virtual methods as dictated by interface definitions.
  • The application of protected virtual methods to allow developers to customize atomic operations through inheritance from existing concrete classes.
  • The injection of new interface objects into the provider's constructor.
  • The overriding of the default behavior of classes.

  Ultimately, customization relies on the virtual methods within the default implementation classes, providing developers the flexibility to override them as necessary for highly tailored Consul/K8s configurations in their specific environments.
  For further details, refer to the respective pull requests for both providers:

  • Kube → PR #2052
  • Consul → PR #2067

• Routing: Introducing the new "Routing based on Request Header" feature by @jlukawska.
  In addition to routing via UpstreamPathTemplate, you can now define an UpstreamHeaderTemplates options dictionary. For a route to match, all headers specified in this section are required to be present in the request headers.
  For more details, see PR #1312.

• Configuration: Introducing the "Custom Default Version Policy" feature by @ibnuda.
  The configurable HttpRequestMessage.VersionPolicy helps avoid HTTP protocol connection errors and stabilizes connections to downstream services, especially when you're not developing those services, documentation is scarce, or the deployed HTTP protocol version is uncertain.
  For developers of downstream services, it's possible to ConfigureKestrel server and its endpoints with new protocol settings. However, attention to version policy is also required, and this feature provides precise version settings for HTTP connections.
  Essentially, this feature promotes the use of HTTP protocols beyond 1.0/1.1, such as HTTP/2 or even HTTP/3.
  For additional details, refer to PR #1673.

• Configuration: Introducing the new "Route Metadata" feature by @vantm. Undoubtedly, this is the standout feature of the release! ⭐
  Route metadata enables Ocelot developers to incorporate custom functions that address specific needs or to create their own plugins/extensions.
  In versions of Ocelot prior to 23.3.0, the configuration was limited to predefined values that Ocelot used internally. This was sufficient for official extensions, but posed challenges for third-party developers who needed to implement configurations not included in the standard FileConfiguration. Applying an option to a specific route required knowledge of the array index and other details that might not be readily accessible using the standard IConfiguration or IOptions<FileConfiguration> models from ASP.NET. Now, metadata can be directly accessed in the DownstreamRoute object. Furthermore, metadata can also be retrieved from the global JSON section via the FileConfiguration.GlobalConfiguration property.
  For more information, see the details in PR #1843 on this remarkable feature.

Focus On

Updates of the features: Configuration, Service Discovery, Routing and Quality of Service

• Configuration: New features are "Custom Default Version Policy" by @ibnuda and "Route Metadata" by @vantm.

• Service Discovery: New feature is "Customization of services creation" by @raman-m.

• Routing: New feature is "Routing based on Request Header" by @jlukawska.

• Quality of Service: The team has decided to remove the Polly V7 policies logic and the corresponding Ocelot AddPollyV7 extensions (referenced in PR #2079). Furthermore, the Polly V8 Circuit Breaker has been mandated as the primary strategy (as per PR #2086).
  See more detailed below in "Ocelot extra packages" paragraph.

Ocelot extra packages

• Ocelot.Provider.Polly

  • Our team has resolved to eliminate the Polly V7 policies logic and the corresponding Ocelot AddPollyV7 extensions entirely (refer to the "Polly v7 vs v8" documentation). In the previous 23.2 release, named Lunar Eclipse, we included these to maintain the legacy Polly behavior, allowing development teams to transition or retain the old Polly V7 functionality. We are now confident that it is time to progress alongside Polly, shifting our focus to the new Polly V8 resilience pipelines. For more details, see PR #2079.

  • Additionally, we have implemented Polly v8 Circuit Breaker as the primary strategy. Our Quality of Service () relies on two main strategies: Circuit Breaker and Timeout. If both Circuit Breaker and Timeout are configured with their respective properties in the QoSOptions of the route JSON, then the Circuit Breaker strategy will take precedence in the constructed resilience pipeline. For more details, refer to PR #2086.

Stabilization aka bug fixing

• Fixed #2034 in PR #2045 by @raman-m
• Fixed #2039 in PR #2050 by @PaulARoy
• Fixed #1590 in PR #1592 by @sergio-str
• Fixed #2054 #2059 in PR #2058 by @thiagoloureiro
• Fixed #954 #957 #1026 in PR #2067 by @raman-m
• Fixed #2002 in PR #2003 by @bbenameur
• Fixed #2085 in PR #2086 by @RaynaldM
• See all bugs of the Spring'24 milestone

Documentation for version 23.3.0

• Caching: New EnableContentHashing option and Global Configuration sections
• Configuration: New DownstreamHttpVersionPolicy and Route Metadata sections
• Metadata: This is new chapter for Route Metadata feature.
• [Quality of Service](htt...

23.2.2

Hotfix release (version 23.2.2) for #2031 issue

Route path template placeholders and their validation rules

Special thanks to Guillaume Gnaegi and Fabrizio Mancin!

About

The bug is related to the Placeholders feature in Configuration and Routing.
The bug was introduced in version 23.2.0 as a part of PR #1927.

Breaking Change

The new validation rules of the FileConfigurationFluentValidator class do not allow the Ocelot app to start when implicit placeholders are defined in custom implementations, such as middlewares, delegating handlers, and replaced services in the dependency injection (DI) container.
These new rules are capable of validating explicit placeholders only within the UpstreamPathTemplate and DownstreamPathTemplate properties. Unfortunately, they cannot oversee implicit placeholders in custom implementations, and they do not validate early during the Ocelot app startup process.

Ensure that you avoid using version 23.2.0. If you are currently on that version, upgrade to version 23.2.2 by applying this hotfix patch.

Technical info

With version 23.2.0, particularly if you have overridden certain service classes or implemented custom logic that manipulates placeholders, you may encounter Ocelot app crashes accompanied by the following errors in the log:

One or more errors occurred. (Unable to start Ocelot, errors are: XXX)

where XXX are the following validation error messages:

• UpstreamPathTemplate 'UUU' doesn't contain the same placeholders in DownstreamPathTemplate 'DDD'
• DownstreamPathTemplate 'DDD' doesn't contain the same placeholders in UpstreamPathTemplate 'UUU'

Finally, the validation rules resulted from the incorrect assumption that placeholders are always explicit and can be validated early. Therefore, custom implementations and feature services in the dependency injection (DI) container, which rely on or manipulate placeholders, should validate the configuration JSON and appropriate options later, directly within their service implementations.

Bug Artifacts

• Released in version: 23.2.0
• Introduced in: PR #1927
• Reported bug: #2031 by @ggnaegi and tested by @Fabman08
• Hotfix PR: #2032 by @raman-m

Features in Release 23.2.2

_{2ded872 by Raman Maksimchuk on Friday, April 05 at 15:13 →}
Release 23.2.1-2 artifacts | +semver: patch
_{14c6d82 by Raman Maksimchuk on Friday, April 05 at 12:57 →}
#2031 Don't validate placeholders in templates (#2032)
_{d1855cb by Raman Maksimchuk on Thursday, April 04 at 00:17 →}
#1673 #1672 Update Docker for CircleCI builds (#2030)

23.2.1

Documentation patch (version 23.2.1) for 23.2.0 release

Read the Docs: Ocelot 23.2

This is a technical release: no other information.

What's Changed

• Release 23.2.1 by @raman-m in #2029

Full Changelog: 23.2.0...23.2.1

23.2.0

February 2024 (version 23.2.0) aka Lunar Eclipse release

Codenamed: Lunar Eclipse
Read the Docs: Ocelot 23.2

What's new?

• Configuration: A brand new Merging files to memory feature by @ebjornset as a part of the Merging Configuration Files one.
  The AddOcelot method merges the ocelot.*.json files into a single ocelot.json file as the primary configuration file, which is written back to disk and then added to the IConfigurationBuilder for the well-known IConfiguration. You can now call another AddOcelot method that adds the merged JSON directly from memory to the IConfigurationBuilder, using AddJsonStream instead.
  See more details in Configuration Overview of Dependency Injection.
• Service Fabric: Published old undocumented "Placeholders in Service Name" feature of Service Fabric service discovery provider.
  This feature by @FelixBoers is available starting from version 13.0.0.
• Quality of Service: A brand new Polly v8 pipelines Extensibility feature by @RaynaldM

Focus On

Updates of the features: Configuration, Dependency Injection and QoS

• Configuration: New Merging files to memory feature by @ebjornset
• Dependency Injection: Added new overloaded AddOcelot methods by @ebjornset
• Quality of Service: Support of new Polly v8 syntax and new Extensibility feature by @RaynaldM

Ocelot extra packages

• Ocelot.Provider.Polly: Support of new Polly v8 syntax.
  Polly 8.0+ versions introduced the concept of resilience pipelines.
  All AddPolly extensions have been automatically migrated from v7 to v8.
  Please note that older v7 extensions are marked with the [Obsolete] attribute and renamed using the V7 suffix. And the old v7 implementation has been moved to the v7 namespace.
  See more details in Polly v7 vs v8 section of Quality of Service chapter.

Stabilization aka bug fixing

• 683 by PR 1927
  New rules have been added to Ocelot's configuration validation logic to find duplicate placeholders in path templates.
  See more in the FileConfigurationFluentValidator class. Thanks to @AlyHKafoury!
• 1518 hotfix by PR 1986
  Using the default IServiceCollection DI extensions to register Ocelot services resulted in the ServiceCollection provider being forced to be created by calling BuildServiceProvider().
  This resulted in problems with dependency injection libraries, or worse, causing the Ocelot app to crash!
  See more in the ServiceCollectionExtensions class. Thanks to @ArwynFr!
• See all bugs of the February'24 milestone

Documentation for version 23.2

• Configuration
• Dependency Injection
• Quality of Service
• Service Fabric

Honoring 🏅 aka Top Contributors 👏

1^st 🥇 goes to Eirik Bjornset for delivering 1 feature in 19 files changed
2^nd 🥈 goes to Aly Kafoury for delivering 1 feature in 9 files changed
3^rd 🥉 goes to Adrien Hupond for delivering 1 feature in 6 files changed

Starring ⭐ aka Release Influencers

⭐ Adrien Hupond, @ArwynFr
⭐ Aly Kafoury, @AlyHKafoury
⭐ Eirik Bjornset, @ebjornset
⭐ Raman Maksimchuk, @raman-m
⭐ Raynald Messié, @RaynaldM

Features in Release 23.2.0

Milestone: February'24

Logbook

• _{334432f by Raman Maksimchuk on Friday, March 29 at 20:18 →}
  Release 23.2 artifacts | +semver: minor (#2022)
• _{4f0e483 by Aly Kafoury on Tuesday, March 26 at 14:35 →}
  #683 Validate placeholder duplicates in path templates (#1927)
• _{ded4d7e by Adrien Hupond on Thursday, March 21 at 9:54 →}
  #1518 Create building the IServiceCollection (#1986)
• _{d6eefc8 by Raynald Messié on Friday, March 15 at 13:46 →}
  #1875 Use Polly v8 syntax (#1914)
• _{84bd6e4 by Eirik Bjornset on Friday, March 15 at 9:05 →}
  #1216 #1955 #1956 Overloaded AddOcelot method to support merging of configuration files to memory (#1227)

23.1.0

January 2024 (version 23.1.0) aka Hornussen release

Codenamed as Hornussen Sport
Read the Docs: Ocelot 23.1

Focus On

Multiplexing middleware aka Request Aggregation feature

• Significant refactoring and design review of the Multiplexer
• Optimizing multiplexer performance: HttpContext is not copied when there is only one downstream route, and etc.
• Fixed the bug in the multiplexer: HttpContext.User information was not copied if there was more than one downstream request.

System routing. Content streaming when Transfer-Encoding: 'chunked'

• Correction of the bug when creating requests: The header Transfer-Encoding: chunked was present even when there was no content or the request body size was 0. These cases are now addressed.

Updates of the features: QoS, Load Balancer and Error Status Codes

• Quality of Service: Possibility of implementation of custom Polly v8.2 providers. New AddPolly extension methods.
• Load Balancer: Extension of the route key format, ensuring that the key remains unique for cases of UpstreamHost route property and ServiceName vs ServiceNamespace properties in Consul setup.
• Error Status Codes: When 413 Content Too Large, Ocelot now returns a 413 PayloadTooLargeError (Ocelot error code 41).

Documentation for Request Aggregation

• Request Aggregation

Stabilization aka bug fixing

• See all bugs of the January'24 milestone

Honoring 🏅 aka Top Contributors 👏

1^st 🥇 goes to Guillaume Gnaegi for delivering 2 features
2^nd 🥈 goes to Alexander Reinert for delivering 1 feature in 8 files changed
3^rd 🥉 goes to Steven Liekens for delivering 1 feature in 5 files changed with 353 insertions

Starring ⭐ aka Release Influencers

⭐⭐ Guillaume Gnaegi, @ggnaegi
⭐ Alexander Reinert, @alexreinert
⭐ Chris Williams, @williamscs
⭐ Masoud Bahrami, @masoud-bahrami
⭐ Raman Maksimchuk, @raman-m
⭐ Raynald Messié, @RaynaldM
⭐ Steven, @sliekens
⭐ Ugway77, @Ugway77

Features in Release 23.1.0

Milestone: January'24

Logbook

• _{5ec192a by Raman Maksimchuk on Monday, March 4 at 14:12 →}
  Release 23.1 artifacts | +semver: minor
• _{36986d6 by Guillaume Gnaegi on Friday, March 1 at 18:33 →}
  #1825 #1330 #1287 #1069 Improvements of the multiplexing middleware (#1826)
• _{42ac3ca by Guillaume Gnaegi on Friday, March 1 at 12:00 →}
  #749 Bad error handling for IOException while reading incoming request body (#1769)
• _{319e397 by Alexander Reinert on Thursday, February 29 at 22:16 →}
  #1971 #928 Avoid content if original request has no content and avoid Transfer-Encoding: chunked if Content-Length is known (#1972)
• _{8845d1b by Steven on Thursday, February 29 at 9:44 →}
  #849 #1496 Extend the route key format used for load balancing making it unique (#1944)
• _{171e3a7 by Masoud Bahrami on Tuesday, February 27 at 19:05 →}
  Logging bug in HttpRequesterMiddleware (#1953)
• _{0404c24 by Raynald Messié on Monday, February 26 at 9:24 →}
  #1844 More open customization of Polly use (#1974)
• _{108bede by Ugway77 on Thursday, February 22 at 23:38 →}
  #1396 Lost context User in MultiplexingMiddleware (#1462)
• _{a9dff7c by Chris Williams on Thursday, February 22 at 4:25 →}
  Fix typo in the name of the DistributedCacheRateLimitCounterHandler class (#1969)

23.0.0

November-December 2023 (version 23.0.0) aka Sunny Koliada release

Codenamed as Sunny Koliada
Read the Docs: Ocelot 23.0

Focus On

System performance. System core performance review, redesign of system core related to routing and content streaming

• Modification of the RequestMapper with a brand new StreamHttpContent class, in Ocelot.Request.Mapper namespace. The request body is no longer copied when it is handled by the API gateway, avoiding Out-of-Memory issues in pods/containers. This significantly reduces the gateway's memory consumption, and allows you to transfer content larger than 2 GB in streaming scenarios.

• Introduction of a new Message Invoker pool, in Ocelot.Requester namespace. We have replaced the HttpClient class with HttpMessageInvoker, which is the base class for HttpClient. The overall logic for managing the pool has been simplified, resulting in a reduction in the number of CPU cycles.

• Full HTTP content buffering is deactivated, resulting in a 50% reduction in memory consumption and a performance improvement of around 10%. Content is no longer copied on the API gateway, avoiding Out-of-Memory issues.

• Memory consumption summary. We would like to share here some screenshots of K8s pods from our production environment. These charts were created on January 29-30. Special thanks to @RaynaldM for providing the screenshots!
  (Click on the image to see the full resolution picture) 👇

  3 hours chart	1 day chart	2 days chart
  ~300 MB on average	~320 MB on average	~340 MB on average

  Finally, we confirm that memory consumption is stable, and Ocelot ver. 23.0 is ready for use in production environments—even as a containerized application that may lack the memory resources of a Docker container. The typical memory consumption of a minimal ASP.NET Web API application at startup is around 250 MB. However, this figure depends on several indicators, including content body size, application load (i.e., requests per second index), and integration within the application core.
  For high-load systems, a deployed Ocelot Docker container can allocate up to 400-500 MB, but we hope it won’t exceed that range. In our production environment, a container instance typically occupies around 350 MB. We recommend monitoring the deployed containers in your production environment, paying attention to their CPU & memory consumption. We believe that there will be no out-of-memory incidents at all.

Ocelot extra packages. Total 3 Ocelot packs were updated

• Ocelot.Cache.CacheManager: Introduced default cache key generator with improved performance (the DefaultCacheKeyGenerator class). Old version of CacheKeyGenerator had significant performance issue when reading full content of HTTP request for caching key calculation of MD5 hash value. This hash value was excluded from the caching key.

• Ocelot.Provider.Kubernetes: Fixed long lasting breaking change being added in version 15.0.0, see commit 6e5471a. The bug persisted for more than 3 years in versions 15.0.0-22.0.1, being masked multiple times via class renaming! Special Thanks to @ZisisTsatsas who once again brought this issue to our attention, and our team finally realized that we had a breaking change and the provider was broken.

• Ocelot.Provider.Polly: A minor changes without feature delivery. We are preparing for a major update to the package in the next release.

Middlewares. Total 8 Ocelot middlewares were updated

• AuthenticationMiddleware: Added new Multiple Authentication Schemes feature by @MayorSheFF
• OutputCacheMiddleware, RequestIdMiddleware: Added new Cache by Header Value feature by @EngRajabi, and redesigned as Default CacheKeyGenerator feature by @raman-m
• DownstreamUrlCreatorMiddleware: Fixed bug for ending/omitting slash in path templates aka Empty placeholders feature by @AlyHKafoury
• ConfigurationMiddleware, HttpRequesterMiddleware, ResponderMiddleware: System upgrade for Custom HttpMessageInvoker pooling feature by @ggnaegi
• DownstreamRequestInitialiserMiddleware: System upgrade for Performance of Request Mapper feature by @ggnaegi

Documentation for Authentication, Caching, Kubernetes and Routing

• Authentication
• Caching
• Kubernetes
• Routing

Stabilization aka bug fixing

• See all bugs of the Nov-December'23 milestone

Testing

• The Ocelot.Benchmarks testing project has been updated with new PayloadBenchmarks and ResponseBenchmarks by @ggnaegi
• The Ocelot.AcceptanceTests testing project has been refactored by @raman-m using the new AuthenticationSteps class, and more refactoring will be done in future releases

Honoring 🏅 aka Top Contributors 👏

1^st 🥇 goes to Guillaume Gnaegi for delivering 3 features
2^nd 🥈 goes to Igor Polishchuk for delivering 1 feature in 25 files changed
3^rd 🥉 goes to Aly Kafoury for delivering 1 feature in 9 files changed

Starring ⭐ aka Release Influencers

⭐⭐⭐ Guillaume Gnaegi, @ggnaegi
⭐⭐ Raman Maksimchuk, @raman-m
⭐ Aly Kafoury, @AlyHKafoury
⭐ Igor Polishchuk, @MayorSheFF
⭐ Tanmay Seth, @ks1990cn
⭐ Zisis Tsatsas, @ZisisTsatsas
⭐ Mohsen Rajabi, @EngRajabi

Features in Release 23.0.0

Logbook

• _{290fbde by Raman Maksimchuk on Tuesday, February 13 at 14:29 →}
  Release 23.0 | Artifacts | +semver: breaking (#1962)
• _{a1607f5 by ZisisTsatsas on Monday, February 12 at 9:17 →}
  [#1527 #1529] Breaking change to the class renaming of Kube service discovery provider (#1954)
• _{c9510b1 by Igor on Monday, February 5 at 19:39 →}
  #740 #1580 Support multiple authentication schemes in one route (#1870)
• _{f4803c2 by Aly Kafoury on Thursday, January 18 at 20:23 →}
  #748 Match Route configurations for upstream paths when empty Catch-All placeholders at the end of template (#1911)
• _{5e7e76b by Guillaume Gnaegi on Thursday, January 18 at 12:43 →}
  #356 #695 #1924 Custom HttpMessageInvoker pooling (#1824)
• _{bb79587 by Guillaume Gnaegi on Monday, December 18, 2023 at 12:54 →}
  #1724 Reverting back HttpClient full buffering (#1853)
• _{ba641b2 by Raman Maksimchuk on Thursday, December 14, 2023 at 12:18 →}
  #1172 Default CacheKeyGenerator (#1849)
• _{a17242d by Guillaume Gnaegi on Wednesday, December 13, 2023 at 20:42 →}
  #827 #1679 Improve performance of Request Mapper (#1724)
• _{6b1f332 by Tanmay Seth on Friday, December 8, 2023 at 5:49 →}
  #649 Acceptance tests (#1846)
• _{e92b103 by Mohsen Rajabi on Thursday, October 19, 2023 at 10:40 →}
  Cache by header value: a new Header property in (File)CacheOptions configuration of a route (#1172)

Roadmap

We would like to share our team's plans for the future regarding: development trends, ideas, community expectations, etc.

Code Review and Performance Improvements

Without a doubt, we care about code quality every day, following best development practices. And we review, test, refactor, and redesign features with overall performance in mind. In the next few releases (versions 23.x-24.0) we will take care of: generic providers, multiplexing middleware (Aggregation feature), memory management.

Server-Se...

22.0.1

Hotfix release (version 22.0.1) for #1833 issue

Default timeout vs the Quality of Service feature

Special thanks to Alvin Huang!

About

The bug is related to the Quality of Service feature (aka QoS) and the HttpClient.Timeout property.

• If JSON QoSOptions section is defined in the route config, then the bug is masked rather than active, and the timeout value is assigned from the QoS TimeoutValue property.
• If the QoSOptions section is not defined in the route config or the TimeoutValue property is missing, then the bug is active and affects downstream requests that never time out.

Breaking Change

• The old zero value has recovered in the FileQoSOptions class. Make sure your custom code proper usage of the Ocelot.Configuration.DownstreamRoute class QosOptions.TimeoutValue property!

Technical info

In version 22.0, the bug was found in the explicit default constructor of the FileQoSOptions class with a maximum TimeoutValue. Previously, the default constructor was implicit with the default assignment of zero 0 to all int properties.

The new explicit default constructor breaks the old implementation of QoS TimeoutValue logic, as our QoS documentation states:


Finally, the "default 90 second" logic for HttpClient breaks down when there are no QoS options and all requests on those routes are infinite, if, for example, downstream services are down or stuck.

The Bug Artifacts

• Reported bug: 1833 by @huanguolin
• Hotfix PR: 1834 by @huanguolin

Starring ⭐ aka Release Influencers

⭐ Alvin Huang, @huanguolin
⭐ Raman Maksimchuk, @raman-m

Features in Release 22.0.1

Logbook

• _{37265ad by Raman Maksimchuk on Friday, December 08 at 11:46 →}
  Release 22.0.1
• _{ab79b01 by Alvin Huang on Friday, December 08 at 03:59 →}
  #1833 Default timeout(90s) of downstream requests is broken (#1834)

22.0.0

Tag v22.0 → 6740f50

October 2023 (version 22.0.0) aka Swiss Locomotive release

Codenamed as Swiss Locomotive
Read the Docs: Ocelot 22.0

Focused On

Logging feature. Performance review, redesign and improvements with new best practices to log

• Proposing a centralized WriteLog method for the OcelotLogger
• Factory methods for computed strings such as string.Format or interpolated strings
• Using ILogger.IsEnabled before calling the native WriteLog implementation and invoking string factory method

Quality of Service feature. Redesign and stabilization, and it produces less log records now.

• Fixing issue with Polly Circuit Breaker not opening after max number of retries reached
• Removing useless log calls that could have an impact on performance
• Polly lib reference updating to latest 8.2.0 with some code improvements

Documentation for Logging, Request ID, Routing and Websockets

• Logging
• Request ID
• Routing
• Websockets

Testing improvements and stabilization aka bug fixing

• Routing bug fixing: query string placeholders including CatchAll one aka {everything} and query string duplicates removal
• QoS bug fixing: Polly circuit breaker exceptions
• Testing bug fixing: rare failed builds because of unstable Polly tests. Acceptance common logic for ports

Honoring 🏅 aka Top Contributors 👏

1^st 🥇 goes to Guillaume Gnaegi for delivering 2 features in 99 files changed
2^nd 🥈 goes to Raynald Messié for delivering 2 features in 15 files changed
3^rd 🥉 goes to @jlukawska for delivering 1 feature in 51 files changed

Starring ⭐ aka Release Influencers

⭐⭐⭐ @raman-m
⭐⭐ Guillaume Gnaegi, @ggnaegi
⭐⭐ Raynald Messié, @RaynaldM
⭐ Samuel Poirier, @sam9291
⭐ Stjepan, @wast
⭐ @jlukawska

Features in Release 22.0.0

Logbook

• _{349825f by raman-m on Tuesday, November 28 at 15:45 →}
  Switch off the PublishToNuget task
• _{22bc5b6 by raman-m on Monday, November 27 at 22:05 →}
  Release 22.0 | +semver: breaking
• _{b2246a5 by Raynald Messié on Friday, November 24 at 23:21 →}
  #1783 Less logs for circuit breakers (Polly exceptions) (#1786)
• _{388ebc3 by Guillaume Gnaegi on Friday, November 24 at 21:59 →}
  #1744 Avoid calls to 'Logger.Log' if LogLevel not enabled in appsettings.json (#1745)
• _{04ad9bf by raman-m on Tuesday, November 21 at 19:56 →}
  Resolve issues with projects after auto-merging. Format Document
• _{ec55504 by Samuel Poirier on Saturday, November 04 at 13:15 →}
  #1179 Add missing documentation for Secured WebSocket #1180
• _{dabb4b5 by Guillaume Gnaegi on Saturday, November 04 at 09:27 →}
  #1550 #1706 Addressing the QoS options ExceptionsAllowedBeforeBreaking issue (#1753)
• _{ae43f32 by Stjepan on Wednesday, November 01 at 12:41 →}
  #952 #1174 Merge query strings without duplicate values (#1182)
• _{ab3d8e6 by jlukawska on Friday, October 27 at 21:20 →}
  Find available port in integration tests (#1173)
• _{3b776a7 by Raynald Messié on Friday, October 13 at 18:40 →}
  #1712 Bump to Polly 8.0 (#1714)

21.0.0

Upgrade to .NET 8 (version 21.0.0) aka .NET 8 release

Read article: Announcing .NET 8 by Gaurav Seth, on November 14th, 2023
Read the Docs: Ocelot 21.0

About

We are pleased to announce to you that we can now offer the support of .NET 8.
But that is not all, in this release, we are adopting support of several versions of the .NET framework through multitargeting.
The Ocelot distribution is now compatible with .NET 6, 7 and 8. 🎉

In the future, we will try to ensure the support of the .NET SDKs that are still actively maintained by the .NET team and community. Current .NET versions in support are the following: 6, 7, 8.

Technical info

As an ASP.NET Core app, now Ocelot targets net6.0, net7.0 and net8.0 frameworks. Starting with v21.0.0, the solution's code base supports Multitargeting as SDK-style projects. Find out more here: Target frameworks in SDK-style projects.

It should be easier for teams to move between (migrate to) .NET 6, 7 and 8 frameworks. Also, new features will be available for all .NET SDKs which we support via multitargeting.

Honoring 🏅 aka Top Contributors 👏

1^st 🥇 goes to Guillaume Gnaegi for delivering 1 feature in 63 files changed
2^nd 🥈 goes to Raman Maksimchuk for delivering 1 feature in 17 files changed
3^rd 🥉 goes to @raman-m for delivering 1 feature in 5 files changed

Starring ⭐ aka Release Influencers

⭐ Guillaume Gnaegi, @ggnaegi
⭐ Raman Maksimchuk, @raman-m

Features in Release 21.0.0

Logbook

• _{50ff768 by raman-m on Monday, November 20 at 23:43 →}
  +semver: breaking | Release 21.0
• _{7d93623 by Raman Maksimchuk on Monday, November 20 at 23:02 →}
  .NET8 Release artifacts (#1792)
• _{24b507e by Guillaume Gnaegi on Monday, November 20 at 00:41 →}
  #1787 Upgrade to .NET 8 (#1789)