Skip to content

FileResult EnableRangeProcessing is an undocumented breaking change #7279

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
maknapp opened this issue Feb 5, 2019 · 1 comment
Closed

FileResult EnableRangeProcessing is an undocumented breaking change #7279

maknapp opened this issue Feb 5, 2019 · 1 comment
Labels
area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates

Comments

@maknapp
Copy link

maknapp commented Feb 5, 2019

With v2.1.0, FileResult does no longer processes the Range header by default - it needs to be enabled via the EnableRangeProcessing flag. This seems like a breaking change that should be documented in the 2.0 to 2.1 migration.

2fcfc6b
aspnet/Mvc#6780
aspnet/Mvc#6895
@Eilon Eilon added the area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates label Feb 5, 2019
@danroth27 danroth27 mentioned this issue Feb 12, 2019
Closed
@danroth27
Copy link
Member

This issue was moved to dotnet/AspNetCore.Docs#10891

@dotnet dotnet locked and limited conversation to collaborators Feb 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Eilon @maknapp @danroth27