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

UpdaterThread: Check for Content-Range instead of Accept-Ranges #30

Merged
merged 1 commit into from
Dec 22, 2023

Conversation

chenxiaolong
Copy link
Owner

nginx only returns Accept-Ranges if the request was sent without the Ranges header.

Fixes: #29

nginx only returns Accept-Ranges if the request was sent without the
Ranges header.

Fixes: #29

Signed-off-by: Andrew Gunnerson <accounts+github@chiller3.com>
@chenxiaolong chenxiaolong self-assigned this Dec 22, 2023
@chenxiaolong chenxiaolong merged commit c242197 into master Dec 22, 2023
4 checks passed
@chenxiaolong chenxiaolong deleted the ranges branch December 22, 2023 00:30
chenxiaolong added a commit that referenced this pull request Dec 22, 2023
Signed-off-by: Andrew Gunnerson <accounts+github@chiller3.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

IOException (Server does not support byte ranges)
1 participant