System.Net.Http.HttpClient Disable Caching (.Net Standart Project)

Question

In my .NET Standard project I'm using System.Net.Http.HttpClient. How can I disable all caching (request caching especially) in HttpClient?

If server sends responses with no cache header problem solves. But I want to make this on client side. I want to completely disable all caching.

Thanks.

Edit: It looks like I could use WebRequestHandler but this does not exist in .NET standard. I can only use HttpClientHandler but HttpClientHandler doesn't have any option about caching.

marv51 · Accepted Answer · 2020-07-24 10:12:58Z

42

You can use CacheControlHeaderValue in HttpClient

using System.Net.Http.Headers;

httpClient.DefaultRequestHeaders.CacheControl = new CacheControlHeaderValue
{
  NoCache = true
}

For more information you can look https://learn.microsoft.com/en-us/dotnet/api/system.net.http.headers.cachecontrolheadervalue

edited Jul 24, 2020 at 10:12

marv51

3761 silver badge13 bronze badges

answered Dec 19, 2018 at 20:11

Agshin Nabiyev

5365 silver badges3 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

pvma · Accepted Answer · 2019-10-01 03:47:47Z

4

I tried everything, this one worked for me. Just in case some is not able to make the accepted answer work:

var uri = new Uri("http://localhost:8080/v?time=" + DateTime.Now);
var client = new HttpClient();
var response = await client.GetAsync(uri);

answered Oct 1, 2019 at 3:47

pvma

55111 silver badges18 bronze badges

2 Comments

Josh Aug 27 at 14:57

I'm confused to what this solution is doing. Are you recommending newing up an HttpClient for each request? If that's the case, be aware that HttpClient is designed to be shared throughout the application. Creating a new one on each request is likely to run you out of TCP sockets. (If you're using ASP.Net or modern .Net, you'll want to use services.AddHttpClient(). If using .Net's service collection isn't an option, then HttpClientFactory will also handle pooling HttpClients.)

Frank Alvaro Oct 3 at 14:02

@Josh - I think the idea is to use a unique query argument to bust the cache lookup. You are correct though in that new'ing up a HttpClient for each request is <strike>generally</strike> a bad idea.

Collectives™ on Stack Overflow

System.Net.Http.HttpClient Disable Caching (.Net Standart Project)

2 Answers 2

Comments

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related