nextcloud / nextcloud/server

[WebDAV] Add "Accept-Ranges: bytes" header

Open
#42,528 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement feature: dav hotspot: file transfer performance performance 🚀
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

Nextcloud seems to support range requests (partial downloads), but it doesn't seend an Accept-Ranges: bytes header.

It could add such a header to HEAD (and maybe other) responses for WebDAV files to advertise this support.

In case of DAVx5, DAVx5 can open a resource in random-access mode instead of the less flexible streaming mode when DAVx5 knows that the server supports ranged requests.

Contributor guide

Open the contributing guide

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.

Research direction

Start by locating the WebDAV response handling for file resources and inspect how HEAD responses and range requests are currently handled. Confirm which relevant responses should advertise byte ranges, then verify the resulting header behavior with the existing WebDAV test coverage or an appropriate request-level check.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
api, backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.