HTTP Headers adds a number of HTTP headers to both inbound and outbound messages. We don’t modify or block existing headers on either request or response.

Request headers adds the following HTTP headers in the router to give the application information about the connection. These are stable and may be examined by the application as necessary.

  • X-Forwarded-Proto: The protocol forwarded to the application, for example: http, https.
  • X-Client-IP: The remote IP address of the request.
  • X-Client-SSL: Set “on” only if the client is using SSL connection, otherwise the header isn’t added.
  • X-Original-Route: The route in .platform/routes.yaml which is used currently, for example: https://{default}/.

Response headers adds a number of response headers automatically to assist in debugging connections. These headers should be treated as a semi-private API. Do not code against them, but they may be inspected to help determine how handled the request to aid in debugging.

  • X-Platform-Cache: Either HIT or MISS to indicate if the router in your cluster served the response from its own cache or if the request was passed through to the application.
  • X-Platform-Cluster: The ID of the cluster that received the request. The cluster name is formed from the project ID and environment ID.
  • X-Platform-Processor: The ID of the container that generated the response. The container ID is the cluster ID plus the container name.
  • X-Platform-Router: The ID of the router that served the request. The router ID is the processor ID of the router container, specifically.
  • X-Debug-Info: This is a header added by the edge layer. It doesn’t contain any sensitive information or anything that could be misused. It has no relation to the PHP debugging tool Xdebug.

Custom headers 

Apart from those listed above, your application is responsible for setting its own response headers.

You can also add headers to static files.