Skip to content

fix: stucked byte range requests #462

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

Merged
merged 3 commits into from
Feb 6, 2025

Conversation

Chocobozzz
Copy link
Contributor

Due to an invalid check, the request throws even if it is valid.

total from parseContentRangeHeader is the total amount of bytes of the stream but totalBytes from request is the total amount of bytes of the request that we can infer from to and from

Due to an invalid check, the request throws even if it is valid.

`total` from `parseContentRangeHeader` is the total amount of bytes of
the stream but `totalBytes` from `request` is the total amount of bytes
of the request that we can infer from `to` and `from`
@mrlika mrlika requested a review from DimaDemchenko February 5, 2025 20:27
Copy link
Contributor

@DimaDemchenko DimaDemchenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @Chocobozzz,
Thank you for reporting this bug! We have found a better way to validate the contentRange from the response. Could you please update your PR accordingly?

@Chocobozzz
Copy link
Contributor Author

Sure! It's done. You can squash the PR or I can do it manually if you prefer

@DimaDemchenko DimaDemchenko merged commit b26df75 into Novage:main Feb 6, 2025
3 checks passed
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.

3 participants