New option: defaultExtension #173
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
Zarel
pushed a commit
to Zarel/node-static
that referenced
this pull request
Aug 10, 2021
Zarel
pushed a commit
to Zarel/node-static
that referenced
this pull request
Aug 10, 2021
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.
I've forked you project to create an option to check for default extensions in URLs.
This way, a server can serve html files while allowing "pretty" URLs like
http://example.com/my-html-file.Your vows' tests are updated to test the new resource while maintaining compatibility. Also, I added a Travis file and my test build is at https://travis-ci.org/fmalk/node-static/builds/90381188