Skip to Content
Last modified by Alexandru Pentilescu on 2023/06/25 18:53
From version 4.1
edited by Alexandru Pentilescu
on 2022/06/11 21:21
Change comment: There is no comment for this version
To version 6.1
edited by Alexandru Pentilescu
on 2022/06/11 21:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -141,4 +141,6 @@
141 141  Time to get into the groove of things!
142 142  First, we shall create a new configuration file in "/etc/nginx/sites-available" and then a symbolic link towards it in "/etc/nginx/sites-enabled" called "fallback.conf". Why?
143 143  Well, basically, we want for any HTTP request to our website, either to "pentilescu.com" or to any subdomain of "pentilescu.com" to redirect that request to the exact same destination but using the HTTPS protocol, instead.
144 -This is considered good practice, because, you're eseentially redirecting the browser to use a more secured version of that page.
144 +This is considered good practice, because, you're eseentially redirecting the browser to use a more secured connection protocol. Not only will this ensure that any login credentials are protected from being stolen, but also that the exact resources being retrieved from our server are obfuscated, so that our visitors can browse our server privately.
145 +
146 +The contents of this "fallback.conf" file are as follows: