All 17 ASP.NET Core Middleware & Request Pipeline questions
More in ASP.NET Core Middleware & Request Pipeline
What's the difference between app.Use, app.Run, and app.Map in configuring the middleware pipeline? How does short-circuiting work in middleware, and when would you deliberately not call next()? What is the purpose of UseExceptionHandler and UseDeveloperExceptionPage middleware, and how should they differ between environments? How do you conditionally apply middleware only to certain requests using UseWhen or MapWhen? What is middleware in ASP.NET Core, and how does the order in which it's registered affect request handling? What are Minimal APIs in ASP.NET Core, and when would you choose them over traditional MVC controllers? How do you inject scoped (per-request) services into middleware, given that middleware classes are constructed once at app startup? How does UseRouting and endpoint routing (via MapControllers, MapGet, etc.) fit into the middleware pipeline conceptually? How do minimal API endpoint filters (IEndpointFilter) compare to traditional middleware for cross-cutting logic? How does the middleware pipeline interact with asynchronous streaming responses, and what precautions are needed?
Advertisement
.NET › ASP.NET Core Middleware & Request Pipeline

How does the HttpContext object serve as the shared state carrier through the middleware pipeline?

Intermediate

Answer

HttpContext encapsulates everything about a single HTTP request/response cycle -- the request (headers, body, route values), the response (status code, headers, body stream), user identity (once authentication runs), and a Items dictionary for passing arbitrary custom data between middleware components within the same request's lifetime, since each middleware receives the same HttpContext instance as the pipeline executes.
app.Use(async (context, next) => {
    context.Items["RequestStartTime"] = DateTime.UtcNow;  // stash data for later middleware
    await next();
});

app.Use(async (context, next) => {
    var start = (DateTime)context.Items["RequestStartTime"];
    Console.WriteLine($"Elapsed: {DateTime.UtcNow - start}");
    await next();
});
Real-world example A correlation-ID middleware generates a unique ID early in the pipeline, stores it in context.Items, and every subsequent logging call throughout the request (including deep inside business logic) retrieves it via HttpContext to tag all related log entries consistently.

Common follow-ups: How does HttpContext.Items differ from HttpContext.Features for passing data?;Why shouldn't you store HttpContext itself in a singleton service?

Logging;Diagnostics & Performance
All 17 ASP.NET Core Middleware & Request Pipeline questions