NimbostratusI would like to bypass a explicit URL from Attack Signatures and RFC Compliance checking. For Example: FQDN: URI: /testing/free
I created the explicit URL as /testing/free and in Advanced setting (Header-Based Content Profiles) default profile with any any and Request Body Handling: Do Nothing
It is not bypassing.
EmployeeWhich version of BIG-IP? You should be able to de-select the checkbox for "Check attack signatures on this URL." In the GUI, that tab should be near the Header-Based Content Profiles tab. There is no similar method to bypass RFC compliance checks--but you can leave the URL in staging so that no blocking will occur.
EmployeeThat's a separate violation based on the attributes of the file type. Can you accept the suggestion to add the file type "no_ext" and/or increase the query string length?