Skip to content

[Update] TLS Deployment Best Practices for NGINX #2378

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 28, 2019
Merged

[Update] TLS Deployment Best Practices for NGINX #2378

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions docs/web-servers/nginx/tls-deployment-best-practices-for-nginx/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,6 @@ server {
listen 80;
server_name example.com www.example.com;
return 301 https://example.com$request_uri;
return 301 https://www.example.com$request_uri;
}

server {
Expand All @@ -58,11 +57,11 @@ server {

The [return ](https://nginx.org/en/docs/http/ngx_http_rewrite_module.html#return) directives will be what handles the redirects. Whether to include directives for both `example.com` or `www.example.com`, depends on which domain your certificate was issued for, if not both. (The [NGINX docs](https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/#taxing-rewrites) explain why you should use `return 301` instead of `rewrite`).

2. Reload NGINX:
1. Reload NGINX:

nginx -s reload

3. Go to your site's domain or IP address in a web browser, specifying `http://`. You should be redirected to HTTPS.
2. Go to your site's domain or IP address in a web browser, specifying `http://`. You should be redirected to HTTPS.

## HTTP Strict Transport Security (HSTS)

Expand Down Expand Up @@ -263,7 +262,6 @@ server {
listen [::]:80;
server_name example.com www.example.com;
return 301 https://example.com$request_uri;
return 301 https://www.example.com$request_uri;
}

server {
Expand Down