Repository navigation
Make the Express quickstart keyless, observable and testable - #68
Merged
Merged
Conversation
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
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.
The basic Express example currently requires an API key, refers to a missing
.env.example, disables TLS validation during development, and suggests that changing a User-Agent should block traffic. That no longer demonstrates the default monitor-mode workflow accurately.Replace it with a loopback-only, keyless local tripwire demo. Ordinary traffic returns 200; a controlled decoy route returns its own 404 while the decision records DENY. Explicitly choosing enforce mode stops that route with 403. Keep health, data and JSON-submit examples, and separate local verdicts from cloud reporting.
Add real HTTP checks for ordinary traffic in both modes, monitor-mode route execution, enforced refusal, health bypass and JSON submission. Remove obsolete setup and fingerprinting claims.
Validation: all four HTTP tests and TypeScript build passed in an isolated install using the published @webdecoy/express and @webdecoy/node 0.21.0 packages. No production requests, account credentials or cloud reporting used.