Media originals ignore HTTP range requests

Open
#3,279 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
46/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
api, backend

Research direction

Start with MediaEndpoints.cs around line 170 and trace how original files are opened by the S3 and Azure storage implementations. Check how ASP.NET Core Results.Stream(...) handles range requests and what each storage can provide for a requested byte range. Done means a range request for an original returns HTTP 206 with the requested range on every storage backend.

Written by the indexing model from the issue text.

Description

plugin type:bug

Problem

MediaEndpoints.cs:170 streams originals with Results.Stream(...) without range processing. MP4, WebM, MP3 and WAV are allowed uploads: Safari and iOS refuse MP4 without 206 answers, seeking re-downloads from the start, and large downloads cannot resume.

Proposal

Enable range processing with a seekable or ranged stream; add a ranged open to the S3 and Azure storages, or redirect a range request to a short-lived presigned URL.

Acceptance

  • A range request for an original answers 206 with the range on every storage

Found in the code review of 17 Nov 2026 (B8).

Dominant language
C#
Stars
569
Forks
107
Avg merge
2h 49m
Merged PRs (30d)
397

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fluentcms/FluentCMS

All issues in fluentcms/FluentCMS

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.