Match X-Robots-Tag recommendation in Nextcloud docs #370
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.
Pull Request
Description of the change
The latest Nextcloud documentation suggests setting
X-Robots-Tag
tonoindex, nofollow
. This changes the nginx configuration to align with that recommendation.More context: nextcloud/server#37357
Specifically, this explanation: nextcloud/server#37357 (comment)
Benefits
Prior to this change, someone who is following the Nextcloud documentation to set up their instance may set their nginx reverse proxy to add the
X-Robots-Tag: noindex, nofollow
header. Then their Nextcloud instance still generates the following warning even though they followed the documentation:This is because the Helm chart's included nginx instance still adds
X-Robots-Tag: none
.Possible drawbacks
I'm unsure if older Nextcloud installations will then start to complain that the older recommendation of
X-Robots-Tag: none
isn't implemented.Applicable issues
N/A
Additional information
N/A
Checklist
Chart.yaml
according to semver.