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

PRGateway not loading content correctly



When setting the web application with Pega Web Mashup (IAC) to use the Pega Standard Servlet (PRServlet), access to the application is successful, the content is loaded and work objects can be created.

When instead the web application is set to use the PRGateway URL, the content is not loaded interactively and doesn't display correctly.
It was observerd in particular that javascript files were not loaded.

Error Messages

No error message

Steps to Reproduce

- Create a Pega Case Type
- Create an Operator, a Portal and an Access Group to access that Case Type
- Setup Pega Web Mashup (IAC) to access the system and create the new work object with the data previously defined.
- To avoid any cross domain issues the HTML to be used must be deployed on the same domain Pega is running.
- Use the sample HTML generated by Pega Web Mashup (IAC) to test the Case Type

Root Cause

A defect or configuration issue in the operating environment.
The requirement for PRGateway is just to be on the same domain as the portal. This requirement was met.

However there is also the requirement for the same origin policy which is a different requirement:
Due to web browser enforcement of the same-origin policy rules for website pages, the gateway URL you specify for the gadget must appear to the browser at runtime to match the site URL presented in the web browser at runtime for the web application page, including the same protocol, full host domain name, and port.

So from the point of view of the browser (IE, Firefox…), the url of the portal and PRGateway must have the same host/port/domain.

In this case, it was observed the portal and PRGateway url didn't have the same host and port (from the client perspective), hence the content was not loaded properly.


Re-configured the proxy with redirection such that from the client perspective (IE9, Firefox), the portal and gateway had the same port, host and domain.

Published February 25, 2016 - Updated December 2, 2021

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