Remove the need of temp files from the handling of Range requests #623
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit requires sabre-io/http#45 to work.
The other day, I tried to play a 10 gig HD movie from my Owncloud server through GVFS. It failed, and hanged my server by forcing PHP to create humongous temp files. (see owncloud/core#15321) As it turns out, the problem was with HTTP Range requests: SabreDAV decided to create temp files with the the entire contents of the range (GVFS requested ranges like 40960-). So I went ahead to create this pair of small patches.
I am looking forward to hearing your opinion on the matter. Sorry for not opening a discussion beforehand, but discussing it would have taken longer than writing it.
And yes, with these applied, I have managed to play the video, at least in a separate SabreDAV install.