Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

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.

Deployment behind a reverse proxy

Updated on April 5, 2022

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.

Note: 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.

PropertyRequired?Default valueDescription
X-Forwarded-ProtoRequiredNoneThe original HTTP protocol requested by the client (HTTP or HTTPS).
X-Forwarded-HostOptional from Pega 7.3 and later; required in Pega 7.2.xHost from the standard HTTP headerThe 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-PortOptional80 (for HTTP) 443 (for HTTPS)The original port requested by the client.

Tags

Pega Platform 8.4 System Administration

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us