Update nginx + Apache configuration files to prevent access to internal files #251
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
SimonFrings
approved these changes
Mar 5, 2024
Contributor
SimonFrings
left a comment
SimonFrings
left a comment
There was a problem hiding this comment.
Looks good, let's get this in 👍
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 changeset updates the nginx + Apache configuration files to prevent access to internal files. Note that these configuration files are meant to be a generic starting point and are subject to change for more specific application requirements (YMMV). Our configuration files are fully tested against our integration test suite.
Builds on top of #250, #60, #59, #3 and others
Resolves / closes #195
Supersedes / closes #197, thank you @virtuelle-maschine for the suggestion!