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

Pega Web Mashup Only works on Chrome browser

SA-23924

Summary



User requirement is to display a Pega Web Mashup interface.
The Pega Web Mashup configuration works fine with Chrome browser, but not on Internet Explorer and Firefox browsers.

 


Error Messages



HTTP 400 error


Steps to Reproduce



Open page that contain Pega Web Mashup code.


Root Cause



A defect or configuration issue in the operating environment. The root cause is that the same origin policy was not respected.
The portal was an HTML file located in the Windows folder, with an Mashup gadget pointing to Prgateway in the Pega cloud.
In such case, the origin of the HTML file is seen as "null" for the HTML page and as the Pega cloud URL for the IAC gadget, hence not the same.
Browser behaves differently, more or less strict regarding this which explain the issue's different behavior.

Resolution



Perform the following local-change: 

Install prgateway in the same location as the portal to ensure the same origin policy, so that the URL host, port, domain, protocol for the portal is same as the one for prgateway.
 
 
Following link provides example of valid URL combination:
 
https://pdn.pega.com/setting-gatewayurl-configuration-parameter
 
 
Web application page URL (as seen by the web browser) Pega Gadget URL (as seen by the web browser at runtime) Valid Configuration?
https://www.pega.com/MyWebApp/home.html https://www.pega.com/MyWebApp/gadgetA.html YES
https://www.pega.com/MyWebApp/home.html https://www.pega.com/MyGadgets/gadgetA.html YES
https://www.pega.com/MyWebApp/home.html https://gadgets.pega.com/MyWebApp/gadgetA.html NO – different host name
https://www.pega.com/MyWebApp/home.html https://PRPC.gadgets.pega.com/MyWebApp/gadgetA.html NO – different host name
https://www.pega.com/MyWebApp/home.html https://pega.com/MyWebApp/gadgetA.html NO – different host name
https://www.pega.com/MyWebApp/home.html http://www.pega.com/MyWebApp/gadgetA.html NO – different protocol
https://www.pega.com/MyWebApp/home.html https://www.pega.com:7878/MyWebApp/gadgetA.html NO – different port

 

Published June 6, 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?

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