[codex] Make asset 404 handling explicit#2
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
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.
What changed
not_found_handling = "404-page"for Pongo.Why
Sentry showed scanner-style transaction paths such as
/spawns.phpand/dccs.php. Live probes already returned 404, so this makes the missing-asset behavior explicit in the source config instead of relying on implicit platform defaults.Impact
Unknown asset/probe paths continue to return 404 and should not fall through to any app-shell behavior. This does not filter Sentry data or hide requests.
Validation
npx wrangler deploy --dry-runprettier --write --ignore-unknown,cargo fmt --check,cargo check --workspace,cargo clippy --workspace -- -D warnings,cargo test --workspace/spawns.phpand/dccs.php