Get the source code for this video for FREE → the-dotnet-weekly.ck.page/httpclient Want to master Clean Architecture? Go here: bit.ly/3PupkOJ Want to unlock Modular Monoliths? Go here: bit.ly/3SXlzSt
Hi Milan, I have a correlation Id in my web api. I used typed http client in mvc core 6 application. So in that case how to pass x-correlation Id in all my web API from client. Kindly suggest me..
I've been using named clients, but like the idea of strongly typed clients so may try them out. One advantage of being able to apply configuration once is that you can add Polly retry policies and they will be used for all instances of the named/typed client.
Last part was very nice Milan. Many thanks. I preferred named clients many times in projects. I didn't prefer typed clients because I was a little afraid to delve into this lifetime issues when my services are singleton. I am just basically calling CreateClient method in my infra layer with a using() block. This approach didn't give me any problem so far in production.
Nice, have been working with typed clients for a while and find it to be a good approach. The only thing I do differently is inject configuration into the typed client and assign any required headers with the constructor, keeping the configure services nice and clean.
I do exactly the same because i didnt figure out how to retrieve configuration with Option Pattern. I get null from the IConfiguration inside the HttpClient Configuration method. If someone have any idea
What i don't understand i why does it hate to make a new instance of the class injecting the httpclient if we could have a singleton do avoid being garbage collected all the time, is there issues with such techniques?
That's exactly what i was looking for, thanks Milan. Just one question, where do you think those typed clients belong to - Application layer or whatever?
Awesome explanation , but I have a doubt how can I Mock the http call using the typed approach? I mean, I want to write a test for GetByUserNameAsync method where the internal httpClient simulates returning 200 and a predefined json
you said using httpclient in traditional way can exhaust ports in long run, but is this true if we are doing proper dispose by applying using statements?
Thanks! Very well explained and clear code examples! I use the RestSharp for know - because it has support for oAuth1(I need it for an old smartHome device). Are there any helpers for oAuth1 and HttpClient?
Hi, great video! I've just subscribed and I want to ask about the difference between the EShop and Gatherly projects, which one is better to learn from?
Great video! Thank you! Just to confirm when using named clients, the concern over transient vs singleton lifestyles isn't a concern? It's just with typed clients?
Correct. Since you use a factory to create the named client inside the method each time you invoke it, the lifetime of the class instance is not a factor at all. This is true only if the named client is created inside the method. However, should you create (and capture) named clients inside the constructors, you will effectively introduce the same issues as when using the typed client. Capture the factory instead.
Great video....can you please tell how I can configure multiple http client having different token mechanism and adding different authorisation header in each separate request.
If I'm using 10 different named clients, then 10 object of HttpClient is created using IHttpClientFactory. How can we configure a single instance of HttpClient throughout whole application?
ok but what if the token expires and you need to renew it / pass-in it again? to me it seems that with Factory approach you configure it statically at application startup phase.
Is the last solution for types clients with the lifetime settings a valid and good approach to use? or is it more on the hacky side? I have never stumpled upon it, and I knew almost everything else in the video. Though it was much more well explained than I have read.
Typed clients has too many gotcha's. In addition to the messy stuff you added at the end, what if you have multiple services that require the same HttpClient configuration? I just used named configurations and only inject the factory, simples.
@@MilanJovanovicTech Indeed but then what you would have is all that malarkey to provide a specific configuration of a HttpClient which is only ever used by a single type and that type's only job is to wrap a specific configuration of HttpClient. In that case again you might as well have that service type do all that work. It would take the factory and what other config services it needed, and have a private method that returns a configured HttpClient
What if I just call AddHttpClient() and inject HttpClient into services contstructors? Do they share the same instance or every service gets its own copy?
I wanted to ask the same question! @MilanJovanovicTech I would really appreciate if you could elaborate on differences between factory injection and direct client injection 🙏
Hi @Milan. This was an absolute great video and I am learning a ton from this channel and so, thank you. Hey, how can I use the above method (the 3rd way you describe in the above video) if I am working off of a class library project and I need to use httpClient within it. Basically, all my API calls are in a class library project. Is there an optimal way of using httpClient in it because I am worried about port exhaustion? Thanks
If you can create one HttpClient, pass it a SocketsHttpHandler instance at creation with some connection lifetime, and store it in a static field so that it's long-lived - that should suffice
Hello Milan, Thank you for amazing content. Something is bothering me regarding the configurations you need for a HttpClient. Let's say that you have some configuration stored in Azure Key Vault/Azure SQL Database, and each incoming request to our API has some kind of x-clientId header, how would you handle creating named HttpClient or strong typing HttpClient after retrieving some metadata on Azure Key Vault/Azure SQL? Thank you, keep up the good work :)
My use case is a DLL which will be used with a winforms program. I expect that my DLL will be called periodically (hourly) and occasionally for a short burst of http activity. What video do you have that might help me choose the best implementation method? /Rob
"short burst of http activity" - it doesn't look like you can do much harm whichever implementation you opt for. You could create a static HttpClient in the DLL and reuse it.
Admit that you saw my post a few minutes ago, and in 20 minutes you recorded a 12-minute video, edited and uploaded it. Just admit it, I'll forgive you..
![BRASIL vs. URUGUAY [1-1] | RESUMEN | ELIMINATORIAS SUDAMERICANAS | FECHA 12](http://i.ytimg.com/vi/-hWBAuxF1eY/mqdefault.jpg)
Get the source code for this video for FREE → the-dotnet-weekly.ck.page/httpclient
Want to master Clean Architecture? Go here: bit.ly/3PupkOJ
Want to unlock Modular Monoliths? Go here: bit.ly/3SXlzSt
Hi Milan, I have a correlation Id in my web api. I used typed http client in mvc core 6 application. So in that case how to pass x-correlation Id in all my web API from client. Kindly suggest me..
I've been using named clients, but like the idea of strongly typed clients so may try them out. One advantage of being able to apply configuration once is that you can add Polly retry policies and they will be used for all instances of the named/typed client.
Where is your post?
Strongly typed and singletons have problems, so watch out.
@@zfold4702 ?
Named clients are awesome
Last part was very nice Milan. Many thanks. I preferred named clients many times in projects. I didn't prefer typed clients because I was a little afraid to delve into this lifetime issues when my services are singleton. I am just basically calling CreateClient method in my infra layer with a using() block. This approach didn't give me any problem so far in production.
I think you shouldn't manually dispose the instance. I am pretty sure the framework does that automatically.
I agree, if it works don't fix it. Right?
@@MilanJovanovicTech Yesss 😁
Nice, have been working with typed clients for a while and find it to be a good approach. The only thing I do differently is inject configuration into the typed client and assign any required headers with the constructor, keeping the configure services nice and clean.
I think it's better to do the common things inside of AddHttpClient
@@MilanJovanovicTech fair enough, any particular reason?
I do exactly the same because i didnt figure out how to retrieve configuration with Option Pattern. I get null from the IConfiguration inside the HttpClient Configuration method. If someone have any idea
Well explained and practical oriented step by step tutorial. Thank you!
Glad you enjoyed it!
What about using Transient HttpClient service inside Scoped Services? Its ok?
No scoped services were used here
Great Video Milan! Do you have a video showing how you would unit test this pls? (unit test IHttpClientFactory).
I don't yet, sadly. But I would take a look at MockHttp: github.com/richardszalay/mockhttp
You can inject a httpclientfactory instead of httpclient in a typed client to get around the singleton issue.
What's the point of using a typed client then?
great video but I am wondering how you can configure with token that expires?
DelegatingHandler
Great explantion! Will you make a tutorial about Refit? Thanks!
Perhaps, I like that library. Maybe to compare it with HttpClient
What i don't understand i why does it hate to make a new instance of the class injecting the httpclient if we could have a singleton do avoid being garbage collected all the time, is there issues with such techniques?
A new instance of which class?
That's exactly what i was looking for, thanks Milan. Just one question, where do you think those typed clients belong to - Application layer or whatever?
Infra
HttpClient could lead you to place it in Infrastructure
You could create an interface in Application, however
O think you need to make another video explaining how to add retry using Polly. I recomend to use Backoff.DecorrelatedJitterBackoffV2 in this case.
Will do, great suggestion
Awesome explanation , but I have a doubt how can I Mock the http call using the typed approach?
I mean, I want to write a test for GetByUserNameAsync method where the internal httpClient simulates returning 200 and a predefined json
Check this out: github.com/skwasjer/MockHttp
May I know how to add dynamic certificate using HttpClientFactory ? I have to use different certs.
learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/methods-auto/httpclient/httpclient-addcertificate-method
you said using httpclient in traditional way can exhaust ports in long run, but is this true if we are doing proper dispose by applying using statements?
Yes - you'd end up creating too many handler instances. You want it to be long-lived
Thanks for the infiniteTimeSpan. Cool tip 👍
Don't mention it 😁
You should show the strongly typed version using an interface instead.
You don't need interfaces for everything 🤷♂️
Thanks! Very well explained and clear code examples! I use the RestSharp for know - because it has support for oAuth1(I need it for an old smartHome device). Are there any helpers for oAuth1 and HttpClient?
I am not sure, to be completely honest
Hi, great video! I've just subscribed and I want to ask about the difference between the EShop and Gatherly projects, which one is better to learn from?
They're slightly different, cant' say one is better than the other
Great video! Thank you! Just to confirm when using named clients, the concern over transient vs singleton lifestyles isn't a concern? It's just with typed clients?
Correct. Since you use a factory to create the named client inside the method each time you invoke it, the lifetime of the class instance is not a factor at all. This is true only if the named client is created inside the method.
However, should you create (and capture) named clients inside the constructors, you will effectively introduce the same issues as when using the typed client. Capture the factory instead.
Yes, since with named clients you create an instance and dispose of it. If you capture the client in a field, you have a similar issue
Great video....can you please tell how I can configure multiple http client having different token mechanism and adding different authorisation header in each separate request.
You can use a delegating handler for each client
Thank you for the effort in this video!
You're welcome :)
If I'm using 10 different named clients, then 10 object of HttpClient is created using IHttpClientFactory. How can we configure a single instance of HttpClient throughout whole application?
Well if you want to 10 _DIFFERENT_ named clients, you have no other choice
It was a nicely built overview. Thank you!
Glad you liked it!
ok but what if the token expires and you need to renew it / pass-in it again? to me it seems that with Factory approach you configure it statically at application startup phase.
Use a delegating handler
Is the last solution for types clients with the lifetime settings a valid and good approach to use? or is it more on the hacky side? I have never stumpled upon it, and I knew almost everything else in the video. Though it was much more well explained than I have read.
MSFT recommendation: learn.microsoft.com/en-us/dotnet/fundamentals/networking/http/httpclient-guidelines
Great content as always Milan...thank you🤴🏻
You're welcome!
How do you do when you need to fetch the access token dynamically and refresh when it expires with this approach?
Check this out: ruclips.net/video/_u6v4D6qgDI/видео.html
You need a DelegatingHandler on top of the HttpClient
why can not find video about creating read models eventualy with eventual consistency?
It's a recent video, look for Materialized views
Typed clients has too many gotcha's. In addition to the messy stuff you added at the end, what if you have multiple services that require the same HttpClient configuration? I just used named configurations and only inject the factory, simples.
You'd configure the services separately
@@MilanJovanovicTech Indeed but then what you would have is all that malarkey to provide a specific configuration of a HttpClient which is only ever used by a single type and that type's only job is to wrap a specific configuration of HttpClient.
In that case again you might as well have that service type do all that work. It would take the factory and what other config services it needed, and have a private method that returns a configured HttpClient
What if I just call AddHttpClient() and inject HttpClient into services contstructors? Do they share the same instance or every service gets its own copy?
I wanted to ask the same question! @MilanJovanovicTech I would really appreciate if you could elaborate on differences between factory injection and direct client injection 🙏
In theory, it shouldn't work - because no HttpClient would be wired up for that service
Nice content as always! Could you make a video on how to use Swagger documentation with minimal api?
What's to be covered there?
If I were to call API2 from my API1 and the API2 accepts the bearer token that API1 call has is there a way to pass that as header using this method?
You can either create a request object, and set the header. Or set the DefaultRequestHeaders on the HttpClient
Hi @Milan. This was an absolute great video and I am learning a ton from this channel and so, thank you. Hey, how can I use the above method (the 3rd way you describe in the above video) if I am working off of a class library project and I need to use httpClient within it. Basically, all my API calls are in a class library project. Is there an optimal way of using httpClient in it because I am worried about port exhaustion? Thanks
If you can create one HttpClient, pass it a SocketsHttpHandler instance at creation with some connection lifetime, and store it in a static field so that it's long-lived - that should suffice
@@MilanJovanovicTech , got it! It is that oldish pattern of using the HttpClient I guess. Thanks a lot!
What is good configuration for PooledConnectionLifeTime for Integration test project,
that have a hundred test with API calls?
How long does it take for your test suite execute?
What if you make the typed client a static class with a static HttpClient?
That works cool, since clients should be long-lived (at least the underlying message handler)
Great Video!! Just a curiosity: what VS theme are you using? Looks very clean
It's ReSharper
@@MilanJovanovicTech thank you 🙏🏻
Hello Milan,
Thank you for amazing content. Something is bothering me regarding the configurations you need for a HttpClient. Let's say that you have some configuration stored in Azure Key Vault/Azure SQL Database, and each incoming request to our API has some kind of x-clientId header, how would you handle creating named HttpClient or strong typing HttpClient after retrieving some metadata on Azure Key Vault/Azure SQL?
Thank you, keep up the good work :)
I would explore an option of using a DelegatingHandler, to access Key Vault or SQL and get the configuration value.
Must awaited video. Thanks.
Hope you enjoyed it!
Very good content! Thanks Milan.
You're very welcome!
My use case is a DLL which will be used with a winforms program. I expect that my DLL will be called periodically (hourly) and occasionally for a short burst of http activity. What video do you have that might help me choose the best implementation method? /Rob
"short burst of http activity" - it doesn't look like you can do much harm whichever implementation you opt for. You could create a static HttpClient in the DLL and reuse it.
Based on that service, how do you write tests now to test that the httpclient got called once with x url?
Functional testing. Or you can mock the message handler with something like this: github.com/richardszalay/mockhttp
It's a pity that AddHttpClient forces you to use service locator pattern
You win some, you lose some
isn't it better if the typed client actually still has the name client in itself so it's easier to understand for other developers?
A convention I leave to you
Great !! keep the good work !
Thanks, will do!
why not the "using" or "dispose"?
Not needed
Hello, Is it possible to inject httpclient in .net framework 4.8?
Yes, I believe it's available in .NET Framework (and recommended)
Thanks for this lesson
My pleasure!
why didn't you use Try - Catch to Handle Exceptions that may occur
Didn't need it for this example
Now extend this for clients that need to send Jwt Token in headers with refresh token capability
Will do, that requires Delegating Handlers
Should I dispose the HttpResponseMessage?
Yes
well done
Thanks!
great stuff!
Thanks!
Thanks
You're welcome!
Whats the difference between HttpClient and WebClient?
WebClient is obsolete and shouldn't be used: learn.microsoft.com/en-us/dotnet/api/system.net.webclient?view=net-8.0
@@MilanJovanovicTech thank you
I'm sticking to Blazor Server 😂
Why's that?
Admit that you saw my post a few minutes ago, and in 20 minutes you recorded a 12-minute video, edited and uploaded it. Just admit it, I'll forgive you..
Where is your post?
Yes!
If it was true, nothing wrong with this.
You forgot to dispose the clients.
You would only need to do it in the first example
thx alot , consise and informative
Glad it was helpful!!