Ensure all requests are HTTP secured

Dear Pega Support Team, Greetings of the day!

We have an application built on top of pega platform. After logging in, the home page is not rendering properly because the CSS is being requested insecure (HTTP) and the browser is blocking any insecure requests. We need to change ALL insecure requests and make them secure. We’re currently on Pega v8.5.4.

Thanks in Advance..

@AniketJ17120971 To resolve the issue of the home page not rendering properly due to insecure (HTTP) CSS requests you need to ensure that all resources are requested over HTTPS. This can be done by configuring your Pega server to use a valid certificate and ensuring that all URLs are secure. Here are the steps you can follow: 1. Host Name and Certificate: Ensure that the Pega server is exposed through a valid name and a valid certificate. Access through non secure HTTP or to an HTTPS server using a self signed certificate is neither allowed nor recommended. 2. Cross Site Request Forgery (CSRF) Settings: If you are using Pega Mashup gadgets explicit approval should be provided on the Pega server. Log in to Pega using your administrator user access the Cross Site Request Forgery landing page (Dev Studio System Settings Cross Site Request Forgery) and disable the necessary attributes. 3. Application Configuration: Register the URL of the WSS demo application as a trusted origin in your application if you are not using the out of the box configuration. 4. Access Groups and Operators: Ensure that the Pega Mashup gadgets embedded in the Web Self Service application have the necessary access. By following these steps you can ensure that all requests are made securely over HTTPS preventing the browser from blocking any insecure requests.

:warning: This is a GenAI-powered tool. All generated answers require validation against the provided references.

Server-side configuration

@MarijeSchillern Thanks, the issue has been resolved. It was issue with application server.