Bug ID 476460: WAM Range HTTP header limited to 8 ranges

Last Modified: Jun 17, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP AAM(all modules)

Known Affected Versions:
11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 12.0.0

Fixed In:
12.1.0, 12.0.0 HF1, 11.6.2, 11.5.3 HF2, 11.4.1 HF9

Opened: Aug 21, 2014
Severity: 3-Major
Related AskF5 Article:
K16143

Symptoms

When doing a request with multiple ranges, depending on the current state of the document in the cache (due to previous requests), WAM responds with 'HTTP 416 Requested range not satisfiable'.

Impact

Document is not possible retrieve, even with valid range values.

Conditions

Client requesting more than 8 ranges in a single HTTP Range request for a document that has an active cache record.

Workaround

Force the document to not be cached in the Policy and to be always proxied to the OWS.

Fix Information

Use db variable Wam.Cache.Range.MaxRanges to increase the number of max allowed sub-ranges in a HTTP range request. It defaults to a maximum of 8 sub-ranges, however it can be increased up to 32.

Behavior Change