Don't serve index.html as a site index #100
Merged
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.
This switch prevents the static files from serving
index.html
as an index. This means you can still have aindex.html
file in your static path and it won't get served up as the application index. Fixes #99.From the ExpressJS documentation: http://expressjs.com/en/api.html#express.static
However, if the browser is navigated to (for example)
http://localhost:9001/index.html
then it will serve theindex.html
from the static path. This does not conflict with the application though as there is no applicationindex.html
file to serve anyway.Another fix was to move the:
above the
if (program.staticDir) { ... }
call, but I believe this PR solves the problem more correctly.