Posted: 31 Jan 2019 8:00 EST Last activity: 1 Feb 2019 5:02 EST
Root Cause Of HTTP Request Corrupted(SECU0001)
I am getting HTTP Request Corrupted(SECU0001) alert log in production. I have below understanding:
HTTP Request corrupt(SECU0001) alert is generated during the processing of HTTP requests. Properties that are not in the list of expected properties are ignored by the system during the processing of HTTP requests. After all HTTP parameters have been processed, the system generates this security alert, and lists all unexpected properties.
We can suppress this by doing configuration in prconfig file.
But i have to find the root cause. I analysed this in AES and got below summary:
These articles mentioned about disabling the alert in prconfig file. But i want to understand how ReloadSection, GETTARGETS OOTB activities are producing these alerts. Because in my application there is no integration with external application. Means i am not receiving request from external system. Then how extra properties are getting received in the HTTP request.