Resolve "NGINX settings: clarify the use of HSTS"
What does this MR do?
Explain what's used to "tell browsers and clients to only communicate with your GitLab instance over a secure connection for the next 24 months" and how to reconfigure this, if necessary.
Related issues
Closes #5953 (closed)
Author's checklist (required)
-
Follow the Documentation Guidelines and Style Guide. - If you have
developeraccess or higher (for example, GitLab team members or Core Team members)-
Apply the documentation label, plus: -
Assign the designated Technical Writer.
-
Review checklist
All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.
1. Primary Reviewer
-
Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.
2. Technical Writer
-
Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage. -
Ensure Technical Writing, documentation, and a docs::scoped label are added. -
Add docs-only when the only files changed are under doc/*. -
Add twdoing when starting work on the MR. -
Add twfinished if Technical Writing team work on the MR is complete but it remains open.
-
3. Maintainer
-
Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set. -
If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by Niklas Janz