Bug ID 506557: IBR tags might occasionally be all zeroes.

Last Modified: Feb 13, 2019

Bug Tracker

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

Known Affected Versions:
11.0.0, 11.1.0, 11.2.0, 11.2.1, 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.5.3 HF2, 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

Fixed In:
12.0.0, 11.6.1 HF1, 11.5.4

Opened: Feb 13, 2015
Severity: 3-Major
Related AskF5 Article:
K45240941

Symptoms

IBR tags might occasionally be all zeroes.

Impact

The content hash for that URL can be incorrectly set to all zeroes, causing an incorrect IBR for that item until it is recached.

Conditions

This might occur when requests to OWS to update cached, expired content, receive updated content from OWS that has no Content-Length header and is uncacheable (that is, served with X-WA-Info code S10206).

Workaround

Avoid the specific preconditions, or disable IBR-TO for the specific content meeting the preconditions.

Fix Information

Uncacheable updates from OWS will no longer set IBR tags to zero.

Behavior Change