HTTP profile is enforcing RFC. How can I see logs of the exact violation and block?
For example, if a RST sent due to RFC violation, I could activate BIG-IP system to log TCP RST packets (myF5), but then I only see a general error like "F5RST: Malformed HTTP header error"
How can I log the actual error? For example: duplicate Transfer-Encoding header
Currently, the system does not provide granular logging for the specific reason behind each RFC violation. To determine the exact cause of a reset, you would need to capture the HTTP traffic using a tool like tcpdump and analyze the packet capture to identify the malformed or non-compliant part of the HTTP message.
Thx for the reply. Let me rephrase my question thought. I have an ASM license. Would it be preferable to disable HTTP RFC enforcement at the HTTP profile level and leave the ASM engine handle it instead, so I can get more comprehensive logging details?