Describe the bug
The WebHDFS provider fails when handling requests without a Range header. Previously, if the request did not include the Range header, the function returned None. After a recent change by the main developer, an exception is raised whenever the provider supports ranges, even if the request does not include a Range header. This breaks the expected behavior where a request without Range should download the entire file.
To Reproduce
Steps to reproduce the behavior:
Use a WebHDFS provider to download a file.
Send a GET request without specifying the Range header.
Observe that an exception is raised instead of downloading the full file.
Expected behavior
When the provider supports ranges, a request without a Range header should still succeed and return the full file.
Screenshots
N/A
Desktop (please complete the following information):
OS: macOS (or your OS)
Browser: Firefox
Version: N/A
Additional context
The bug was introduced after a change in the range check logic 85decf1. WebHDFS should handle requests without a Range header gracefully, even if range support is enabled. Opening this issue to discuss and propose a fix.
Describe the bug
The WebHDFS provider fails when handling requests without a Range header. Previously, if the request did not include the Range header, the function returned None. After a recent change by the main developer, an exception is raised whenever the provider supports ranges, even if the request does not include a Range header. This breaks the expected behavior where a request without Range should download the entire file.
To Reproduce
Steps to reproduce the behavior:
Use a WebHDFS provider to download a file.
Send a GET request without specifying the Range header.
Observe that an exception is raised instead of downloading the full file.
Expected behavior
When the provider supports ranges, a request without a Range header should still succeed and return the full file.
Screenshots
N/A
Desktop (please complete the following information):
OS: macOS (or your OS)
Browser: Firefox
Version: N/A
Additional context
The bug was introduced after a change in the range check logic 85decf1. WebHDFS should handle requests without a Range header gracefully, even if range support is enabled. Opening this issue to discuss and propose a fix.