{"id":40604,"date":"2024-05-10T05:36:10","date_gmt":"2024-05-10T05:36:10","guid":{"rendered":"https:\/\/accuweb.cloud\/resource\/?post_type=faq&p=40604"},"modified":"2026-02-19T06:05:38","modified_gmt":"2026-02-19T06:05:38","slug":"http-headers-in-environment","status":"publish","type":"faq","link":"https:\/\/accuweb.cloud\/resource\/articles\/http-headers-in-environment","title":{"rendered":"HTTP Headers"},"content":{"rendered":"

HTTP Headers<\/h2>\n

HTTP headers are important in HTTP requests and responses that provide more information, including such requested pages, clients’ browsers, etc.<\/p>\n

Here are the main headers that are frequently used while deploying apps in environments:<\/p>\n

\n\n\n\n\n\n\n\n\n\n\n
Header<\/th>\nDescription<\/th>\nValue<\/th>\n<\/tr>\n<\/thead>\n
host<\/strong><\/td>\nProvides the host and port number of the resource (server) being requested.<\/td>\n{envName}.{platformDomain}<\/td>\n<\/tr>\n
x-forwarded-proto<\/strong><\/td>\nIdentifies the protocol (HTTP or HTTPS) used to connect to your proxy or load balancer.<\/td>\nhttp\/https<\/td>\n<\/tr>\n
x-forwarded-for<\/strong><\/td>\nIdentifies the originating IP addresses of a client connecting to a web server using an HTTP proxy or load balancer.<\/td>\n\n

xx.xx.xx.xx, xx.xx.xx.xx<\/p>\n

IP or IPs chain (if a request goes through multiple proxies)<\/p>\n<\/td>\n<\/tr>\n

x-real-IP<\/strong><\/td>\nThe final IP address in the x-forwarded-for chain, or the client’s most recent proxy when connecting to a web server<\/td>\nxx.xx.xx.xx
\nthe right-most IP address in\u00a0x-forwarded-for<\/strong><\/td>\n<\/tr>\n
x-host<\/strong><\/td>\nThe server’s originating domain name (for virtual hosting) and, if applicable, the TCP port number.<\/td>\n{envName}.{platformDomain}<\/td>\n<\/tr>\n
x-uri<\/strong><\/td>\nIdentifies a certain name or web resource.<\/td>\n\/<\/em><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
<\/div>\n

The list of supported HTTP headers<\/strong> may differ depending on the topology of the connected environment. There are four potential scenarios when working with the platform, influenced by external access methods (such as resolver\/SLB or public IP).<\/p>\n

<\/div>\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Topology: <\/b>Single application server<\/td>\n<\/tr>\n
Scheme :<\/b>
\n\"\"<\/a><\/td>\n<\/tr>\n
Supported Headers:<\/b><\/p>\n
    \n
  • host<\/li>\n
  • x-forwarded-proto<\/li>\n
  • x-real-ip<\/li>\n
  • x-forwarded-for<\/li>\n
  • x-host<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
Topology: <\/b>Load balancer with application servers<\/td>\n<\/tr>\n
Scheme :<\/b><\/p>\n

\"\"<\/a><\/td>\n<\/tr>\n

Supported Headers :<\/b><\/p>\n
    \n
  • host<\/li>\n
  • x-real-ip<\/li>\n
  • x-host<\/li>\n
  • x-forwarded-for<\/li>\n
  • x-uri<\/li>\n
  • x-forwarded-proto<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
Topology: <\/b>\u00a0Application server with public IP<\/td>\n<\/tr>\n
Scheme :<\/b><\/p>\n

\"\"<\/a><\/td>\n<\/tr>\n

Supported Headers: <\/b>host<\/td>\n<\/tr>\n
Topology: <\/b>Load balancer with public IP and application servers<\/td>\n<\/tr>\n
Scheme :<\/b><\/p>\n

\"\"<\/a><\/td>\n<\/tr>\n

Supported Headers:<\/b><\/p>\n