HttpClient & Networking
HttpClient, HttpClientFactory, request/response, error handling, retry policies, async patterns
1Why use IHttpClientFactory instead of instantiating HttpClient directly?
Why use IHttpClientFactory instead of instantiating HttpClient directly?
답변
IHttpClientFactory automatically manages the lifecycle of HttpClient instances and prevents socket exhaustion. Directly instantiating HttpClient in a using statement can cause TIME_WAIT connection issues that remain open even after disposal. Using IHttpClientFactory also enables configuring resilience policies with Polly and efficiently managing connection pooling.
2What is the main difference between a Named Client and a Typed Client?
What is the main difference between a Named Client and a Typed Client?
답변
A Typed Client encapsulates HTTP call logic in a dedicated class with dependency injection, while a Named Client is retrieved via IHttpClientFactory.CreateClient(name). Typed Clients offer better separation of concerns and facilitate unit testing by encapsulating configuration and business logic. Named Clients are useful for simple cases where multiple different configurations are needed without complex business logic.
3How to configure a global timeout for all HttpClient instances in an application?
How to configure a global timeout for all HttpClient instances in an application?
답변
Configuring the timeout via ConfigurePrimaryHttpMessageHandler allows defining a timeout at the handler level that will apply to all clients created by the factory. This approach centralizes configuration and avoids code repetition. It's also possible to configure the timeout individually on each HttpClient, but this becomes difficult to maintain in a large application with multiple configured clients.
Which method allows reading the body of an HTTP response as a string?
What is the role of a DelegatingHandler in the HttpClient pipeline?
+17 면접 질문