Skip to content
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.

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

HTTP Range header support #5413

Closed
arnaudmm opened this issue Jun 14, 2017 · 5 comments
Closed

HTTP Range header support #5413

arnaudmm opened this issue Jun 14, 2017 · 5 comments

Comments

@arnaudmm
Copy link

Hi,

It looks like xsendfile or X-Accel-Redirect is not supported in Nextcloud (so nginx or apache could manage themself the acceptance of range header)

Is Nextcloud supposed to respect HTTP Range header ? From my point of view it's like it's totally ignoring it.

The problem is my users can't pause/resume download AND Akamai need this headers respected to work.

Any clue on that ?

Thanks

@MorrisJobke
Copy link
Member

Is Nextcloud supposed to respect HTTP Range header ? From my point of view it's like it's totally ignoring it.

It is supported in all WebDav resources and the PDF viewer or the music app already use that.

The problem is my users can't pause/resume download AND Akamai need this headers respected to work.

We don't support Akamai in front of your Nextcloud because URLs are not yet unique to users and Akamai then doesn't know that there are different files for different users on the same URL.

@arnaudmm
Copy link
Author

And what about supporting pause/resume download?

@jasonkuehl
Copy link

Is this still true that Nextcloud and Akamai are not supported?

@xpader
Copy link

xpader commented May 5, 2022

Looks like it's still not supported, view big pdf file in nextcloud is horrible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants