Bug ID 569718: Traffic not sent to default pool after pool selection from rule

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.3, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.1.0, 11.5.4

Opened: Jan 25, 2016

Severity: 3-Major

Symptoms

If you have an iRule configured to match a pattern in the HTTP::uri and send it to a non-default pool, subsequent requests in the HTTP keep-alive session will also be sent to the non-default pool even though they do not match the iRule.

Impact

If the pool members are not configured to accept traffic that doesn't match the uri criterial, the server will not respond properly.

Conditions

This occurs after upgrading from 11.5.3 HF1 to 11.5.3 HF2.

Workaround

None

Fix Information

Reverted a change that caused subsequent HTTP requests to go to the non-default pool after it was selected in an iRule.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips