Skip to content

Handle broken range request implementations#18780

Open
konstin wants to merge 1 commit intomainfrom
konsti/async_http_range_reader_0_11_0
Open

Handle broken range request implementations#18780
konstin wants to merge 1 commit intomainfrom
konsti/async_http_range_reader_0_11_0

Conversation

@konstin
Copy link
Copy Markdown
Member

@konstin konstin commented Mar 31, 2026

This updates async_http_range_reader to v0.11.0 to add the missing range request bounds validation: astral-sh/async_http_range_reader#8.

An open question is how we want to behave when the server has an incorrect range request implementation (while advertising range request support). In the current implementation, it warns with the index URL, so that the user is aware that the massive slowdown is caused by a server advertising broken features.

Also removes a dependency where the corresponding repo was deleted.

Fixes #18316

@konstin konstin added the bug Something isn't working label Mar 31, 2026
This updates adds missing range request bounds validation: astral-sh/async_http_range_reader#8

An open question is how we want to behave when the server has an incorrect range request implementation (while advertising range request support). In the current implementation, it warns with the index URL, so that the user is aware that the massive slowdown is caused by a server advertising broken features.
@konstin konstin force-pushed the konsti/async_http_range_reader_0_11_0 branch from 75e3ebf to 115fb00 Compare March 31, 2026 17:02
} else {
url
};
warn_user_once!(
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I would be okay with this being a tracing warning, since it isn't necessarily something the user can proactively fix (if they don't control the server).

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

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Panic with invalid content length in range reader

2 participants