Closed mcujba closed 2 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
A human has marked this issue as invalid, this likely happened because the issue template was not used in the creation of the issue.
While this bug report is not properly filled, you are free to edit the nginx configuration to see fit, it is stored in persistent storage.
yes, I could do that. But I think it should already be in the registry image. It's a case of security.
While the security aspect is present, we purposely follow the default config provided by Alpine https://git.alpinelinux.org/aports/tree/main/nginx/nginx.conf?h=3.20-stable, which again builds on the default Nginx config.
If this image was built to be directly exposed to the internet, it would have a hardened default, but as with any of our nginx based image (excluding SWAG), this is not built to be directly exposed to the internet, but rather be behind a reverse proxy(in which you can strip both the server and x-powered-by header).
Shipping this change by default is out of scope of this image.
Is there an existing issue for this?
Current Behavior
x-powered-by expose php version.
Expected Behavior
Base a security recommendation this header nee to be removed
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs