-
Notifications
You must be signed in to change notification settings - Fork 344
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
https: T6734: disable software version reporting #4282
Conversation
👍 |
CI integration ❌ failed! Details
|
@@ -18,6 +18,8 @@ server { | |||
listen [::]:{{ port }} ssl; | |||
{% endif %} | |||
|
|||
server_tokens {{ 'on' if server_version_id is vyos_defined and server_version_id == 'enable' else 'off' }}; |
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.
With default disabled I actually ment this ;)
server_tokens {{ 'on' if server_version_id is vyos_defined and server_version_id == 'enable' else 'off' }}; | |
server_tokens 'off'; |
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.
Default is off in my submission. What does it hurt to change the default behavior to off (as you prefer), but allow it to be enabled if the user wants it?
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.
We do not use bool yes|no, disable|enable, true|false
, and so on
- I also prefer to disable the version as in the suggested change.
Change summary
Types of changes
Related Task(s)
Related PR(s)
How to test / Smoketest result
When disabled (default state), server_tokens in nginx are off, HTTP response headers appear like this
When enabled, server_tokens in nginx are on, HTTP response headers appear like this
Checklist: