Skip to main content

Table of Contents

Deployment behind a reverse proxy


Only available versions of this content are shown in the dropdown

To deploy Pega Platform™ behind an HTTP proxy server, use XF-* extension headers. Deploying in this manner does not require any additional configuration of Pega Platform.

Refer to the documentation for your proxy server or load balancer for information about how to implement XF-* extension headers.

If you are accessing your Pega Platform system via a Load Balancer or a Reverse Proxy, you must ensure it is correctly configured before implementing single-sign on, such as SAML and OIDC. For more information, see:

The following table describes the XF-* extension header properties.

Property Required? Default value Description
X-Forwarded-Proto Required None The original HTTP protocol requested by the client (HTTP or HTTPS).
X-Forwarded-Host Optional from Pega 7.3 and later; required in Pega 7.2.x Host from the standard HTTP header The original host requested by the client. Only one value can be specified; a comma-delimited list is not supported. If X-Forwarded-Host is not specified, configure the proxy to preserve the standard host header.
X-Forwarded-Port Optional 80 (for HTTP) 443 (for HTTPS) The original port requested by the client.

Did you find this content helpful?

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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