Question

2
Replies
960
Views
moryh Member since 2017 7 posts
PEGA
Posted: 1 year ago
Last activity: 1 year 8 months ago
Closed

Root Cause Of HTTP Request Corrupted(SECU0001)

Hi

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:

Requested Processing

existing requestor retrieved

First Activity Executed

Rule-Obj-Activity:ReloadSection

Last Step Executed

RULE-OBJ-REPORT-DEFINITION PXRETRIEVEREPORTDATA #20180227T094011.787 GMT Step: 42 Circum: 0

Requested Processing

existing requestor retrieved

First Activity Executed

Rule-Obj-Activity:GetTargets

Last Step Executed

@BASECLASS GETTARGETS #20130919T004727.420 GMT Step: 1 Circum: 0

Requested Processing

existing requestor retrieved

First Activity Executed

Rule-Obj-Activity:ReloadSection

Last Step Executed

@BASECLASS RELOADSECTION #20170710T071709.574 GMT Step: 10 Circum: 0

All these are OOTB activities. So i am not able to understand how these are causing the issue.

Please help to analyze the root cause. Thanks in advance.

System Administration
Moderation Team has archived post
Share this page LinkedIn