DefaultProblemDetailsWriter doesn't pass cancellation token to WriteAsJsonAsync

[Youssef1313]

aspnetcore/src/Http/Http.Extensions/src/DefaultProblemDetailsWriter.cs

Lines 53 to 70 in 05434a9

	public ValueTask WriteAsync(ProblemDetailsContext context)
	{
	var httpContext = context.HttpContext;
	ProblemDetailsDefaults.Apply(context.ProblemDetails, httpContext.Response.StatusCode);
	var traceId = Activity.Current?.Id ?? httpContext.TraceIdentifier;
	var traceIdKeyName = _serializerOptions.PropertyNamingPolicy?.ConvertName("traceId") ?? "traceId";
	context.ProblemDetails.Extensions[traceIdKeyName] = traceId;
	_options.CustomizeProblemDetails?.Invoke(context);
	var problemDetailsType = context.ProblemDetails.GetType();
	return new ValueTask(httpContext.Response.WriteAsJsonAsync(
	context.ProblemDetails,
	_serializerOptions.GetTypeInfo(problemDetailsType),
	contentType: "application/problem+json"));
	}

HttpContext has RequestAborted property (of type CancellationToken). WriteAsJsonAsync accepts an optional cancellation token. Should we be passing the cancellation token in this code path?

[github-actions]

Triage Summary

Area: area-minimal — DefaultProblemDetailsWriter lives in src/Http/Http.Extensions/ and deals with ProblemDetails writing via minimal API HTTP result infrastructure (WriteAsJsonAsync, IProblemDetailsService).
Type: bug — A cancellation token is available (HttpContext.RequestAborted) but is not being forwarded to WriteAsJsonAsync, which means request cancellation is not honored in this code path.

Potential Duplicates

• None found

Notes

This is a small but correctness-impacting omission — passing context.HttpContext.RequestAborted to WriteAsJsonAsync would allow the async write to be cancelled when the client disconnects. Good candidate for a straightforward fix.

Generated by Issue Triage Agent for dotnet/aspnetcore for issue #66600 · ● 142.1K · ◷