HTTP 400 error and Obfuscated URL tampering
Users see the HTTP 400 error on screen and the Obfuscated URL Tampering error in the Pega log.
The on-screen error displays when users log in to the Pega application. The error also displays when users open the instances list of any rule type and click the second page of the list.
Error MessagesHttp status 400 - Invalid URL used in request
Obfuscated URL tampering - unable to derive cleartext data
Steps to Reproduce
Perform one or both of the following actions:
- Log in to the production environment.
- Open the instances list of any rule type and click the second page of the list.
A defect or configuration issue in the operating environment whereby URL obfuscation of HTTP requests was disabled
Perform the following local-change.
Edit the prconfig.xml file to add the following settings:<env name="initialization/urlencryption" value="true" />
<env name="Authentication/RedirectGuests" value="false"/>
<env name="initialization/submitobfuscatedurl" value="required" />
Published April 11, 2017 - Updated November 10, 2017