Add /qa-block Netlify function for Prerender 403<->200 toggle testing - #7
Merged
Conversation
Mirrors the qa-status.ts pattern but toggles between 403 Forbidden
and 200 OK (instead of 500/200) via the build-time env var
QA_FORCE_403:
QA_FORCE_403="true" -> HTTP 403 + text/html minimal body
(<title>QA Block Test</title>,
<h1>403 Forbidden</h1>)
anything else/unset -> HTTP 200 + text/html minimal body
(<title>QA Block Test</title>,
<h1>QA Block Test</h1>)
Same handler signature, env-read pattern, and Response shape as
qa-status.ts. Kept as its own function (not folded into qa-code.ts)
because the env-driven toggle does not fit the generic fixed-status
dispatcher — same reasoning as qa-status.ts.
QA_FORCE_403 is captured at deploy time (process.env), so flipping it
in the Netlify UI requires a redeploy (push to main, or Netlify UI ->
Deploys -> Trigger deploy).
- netlify/functions/qa-block.ts: new function.
- netlify.toml: add /qa-block -> /.netlify/functions/qa-block rewrite
with status = 200 (rewrite TYPE, preserves upstream 200/403 +
Content-Type). Placed immediately after the existing /qa-status
block (grouping the two env-toggled endpoints) and before the SPA
/* catch-all. qa-status.ts, qa-code.ts, and all other rewrites are
untouched.
No app routes, pages, or dependencies changed.
Co-authored-by: Cursor <cursoragent@cursor.com>
✅ Deploy Preview for weirdanimals ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Mirrors the qa-status.ts pattern but toggles between 403 Forbidden and 200 OK (instead of 500/200) via the build-time env var QA_FORCE_403:
QA_FORCE_403="true" -> HTTP 403 + text/html minimal body
(<title>QA Block Test</title>,
403 Forbidden
)anything else/unset -> HTTP 200 + text/html minimal body
(<title>QA Block Test</title>,
QA Block Test
)Same handler signature, env-read pattern, and Response shape as qa-status.ts. Kept as its own function (not folded into qa-code.ts) because the env-driven toggle does not fit the generic fixed-status dispatcher — same reasoning as qa-status.ts.
QA_FORCE_403 is captured at deploy time (process.env), so flipping it in the Netlify UI requires a redeploy (push to main, or Netlify UI -> Deploys -> Trigger deploy).
No app routes, pages, or dependencies changed.