![]() VE0: The last section, VE or "varnish end," represents the sum of the length of the trip.VS0: The next section, VS or "varnish start," represents the start of the varnish part of the request's journey and will always be 0.S1557441707.643683: The first section of the header (starting with S) represents a Unix timestamp of the start of the request on our edges.The above header can be broken down into three parts, each separated by commas: The X-Timer header provides the timing information about the journey of a request from end to end. The X-Runtime HTTP response header provides the time (in milliseconds) an application takes to process a request. The X-Cache-Hits reflects that same “MISS, HIT” information in numeric format as 0, 1. For more details, refer Understanding cache HIT and MISS headers with shielded services. The X-Cache: MISS, HIT indicates that the requested object was not in the shield cache (a MISS) but was in the local delivering node (a HIT). Two cache-nodes in X-Served-By show that shielding is turned on, with cache-lax8631-LAX serving as the delivering cache node at the shield datacenter and cache-bur17525-BUR serving as the delivering cache node at the "local" datacenter. Let’s understand what the above HTTP Header means: Here’s what an HTTP response body looks like: < x-served-by: cache-lax8631-LAX, cache-bur17525-BUR An HTTP header consists of its case-insensitive name followed by a colon (:), then by its value. HTTP headers let the client and the server pass additional information with an HTTP request or response. ![]() Note: Only the stack owners, developers, and admin can create delivery tokens. At the bottom of the resulting page, you will see the API Key and Delivery Token of your stack.Īdditional Resource: Read more about how you can create a new delivery token.From the list of existing delivery tokens, click on the Delivery Token that applies to the publishing environment of your choice.Navigate to Settings > Tokens > Delivery Tokens.To retrieve the stack API key and the delivery token of a specific publishing environment of your stack, perform the steps given below after logging into your Contentstack account: We strongly recommend that you use Delivery Tokens for fetching published content via the Content Delivery API and Management Tokens for fetching draft content via the Content Management API. Note: We have deprecated the usage of Access Tokens for all stacks. Users will not be able to use authentication parameters such as api_key (Stack API key), access_token (access token of the stack), authtoken (user generated authtoken), and authorization (management token of the stack) as query parameters for any stack-specific API requests.To make authorized CDA requests, use the value of the delivery token against the access_token key. Users will not be able to use Access Tokens to run Content Delivery API (CDA) requests.you need to pass the value of the delivery token against the access_token key.įor stacks that are part of organizations created after June 24, 2020: ![]() Note: The nomenclature for the use of delivery tokens in CDA requests will remain the same, i.e. While Content Delivery API requests may work with Access Token (instead of Delivery Token), we strongly recommend that you not use it, since we have already deprecated Access Token for new stacks. The Delivery Token is a read-only credential that you can create for different environments of your stack. The API Key is a unique key assigned to each stack.
0 Comments
Leave a Reply. |