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.
Request to disable
php_expose
. Because when enabled it discloses information about the system that could indicate vulnerabilities or help malicious individuals otherwise.php_expose
is a core INI directive, hence it can only be configured in the primary php.ini.The main reason for myself is that several penetration testing tools indicate it as a (low) security risk. E.g.:
Tradeoff: I am proud to be hosting my app at Azure which means I can leave the security patching to the people who like it, are good at it and make it their responsibility. Bu now there is no longer a header on the HTTP responses showing off my app's high PHP version.