CacheCow icon indicating copy to clipboard operation
CacheCow copied to clipboard

An implementation of HTTP Caching in .NET Core and 4.5.2+ for both the client and the server

Results 12 CacheCow issues
Sort by recently updated
recently updated
newest added

Hello @aliostad, thank you for the good work on CacheCow. Since you have already updated Newtonsoft, do you see the possibility to also update Microsoft.AspNet.WebApi.Client to stay up to date?...

We as a company need to do license clearing and so we need to know what source code matches a particular released nuget version. Is it possible to at least...

enhancement

According to this [issue](dotnet/dotnet-api-docs#7970), TraceSwitch value is not longer read from the config. We need an alternative means of controlling tracing.

enhancement

If the server replies with a `Vary` header then the `DefaultVaryHeaders` are not used when computing the cache key. The new `IncludeRangeHeaderInCacheKey` test demonstrates this issue and ensure it's fixed....

On .NET Core (I've tested 2.0 and 2.1) calling `DeserializeToResponseAsync` on `MessageContentHttpMessageSerializer` will crash with certain http responses. (google.com being one of them) I've tested this on 4.7.1 and the...

It seems the three assemblies (CacheCow.Common.sn, CacheCow.Server.sn & CacheCow.Client.sn) were one time releases and were left in version 1.1.1 Any chances to update them to their latest version (2.4.2)? Thanks...

enhancement
wontfix

it would be nice to have a way of adding hook for POST Action and other custom HTTP verb.

enhancement
UpForGrab

Maybe You will be interested in hosting API Explorer online: https://dndocs.com/d/cachecow-client/api/CacheCow.Client.CachingHandler.html This is ready-to-go, so above link can be added to README.md for other people to see it. Or using...

Strong-named all assemblies, fixes #222 https://learn.microsoft.com/en-us/dotnet/standard/assembly/create-use-strong-named