- Lab
- Cloud
Forcing HTTPS Traffic with NGINX
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.
Path Info
Table of Contents
-
Challenge
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.
-
Challenge
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.
What's a lab?
Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.
Provided environment for hands-on practice
We will provide the credentials and environment necessary for you to practice right within your browser.
Guided walkthrough
Follow along with the author’s guided walkthrough and build something new in your provided environment!
Did you know?
On average, you retain 75% more of your learning if you get time for practice.