gaja-group
/
server-configs-nginx
mirror of https://github.com/h5bp/server-configs-nginx
2
0
Fork 0
Code Issues Releases Wiki Activity
server-configs-nginx/sites-available
History
Philipp Becker fdee2c257c 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
 		2014-11-10 03:04:31 +01:00
..
README.md Typo foorbar -> foobar 2013-11-18 03:41:11 -05:00
example.com IPv6 only is the default 2014-08-21 00:31:37 +01:00
no-default add a doc block to no-default 2013-11-20 20:40:02 +00:00
ssl.example.com Remove include directive in ssl.example.com 2014-11-10 03:04:31 +01:00

README.md

Sites Available

Define host definitions here. It'd be a good thing if you keep your hosts indexed by domain name, eg:

example.com (handles traffic from both www.example.com and example.com)
foobar.com (as above)
test.foobar.com (handles traffic from both www.test.foobar.com and test.foobar.com)