You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cmgchess opened this issue
Nov 20, 2024
· 1 comment
· Fixed by #2210
Assignees
Labels
acceptedBug or feature would be accepted as a PR or is being worked onbugIdentified as a potential bugmergedIssue has been merged to dev and is waiting for the next releaseNov'24November 2024 releaseRoutingOcelot feature: Routing
What's interesting is when I send the request const url = 'https://blablabla.azurecontainerapps.io/entities/${id}/events/recordsdata'; i.e same case as defined in ocelot it worked. The docs mention that it is case-insensitive by default. Is this expected behavior in 23.4.0 or have i missed something.
Specifications
Version: 23.4.0
Platform: .NET 8
Subsystem: Windows
The text was updated successfully, but these errors were encountered:
@cmgchess Hello, thanks for your feedback, indeed, it might be a side effect of the new routing.
Some Testcases are missing. Then, it's a bug, and we will provide a Hotfix. Thanks for your feedback!
acceptedBug or feature would be accepted as a PR or is being worked onbugIdentified as a potential bugmergedIssue has been merged to dev and is waiting for the next releaseNov'24November 2024 releaseRoutingOcelot feature: Routing
Expected Behavior / New Feature
I expected the route to hit
Actual Behavior / Motivation for New Feature
Route didn't hit. Got 400 error .
Steps to Reproduce the Problem
Ocelot
andOcelot.Cache.CacheManager
from 23.3.6 to 23.4.0ocelot.json looks like this
const url = 'https://blablabla.azurecontainerapps.io/entities/${id}/events/recordsdata';
i.e same case as defined in ocelot it worked. The docs mention that it is case-insensitive by default. Is this expected behavior in 23.4.0 or have i missed something.Specifications
The text was updated successfully, but these errors were encountered: