Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

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 Messages

Http 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.

Root Cause

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" />

Suggest Edit

Published November 10, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us