Pega Web Mashup Only works on Chrome browser
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.
HTTP 400 error
Steps to Reproduce
Open page that contain Pega Web Mashup code.
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.
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:
|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://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.