fix: handle missing trailing slash on directories #113
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.
Currently, when fastify-static is configured with
redirectoption set tofalseand a request for a directory does not contain a trailing slash, it causes the server to hang. This is because we only register a directory handler on the underlyingsendstream ifredirectoption istrue.This PR updates the library to handle such requests by calling
reply.callNotFound(). We presume that requesting a directory without using a trailing slash OR settingredirecttotrueshould be handled explicitly as a 404.To reproduce the bug:
In another terminal, running the following command will hang indefinitely:
Checklist
npm run testandnpm run benchmark