skills.rest
AGIBuild
AGIBuildCOMMUNITY
Explore all skills by this author →
GitHub

http-client-resilience

Configure resilient HTTP clients with IHttpClientFactory and Polly policies.

10|Updated Jan 28, 2026
Search Tags:#resilience#circuit breaker#asp.net core#timeout#retry#http client#polly
One-click install
npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill http-client-resilience
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: http-client-resilience
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/http-client-resilience
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill http-client-resilience

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the inherent unreliability of HTTP calls in distributed systems by implementing robust resilience patterns, preventing cascading failures and ensuring application stability.

Core Features & Use Cases

  • Resilient HTTP Communication: Configures IHttpClientFactory with Polly for retries, circuit breakers, and timeouts.
  • Best Practices: Demonstrates patterns for HTTP client configuration, error handling, logging, and health checks.
  • Use Case: When integrating with external payment gateways or microservices that may experience transient failures, use this Skill to automatically retry failed requests, prevent overwhelming the service with circuit breakers, and set strict timeouts to avoid hanging operations.

Quick Start

Configure a named HttpClient with retry, circuit breaker, and timeout policies using IHttpClientFactory and Polly.

Frequently Asked Questions about http-client-resilience

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure retry and circuit breaker policies for HttpClient in ASP.NET Core?▼

IHttpClientFactory integrates with Polly to configure retry, circuit breaker, and timeout policies for HttpClient in ASP.NET Core. This prevents transient failures from causing cascading issues across distributed services.

Why does improper HttpClient usage cause socket exhaustion in .NET?▼

Improper HttpClient usage causes socket exhaustion in .NET because it does not release underlying sockets. Using IHttpClientFactory manages HttpMessageHandler pools to prevent socket exhaustion and ensure stable HTTP communication.

Can I use Polly to add custom resilience pipelines and timeouts for external service calls?▼

Yes, Polly integrates with IHttpClientFactory to define custom resilience pipelines, strict timeouts, and circuit breakers for external service calls. This prevents hanging operations and stops overwhelming failing microservices.

What's the best way to handle transient failures when integrating external payment gateways in .NET?▼

The best way to handle transient failures when integrating external payment gateways is configuring IHttpClientFactory with Polly. This implements resilient HTTP communication to automatically retry failed requests and apply circuit breakers for stability.

How do I integrate health checks for external service dependencies in ASP.NET Core?▼

You integrate health checks for external service dependencies in ASP.NET Core by combining IHttpClientFactory with Polly policies. This setup includes request/response logging and authentication headers to monitor external service availability effectively.

Related Skills

Explore More Software Engineering Skills→
contentstackcontentstack
2

aspnetcore-integration

Register ContentstackClient in ASP.NET Core DI with typed HttpClient configuration.

Official
Intermediate
rudironsonirudironsoni

dotnet-resilience

Implement Polly v8 resilience pipelines for .NET HTTP clients.

Community
Intermediate
zdanovichnickzdanovichnick
4

logging

Standardize Serilog structured logging in ASP.NET Core applications.

Community
Intermediate
wshaddixwshaddix
71

dotnet-http-client

Configure IHttpClientFactory with resilience and DelegatingHandler chains for .NET HTTP APIs.

Community
Advanced