Open
Conversation
aram356
force-pushed
the
feat/staging-env-headers
branch
from
9fa7ac6 to
4c5ee04
Compare
…tion Expose FASTLY_SERVICE_VERSION as X-TS-Version on every response, and set X-TS-Env: staging when FASTLY_IS_STAGING=1. This makes it trivial to tell staging from production via curl or browser DevTools. Adds constants for both the Fastly env vars and the header names. Closes #325 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
aram356
force-pushed
the
feat/staging-env-headers
branch
from
4c5ee04 to
89a9e79
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
X-TS-Versionheader (fromFASTLY_SERVICE_VERSION) to every responseX-TS-Env: stagingheader whenFASTLY_IS_STAGING=1constants.rsfor header namescurlor browser DevToolsTest plan
X-TS-Env: stagingheader is presentX-TS-Versionbut noX-TS-Envcurl -sI <url> | grep X-TSCloses #325