How to catch Ocelot exceptions?

[Tingtzong]

Expected Behavior / New Feature

when an exception (404 NotFound exception) occur in ocelot. when we use try-catch try to catch this exception, we should be able catch this exception.

Actual Behavior / Motivation for New Feature

ocelot not throw this exception, swallowed, so the try-catch did not work.

Steps to Reproduce the Problem

1. add a handler to ocelot. add try-catch to this handler
2. when an exception happen, try-catch code will be ignore, and can not get any exception.

Specifications

• Version: lastest
• Platform: .net core
• Subsystem:

[neetra]

@Tingtzong
Could you please share the sample code?

[raman-m]

@Tingtzong

Actual Behavior / Motivation for New Feature

ocelot not throw this exception, swallowed, so the try-catch did not work.

Exactly! Have you ever heard or read about Error Status Codes feature?
We have a global Exception handler which prevents Ocelot instance failing/hanging because of 5xx errors in downstream services.
But we don't consider this design good because we override status and some headers. See notes about Design

Please develop Delegating Handler to catch exceptions in and read original status of downstream service response.
A delegating handler is exactly right place to catch exception, but we recommend to re-throw it!

Also, PreErrorResponderMiddleware injection should help you too. See Middleware Injection plz!