Bug ID 1018493: Response code 304 from TMM Cache always closes TCP connection.

Last Modified: Feb 07, 2024

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

Known Affected Versions:
14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0, 16.1.1

Fixed In:
17.0.0, 16.1.2, 15.1.4, 14.1.4.5, 13.1.5

Opened: May 13, 2021

Severity: 4-Minor

Symptoms

When a virtual server is configured to accelerate HTTP traffic, it caches responses with 200 and 304 response codes. Serving a response with "304 Not Modified" code, TMM may close a connection to a client.

Impact

A client needs to open a new TCP connection every time when a response with "304 Not Modified" code is served.

Conditions

-- A virtual server has a web-acceleration profile (without a web application for versions prior 16.0.0). -- A response with code 304, stored in TMM cache, is served to a request.

Workaround

None

Fix Information

TMM correctly serves a response with "304 Not Modified" code, allowing to correctly handle TCP connection status.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips