-
-
Notifications
You must be signed in to change notification settings - Fork 758
Added web security headers for nginx configuration #5183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 2 commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
25cdd36
Added web security headers for nginx configuration
ashwini-orchestral 594dd57
Removed unwanted server-tokens from config
ashwini-orchestral 4862435
Added server_tokens in server and removed server_tokens from other pl…
ashwini-orchestral 645db4e
Remove support for TLS v1.0 and v1.1.
Kami a8151bc
Removed Cache-control header as per review comment
ashwini-orchestral 983f7f8
Merge branch 'nginx-conf' of https://github.com/ashwini-orchestral/st…
ashwini-orchestral 410592b
Merge branch 'master' of github.com:StackStorm/st2 into nginx-conf
Kami 1e73251
Add changelog entry for nginx.conf TLS v1.2 change.
Kami ce0e767
Modified Changelog entry
ashwini-orchestral 6638f22
Update CHANGELOG.rst
Kami a936c2d
Merge branch 'master' into nginx-conf
Kami b092524
Update CHANGELOG.rst
Kami File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While the security-focused headers are all good, I'm wondering what would be the user impact for the Cache-Control changes here and totally disabling the caching? @ashwini-orchestral what are the specific reasons behind hardening cache-control this way?
WDYT @StackStorm/maintainers @StackStorm/contributors? Any downsides, any behavior/UX changes you could think of?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, +1, I don't see much benefit security wise from cache control headers, it would just slow things down if we need to re-fetch all the static resources on each page (re)load...
But others (iframe, stric transport security, etc.) are indeed a good idea 👍
On that note, I believe we need to sync up multiple places (if they don't contain those headers already) - Docker, installer, etc. Or do those places use config from this repo?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, we're pulling in all the places nginx config from the
st2
repo (this file).I think only Puppet is different with the templating @nmaludy ? I guess you'll need to update that