Symptoms

An "Unparsable request content" violation is detected for valid headers without a space after the headers name ':'

Impact

Requests that suppose to pass are blocked by ASM enforcer

Conditions

Any header without a space between the ':' and the header value will trigger "Unparsable request content"

Workaround

The client has to send headers with space after ':'

Fix Information

No "Unparsable request content" violation for headers with space after ':'

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips