Bug ID 459851: Connection aborted when using GET request If-Match header in Policy Node with No-Proxy(request)/Always_Proxy(response) setting.

Last Modified: Jul 13, 2024

Affected Product(s):
BIG-IP WAM(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 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.1 HF10, 11.5.1 HF11, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10

Fixed In:
11.6.0, 11.4.1 HF9

Opened: Apr 30, 2014

Severity: 3-Major

Related Article: K16570

Symptoms

The connection is aborted when using If-Match header with a Always Proxy response policy node but No Proxy request policy node.

Impact

The connection is reset when it should return 412.

Conditions

Virtual server with Web Accelerator. GET request with Header: If-Match with strong tag. WA Policy: Node matching the request: No-Proxy Node matching the response: Always Proxy

Workaround

None.

Fix Information

When using If-Match header with a Always Proxy response policy node but No Proxy request policy node, the connection condition returns 412, which is correct behavior.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips