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.
Mit meinem Agent installieren
Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das 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.Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.
Agent-lesbare Ressourcen
Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.
Testen
„httpclient-factory“ wird verwendet. Which HTTP client registration should a new .NET 10 endpoint use?
Erwartetes Ergebnis:
- 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.
„httpclient-factory“ wird verwendet. Review a payment client that uses standard resilience and posts charges.
Erwartetes Ergebnis:
- 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.
„httpclient-factory“ wird verwendet. How can I test a service without calling its external API?
Erwartetes Ergebnis:
- 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.
Sicherheitsaudit
Mittleres RisikoAll 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.
Bestätigte Sicherheitsbedenken (1)
Risikofaktoren
⚙️ Externe Befehle (39)
🌐 Netzwerkzugriff (5)
Diesen Bericht teilen & zitieren
Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.
Berichtslink kopieren
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>Einbettungskarte
<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>Wissenschaftliche Zitate (APA · BibTeX · CFF)
APA-Zitat
codewithmukesh. (2026). httpclient-factory security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/codewithmukesh-httpclient-factory/audits/1BibTeX-Zitat
@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
Warum dieser Score Evidenzvertrauen: MittelWas Sie erstellen können
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.
Diese Prompts ausprobieren
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.
Bewährte Praktiken
- 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.
Vermeiden
- 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.
Häufig gestellte Fragen
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?
Entwicklerdetails
Autor
codewithmukeshLizenz
MIT
Skillstore-Revision
r1
Versionshinweis
Der Autor hat keine Version angegeben.
Ref.
7f45681b0327e778bad91dabd0ddd268beec2a19
Aktualität der Wartung
31.10.2026
Nutzung
0 Downloads · 0 Aufrufe
Dateistruktur
📄 SKILL.md