dotnet / dotnet/aspnetcore

Make FileResult and ContentResult use Pipelines

Open
#7,840 9 comments 0 reactions 0 assignees View on GitHub
affected-few area-mvc area-networking enhancement feature-pipelines severity-nice-to-have
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 10h
Merged PRs (30d)
281

Description

Both executors are using the response stream today. These can go ahead and use the BodyPipe instead.

https://github.com/aspnet/AspNetCore/blob/c565386a3ed135560bc2e9017aa54a950b4e35dd/src/Mvc/Mvc.Core/src/Infrastructure/ContentResultExecutor.cs#L24
https://github.com/aspnet/AspNetCore/blob/7af971838ec527221f4260bae3bf11e8ae5b035c/src/Mvc/Mvc.Core/src/Infrastructure/FileResultExecutorBase.cs#L361

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.