Repository navigation
nginx: unknown paths answer 404 at the edge; static assets are served directly - #3302
Merged
Merged
Conversation
… directly Keep the existing API and page routes on their selected backends. Send known assets and public documents directly to the file-server, preserving their bytes, cache headers and compression. Return the file-server-compatible error body locally for unmatched paths. Keep the application catch-all registered while page routes still use it. Cover route selection, static files, error bodies and the absence of unknown requests in the application log. Verify reloads with concurrent participation traffic and save both rendered route selections. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ss9NfEMZS9Qm4FZ2npXDrx
Contributor
Delphi Coverage Report
|
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.
Keep the existing API and page routes on their selected backends. Send known
assets and public documents directly to the file-server, preserving their
bytes, cache headers and compression.
Return the file-server-compatible error body locally for unmatched paths.
Keep the application catch-all registered while page routes still use it.
Cover route selection, static files, error bodies and the absence of unknown
requests in the application log. Verify reloads with concurrent participation
traffic and save both rendered route selections.
Path families and their destinations after the change are listed in the private evidence; nothing live changes destination. Rehearsed on a box with the nginx and file-server images: unknown paths answer 404 at nginx without reaching Node; every kept static, API and page route still routes as before; 10 reload groups green.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Ss9NfEMZS9Qm4FZ2npXDrx