HTTP headers can be found in both the HTTP Request and HTTP Response.
The following headers are sent to each Now deployment and can be used to process the request before sending back a response. These headers can be read from the Request object in your Lambda.
This header represents the domain name as it was accessed by the client. If the deployment has been aliased and the client visited the alias URL, it contains the alias instead of the underlying deployment URL.
This header is identical to the
This header represents the protocol of the forwarded server, typically
https in production and
http in development.
This header represents the unique deployment, not the alias. For example,
The following headers are included in Now deployment responses and indicate certain factors of the environment. These headers can be viewed from the Browser's Dev Tools or using an HTTP client such as
curl -I <DEPLOYMENT_URL>.
now: 1. This header can be overridden by other proxies (e.g., Cloudflare).
This header's value indicates whether the response was served from ZEIT's edge cache.
The following values are possible when the content being served is static or uses a
The response was served from the edge.
The response was not found in the edge and so was fetched from an origin server.
The cache was bypassed and so the response was served from an origin server.
The response from the cache is outdated but another visitor has already requested the response and the edge node is processing the revalidation.
The unique identifier for each request.
Contains a list of our data centers through which the request has traversed, usually the data center closest to you.
Custom headers can be added dynamically to the Response object in your Lambda or they can be added statically to the routes property in your