HTTP Headers

HTTP headers are the core part of the HTTP requests and responses. They pass additional information with an HTTP request or response (e.g. the client browser, requested page, server, and more).

The main headers used with environments for deploying your applications:

hostSpecifies the host and port number of the resource (server) being requested.{envName}.{platformDomain}
x-forwarded-protoIdentifies the protocol (HTTP or HTTPS) that connects to your proxy or load balancer.http/https
x-forwarded-forIdentifies the originating IP addresses of a client connecting to a web server through an HTTP proxy or load balancer.xx.xx.xx.xx, xx.xx.xx.xx
IP or IPs chain (if a request goes through multiple proxies)
x-real-ipThe ending IP address in the x-forwarded-for chain, i.e. the most recent proxy of a client connecting to a web server.xx.xx.xx.xx
the right-most IP address in x-forwarded-for
x-hostThe originating domain name of the server (for virtual hosting) and optionally the TCP port number.{envName}.{platformDomain}
x-uriIdentifies a name or a web resource./
Tip: Additional security headers are used for some specific stacks.

The list of supported HTTP headers can vary based on the topology of the connected environment. Due to external access specifics (via resolver/SLB or public IP), there are four possible scenarios when working with the platform:

TopologySchemeSupported Headers
Single application serverSLB to app serverhost
Load balancer with application serversSLB to load balancerhost
Application server with public IPpublic IP to app serverhost
Load balancer with public IP and application serverspublic IP to load balancerhost

Security Headers

You can easily manage security headers by managing the appropriate configuration file. The path is different for different servers:

  • Apache (PHP, Ruby, Python), MySQL, MariaDB: /etc/httpd/conf.d/10-shared_headers.conf
  • NGINX (PHP, Ruby) and LEMP: /etc/nginx/conf.d/headers/10-shared_headers.conf
  • LiteSpeed, LLSMP: /var/www/conf/vhconf.xml (adjust via the admin panel only)
  • Tomcat, TomEE: /opt/tomcat/conf/web.xml


  • The headers processing for the Node.js, Golang, .NET, JavaEngine, and Springboot servers must be implemented manually in the user application.
  • For the Tomcat and TomEE stacks, only the following headers are enabled by default: X-Content-Type-Options, X-Frame-Options, X-XSS-Protection, and Strict-Transport-Security (for SSL). Other headers can be enabled manually, if needed.

security headers configuration file

Don’t forget to restart your server to apply any changes made to the configuration file.

The following additional HTTP headers are used on the above-listed stacks by default:

Cross-Origin-Embedder-PolicyAllows the server to declare an embedded policy for the given document.unsafe-none;
Cross-Origin-Opener-PolicyPrevents other domains from opening/controlling a window.same-origin-allow-popups
Cross-Origin-Resource-PolicyPrevents other domains from reading the response of the resources to which this header is applied.same-origin
Content-Security-PolicyControls resources the user agent is allowed to load for a given page. Disabled by default.frame-ancestors ‘self’;frame-src ‘self’;
Expect-CT (only with SSL enabled)Allows sites to enforce the Certificate Transparency requirements, which prevents the use of miss issued certificates for the site (i.e requires that any certificate for that site appears in public CT logs).max-age=3600, enforce
Permissions-PolicyProvides a mechanism to allow and deny the use of browser features in its frames and embedded iframes.payment=(self)
Strict-Transport-Security (only with SSL enabled)Forces communication using HTTPS instead of HTTP.max-age=5; includeSubDomains
X-Content-Type-OptionsDisables MIME sniffing and forces the browser to use the type given in Content-Type.nosniff
X-Frame-OptionsIndicates whether a browser should be allowed to render a page in a <frame>, <iframe>, <embed>, or <object>.SAMEORIGIN
X-Permitted-Cross-Domain-PoliciesSpecifies if a cross-domain policy file (crossdomain.xml) is allowed. The file may define a policy to permit clients to handle data across domains that would otherwise be restricted due to the Same-Origin Policy.none
Referrer-PolicyControls how much referrer information (sent via the Referer header) should be included with requests.strict-origin-when-cross-origin (default)
X-XSS-ProtectionEnables cross-site scripting filtering.1; mode=block

What’s next?