You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a customer whose hired auditors asked us not publish our nginx version in the Server: header of our responses. I think this is a little silly but we want to comply
I don't however want to have to switch to using a custom nginx.conf template just for this.
Its a simple boolean and would easily match the existing implementation pattern on configMap / annotations. If I write a PR for this will it be accepted or is beyond some pale of Feature Creep?
Are there plans to allow injection of simple custom config? or is the feeling that either you take the feature set you are given or you use a custom template?
The text was updated successfully, but these errors were encountered:
We have a customer whose hired auditors asked us not publish our nginx version in the
Server:
header of our responses. I think this is a little silly but we want to complyI don't however want to have to switch to using a custom nginx.conf template just for this.
Its a simple boolean and would easily match the existing implementation pattern on configMap / annotations. If I write a PR for this will it be accepted or is beyond some pale of Feature Creep?
Are there plans to allow injection of simple custom config? or is the feeling that either you take the feature set you are given or you use a custom template?
The text was updated successfully, but these errors were encountered: