http-pipeline

Customize HTTP pipeline behavior for Contentstack.Management.Core in the .NET SDK.

2|4|Updated Jun 30, 2021
One-click install
npx skills add https://github.com/contentstack/contentstack-management-dotnet --skill http-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: http-pipeline
Source: https://github.com/contentstack/contentstack-management-dotnet/tree/main/skills/http-pipeline
Command: npx skills add https://github.com/contentstack/contentstack-management-dotnet --skill http-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage and customize the HTTP pipeline within the Contentstack.Management.Core runtime to control request handling, retry behavior, and the ordering of pipeline components.

Core Features & Use Cases

  • Modify and tune HttpHandler, RetryHandler, DefaultRetryPolicy, and RetryConfiguration to align with app needs.
  • Reorder pipeline components by updating ContentstackClient.BuildPipeline and observing outer-to-inner execution flow.
  • Debug and optimize retry loops, status handling (e.g., 5xx, 429), and network error classification for reliable CMA interactions.

Quick Start

Configure a ContentstackClient, adjust the pipeline order, and run a representative request to observe the interaction between HttpHandler and RetryHandler.

Frequently Asked Questions about http-pipeline

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

FAQPage Schema
How do I customize the HTTP pipeline retry behavior in the Contentstack .NET SDK?

Customize the HTTP pipeline retry behavior by modifying RetryConfiguration and DefaultRetryPolicy within Contentstack.Management.Core to align retry loops with your application's network error handling requirements.

How does the DefaultRetryPolicy handle HTTP server errors and network errors?

DefaultRetryPolicy classifies network and HTTP server errors like 5xx and 429 status codes to determine retry loops within the pipeline, ensuring reliable Contentstack Management API interactions during transient failures.

What is the best way to reorder HTTP handlers in the ContentstackClient pipeline?

Reorder HTTP handlers by updating ContentstackClient.BuildPipeline to observe the outer-to-inner execution flow, allowing you to control the precise sequence HttpHandler and RetryHandler process requests.

Can I configure custom HTTP request handling for different environments in Contentstack.Management.Core?

Yes, you can modify and tune HttpHandler within the HTTP pipeline to align with various environment needs, controlling how requests are dispatched before retry logic is applied.

Why does my HTTP retry loop keep triggering on 429 status codes in the .NET SDK?

The retry loop triggers on 429 status codes because DefaultRetryPolicy identifies them as transient HTTP server errors, applying RetryConfiguration rules to attempt the request again until limits are reached.

Do I need to adjust RetryConfiguration to optimize Contentstack CMA network interactions?

Adjusting RetryConfiguration is necessary to optimize retry loops and status handling, allowing you to fine-tune how the pipeline responds to network errors and HTTP server errors during Contentstack CMA interactions.