httpclient-factory
Configure Resilient .NET HTTP Clients
Poor HTTP client lifetimes and retry settings can cause connection failures or repeated operations. This skill guides .NET client registration, resilience configuration, request handlers, and testing.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "httpclient-factory" from https://skillstore.io/skills/codewithmukesh-httpclient-factory.md and its manifest at https://skillstore.io/api/skills/codewithmukesh-httpclient-factory/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "httpclient-factory". Which HTTP client registration should a new .NET 10 endpoint use?
Expected outcome:
- Use a named client with keyed registration for direct endpoint injection.
- Set the base address during registration and pass cancellation tokens for requests.
- Configure one resilience pipeline and review retry safety for each operation.
Using "httpclient-factory". Review a payment client that uses standard resilience and posts charges.
Expected outcome:
- Default retries can repeat a charge after an ambiguous failure.
- Disable unsafe-method retries unless the payment provider supports reliable idempotency keys.
- Test transient failures and verify that one logical payment cannot produce multiple charges.
Using "httpclient-factory". How can I test a service without calling its external API?
Expected outcome:
- Construct an HttpClient with a custom HttpMessageHandler that returns controlled responses.
- Inject that client into the service under test.
- Check success and failure behavior without opening network connections.
Security Audit
Medium RiskAll 44 static findings are false positives: 39 match Markdown backticks, and five match illustrative HTTPS addresses. The payment example enables default retries without disabling unsafe methods, creating a duplicate-charge risk. No evidence found of prompt injection, command execution, or intentional data exfiltration.
Confirmed security concerns (1)
Risk Factors
โ๏ธ External commands (39)
๐ Network access (5)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/codewithmukesh-httpclient-factory/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/codewithmukesh-httpclient-factory?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/codewithmukesh-httpclient-factory?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/codewithmukesh-httpclient-factory/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/codewithmukesh-httpclient-factory.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
codewithmukesh. (2026). httpclient-factory security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/codewithmukesh-httpclient-factory/audits/1BibTeX citation
@techreport{codewithmukesh-codewithmukesh-httpclient-factory-2026,
author = {codewithmukesh},
title = {httpclient-factory security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/codewithmukesh-httpclient-factory/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "httpclient-factory security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "codewithmukesh"
date-released: "2026-10-31"
url: "https://skillstore.io/skills/codewithmukesh-httpclient-factory/audits/1"
identifiers:
- type: other
value: "skillstore:codewithmukesh-httpclient-factory:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Integrate an External API
Choose named or keyed clients, configure headers, and add suitable resilience policies for an ASP.NET Core integration.
Review HTTP Reliability
Review connection lifetimes, timeout settings, unsafe retries, shared headers, and handler composition during a service reliability assessment.
Isolate Client Tests
Use an in-memory HttpMessageHandler to test service behavior without contacting an external API.
Try These Prompts
Show a named IHttpClientFactory client for GitHub repository reads in .NET 10. Include request headers, cancellation, and required packages.
Configure a keyed HTTP client for [API name] in an ASP.NET Core endpoint. Explain its lifetime and propagate cancellation tokens.
Add bearer-token and correlation-ID handlers to [client name]. Use per-request headers and provide isolated tests with a custom HttpMessageHandler.
Review [payment client] for duplicate-charge risks. Assess retries, idempotency, timeouts, lifetimes, and handler stacking. Propose fixes and failure tests.
Best Practices
- Use factory-managed clients and select dependency-injection lifetimes that preserve connection management.
- Review retry safety before enabling resilience for payments or other state-changing requests.
- Pass cancellation tokens, set authorization per request, and test clients with controlled handlers.
Avoid
- Creating and disposing a new HttpClient for every production request.
- Retrying non-idempotent operations without explicit safeguards against duplicate effects.
- Stacking standard retry and hedging handlers without a deliberate pipeline design.
Frequently Asked Questions
Which .NET version does this skill target?
Does the skill install packages or run tests?
Does it explain named, typed, and keyed clients?
Are default retries safe for payments?
Can the testing example avoid real network requests?
Can I use this guidance with Claude and Codex?
Developer Details
Author
codewithmukeshLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
7f45681b0327e778bad91dabd0ddd268beec2a19
Maintenance freshness
10/31/2026
Usage
0 downloads ยท 0 views
File structure
๐ SKILL.md