With benefits including security, improved performance, and better search engine positioning, there’s no reason to not be serving *all* web traffic over HTTPS. In this activity, the student will take an existing NGINX virtual host that only handles traffic over HTTP and configure it to handle HTTPS traffic (using a self-signed certificate) and redirect HTTP traffic to HTTPS.
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Accept HTTPS Requests for status.example.com
The student is asked to expand the NGINX configuration so that an explicit request to https://status.example.com renders the status page. This will require generating a self-signed certificate to use in the SSL configuration.
- HTTP Requests for status.example.com Redirect to HTTPS Equivalent
Requests to port 80 (HTTP) for status.example.com should redirect to the same URL over HTTPS with a status code of 301 or 302.
