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 errors display and unable to download images and script




HTTP 400 errors display and unable to download images and scripts with MuleSoft proxy configuration.

Error Messages

HTTP 400 erorrs display at the user side.

On the server, static content requests display however, they do not contain the AccessGroup hash and errors are thrown.

Steps to Reproduce

  1. Create a widget which can render UI contents of the Case Manager portal
  2. Promote the widget code in a non-Pega application and verify that the widget renders successfully
  3. Replace the gateway URL with reverse proxy URL (Mule ESB) to redirect the traffic through the proxy URL

Root Cause

The Mulesoft proxy configuration by default has FollowRedirects enabled. There were no HTTP 303 for the AccessGroup switch occurring at the browser level because the MuleSoft proxy was following and making the requests. These 303 redirects have to hit the browser so, the base URL contains the AccessGroup hash. Thus, the static content requests also contain the AccessGroup hash as well.


Perform the following local-change:

Set FollowRedirects to false in the Mulesoft configuration.  


Published August 24, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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