Update from 18.0.0 to 23.0.0 broke upstream URLs with 503

[patolax]

Expected Behavior / New Feature

The following routes work 18.0.0 version.

    {
      "UpstreamPathTemplate": "/api/{version}/adapter/resources/firmware",
      "UpstreamHttpMethod": [ "Get" ],
      "DownstreamPathTemplate": "/api/{version}/adapter/resources/firmware",
      "DownstreamScheme": "http",
      "ServiceName": "Cloud.Services/adapterService"
    },
    {
      "UpstreamPathTemplate": "/api/{version}/adapter/resources/script",
      "UpstreamHttpMethod": [ "Get" ],
      "DownstreamPathTemplate": "/api/{version}/adapter/resources/script",
      "DownstreamScheme": "http",
      "ServiceName": "Cloud.Services/adapterService"
    },

Actual Behavior / Motivation for New Feature

However, the 23.3.3 upgrade returns 503 now.

If I make changes to adapter segment of the UpstreamPathTemplate paths to say, first route adapterX and seconde route to adapterY. Things start to work

Steps to Reproduce the Problem

Add this config on 23.3.3

    {
      "UpstreamPathTemplate": "/api/{version}/adapter/resources/firmware",
      "UpstreamHttpMethod": [ "Get" ],
      "DownstreamPathTemplate": "/api/{version}/adapter/resources/firmware",
      "DownstreamScheme": "http",
      "ServiceName": "Cloud.Services/adapterService"
    },
    {
      "UpstreamPathTemplate": "/api/{version}/adapter/resources/script",
      "UpstreamHttpMethod": [ "Get" ],
      "DownstreamPathTemplate": "/api/{version}/adapter/resources/script",
      "DownstreamScheme": "http",
      "ServiceName": "Cloud.Services/adapterService"
    },

Specifications

• Version: 23.3.3
• Platform: Windows
• Subsystem: Service Fabric

[raman-m]

Hello Tha!

The following routes work 18.0.0 version.
However, the 23.3.3 upgrade returns 503 now.

Could you please attach the content of your logs? I need to review the text of the error message.

To identify the root cause, could you please downgrade from version 23.3.3 to 19.0.0 changing for each major version? This step will assist in pinpointing the precise version that contains the bug and potentially the specific feature that is malfunctioning.

---

    {
      "UpstreamPathTemplate": "/api/{version}/adapter/resources/firmware",
      "UpstreamHttpMethod": [ "Get" ],
      "DownstreamPathTemplate": "/api/{version}/adapter/resources/firmware",
      "DownstreamScheme": "http",
      "ServiceName": "Cloud.Services/adapterService"
    },
    {
      "UpstreamPathTemplate": "/api/{version}/adapter/resources/script",
      "UpstreamHttpMethod": [ "Get" ],
      "DownstreamPathTemplate": "/api/{version}/adapter/resources/script",
      "DownstreamScheme": "http",
      "ServiceName": "Cloud.Services/adapterService"
    },

and

Subsystem: Service Fabric

The configuration appears correct and should function, but there might be issues, particularly with Service Fabric. Have you considered using a single Catch All route for routing purposes? It looks like both routes could be combined as follows:

    {
      "UpstreamPathTemplate": "/api/{version}/adapter/{everything}",
      "UpstreamHttpMethod": [ "Get" ],
      "DownstreamPathTemplate": "/api/{version}/adapter/{everything}",
      "DownstreamScheme": "http",
      "ServiceName": "Cloud.Services/adapterService"
    },

Please try this configuration in version 23.3.3 and inform us of the outcome.

[raman-m]

Top Task

Firstly, it's crucial to determine whether this bug is part of version 23.3.3.
The most critical test involves downgrading to version 23.2.2 ❗
If version 23.2.2 is not affected by this bug, then it will be included in the v23.3 Hotfixes milestone.

[patolax]

See below for test results of different versions.

18.0.0 OK
19.0.4 OK
20.0.0 OK
21.0.0 OK
22.0.0 OK
23.0.0 NOT OK (503)
23.3.3 NOT OK (503)

Only two paths fail, others work fine.

I will rollback to 22.0.0.

[raman-m]

Thank you for the testing! It's beneficial that this issue is not part of the v23.3 Hotfixes milestone, which aids in faster delivery. It appears the root cause emerged in version 23.0.0. The changes between 22.0.1...23.0.0 need to be reviewed to pinpoint which specific feature affects the Service Fabric path matching. Likely, it is the commit f4803c2

[BrunoSampaioDTx]

My team is experiencing the same issue; however, rolling back from the latest version to 22.0.0 yields the same result.

@raman-m

[raman-m]

@BrunoSampaioDTx
I can't see your attachment. Please reupload the image from the clipboard into the edit window so that GitHub will correctly attach the image.

[raman-m]

@BrunoSampaioDTx Dear Bruno,
Your root cause is SSL broken connection 👇

• Downstream url is https://localhost:5080/tenants/...

You have an invalid or broken SSL certificate on the localhost:5080 machine ❗

My team is experiencing the same issue;

False! You are experiencing SSL connection error!

however, rolling back from the latest version to 22.0.0 yields the same result.

Precisely! Changing the Ocelot version will not resolve the SSL connection error. I am curious as to why you are contributing to this thread. The Ocelot team is not responsible for users' environments and networks. If you do not know how to resolve the issue, please consult your DevOps engineer.

Have you also reviewed our Gotchas document? 👉 SSL Errors
If you install a correct and valid SSL certificate on your downstream service host, I believe everything will be fine.