Bug ID 2187185: BIG-IP v21.0 REST framework incorrectly processes Content-Range in HTTP GET requests

Last Modified: Dec 19, 2025

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
21.0.0

Opened: Dec 18, 2025

Severity: 3-Major

Symptoms

On BIG-IP v21.0, REST-based file download requests may fail with errors such as “attempt to read past end of file” when the client includes a Content-Range header in an HTTP GET request. This occurs when the specified byte range exceeds the actual size of the requested file. The failure is triggered by the BIG-IP REST framework incorrectly attempting to process the Content-Range header for GET requests, resulting in an invalid file offset calculation and an EOF read condition. As a result, the REST request is terminated and the file download does not complete.

Impact

REST-based file downloads fail unexpectedly

Conditions

HTTP GET request includes a Content-Range header The byte range specified in Content-Range exceeds the actual size of the requested file

Workaround

Determine the actual size of the target file and ensure that any Content-Range header sent by the client specifies a byte range that does not exceed the file length. Alternatively, remove the Content-Range header entirely from HTTP GET requests, as it is not required and may cause request failures.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips