HTTP In Memory Response Cache #1774
Replies: 2 comments
-
|
Hi, Just to let you know that I just pushed Apizr v6.1.0 which includes your response caching feature on top of Refit. Let me know if it suits your needs or if I forgot something :) |
Beta Was this translation helpful? Give feedback.
-
|
HTTP caching is out of scope for Refit's core - Refit is a thin typed wrapper over HttpClient and intentionally stays out of the response pipeline beyond serialization. The right place for conditional-request / 304 / If-Modified-Since handling is a As JeremyBP noted, this is already available built on top of Refit: Apizr v6.1.0+ ships exactly this via its Recommendation: use Apizr, or write a small caching |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
We need an HTTP client that leverages ASP.NET Core Response and/or Output caching (which uses relatively standard HTTP caching headers).
Would this be something you would accept into Refit or should we build on top of/to the side of Refit?
We are initially looking to support the
If-Modified-Sincecaching mechanism, in short:If-Modified-Sincefor requests in question where we have a cached entry304is returned, return cached response, otherwise store the result adhering to cache headers, and return it.Beta Was this translation helpful? Give feedback.
All reactions