Forum Discussion
biggaraga
Nimbostratus
For clarification, my team has been reading through these:
Disable the Unparsable request content violation
You may disable the Unparsable request content violation in the affected security policies.
Impact of workaround: The BIG-IP will no longer trigger violations for any unparseable content, not specifically limited to Authorization headers.
Enable the 'ignore_authorization_header_decode_failure' internal parameter
Consider enabling this internal parameter to ignore only failures to decode authorization headers, leaving the Unparsable request content violation enabled in the policy.
There’s two options here, and we’re wondering if this is granular to do per policy or if we have to do for all policies. Could you give us clarity?
Thanks
biggaraga
Jun 07, 2021Nimbostratus
It's not immediately clear to us whether we have the option to do the first option (disable the Unparsable request content violation) for specific policies because of how the impact sentence is phrased. Does that option cover specific policies or all policies behind F5_ASM?
Similarly with the second option, 'ignore_authorization_header_decode_failure' -- does that option cover specific policies or all policies behind F5_ASM?