raman-m
commented
1 month ago Hello, Mert! It's great to know that you've incorporated Ocelot into your products!
As for the caching issue...
I am using Ocelot in my .NET project and have recently implemented a new caching mechanism.
Please note that we cannot be held accountable for hybrid solutions if modifications have been made to Ocelot services.
I have encountered an issue where Ocelot is using the same cache key for different requests even though the request bodies are different.
It's important to note that the cache key is generated based on the route definition, which includes paths, service names, HTTP verbs, etc. For a more effective analysis, could you please provide your ocelot.json file? Regarding the cache versus load balancing keys, we have addressed this in the past with:
- PR #1944
- A commit in the develop branch: https://github.com/ThreeMammals/Ocelot/commit/8845d1b98d2c3b0bd633ebd2b526b923687edd33
The aforementioned fix was included in the release of version 23.1.0, which you can find here: 23.1.0
Regarding body hashing for cache keys, we have implemented a fix:
- PR #2058
- Commit: https://github.com/ThreeMammals/Ocelot/commit/6e9a975fae3b26229c3f0b3c1a475a7b05e95fee
This fix will be included in the upcoming release, version 23.3, which is scheduled for release in a few days. Please look out for the new version! If you require the bug fix urgently, you may fork the repository and compile the DLL manually in Visual Studio.
Is there anything else I can assist with?
mertgundoganx
I am using Ocelot in my .NET project and have recently implemented a new caching mechanism. However, I have encountered an issue where Ocelot is using the same cache key for different requests even though the request bodies are different. As a result, different requests are returning the same response.
Specifications