From fdee2c257c4e72a82505e46085a681d4746f1a58 Mon Sep 17 00:00:00 2001 From: Philipp Becker Date: Mon, 10 Nov 2014 03:04:31 +0100 Subject: [PATCH] Remove include directive in ssl.example.com To include the SSL related directives in the port 80 server block seems to be redundant. Because we are redirecting explicit all incoming traffic via port 80 to the HTTPS host on port 443 where only the *secure-connection-magic* is happen. Maybe I am missing something, but I tested the configuration under the following system and encountered no negative side effects: **Server** * Ubuntu 14.04 LTS * Nginx 1.7.7 mainline **Client** * OS X 10.9.5 * Browser: FF 33, Chrome 38, Safari 7 --- sites-available/ssl.example.com | 2 -- 1 file changed, 2 deletions(-) diff --git a/sites-available/ssl.example.com b/sites-available/ssl.example.com index 04c4466..4c90084 100644 --- a/sites-available/ssl.example.com +++ b/sites-available/ssl.example.com @@ -8,8 +8,6 @@ server { # listen on both hosts server_name example.com www.example.com; - include h5bp/directive-only/ssl.conf; - # and redirect to the https host (declared below) # avoiding http://www -> https://www -> https:// chain. return 301 https://example.com$request_uri;