Forcing HTTPS Traffic with NGINX

1.25 hours
  • 2 Learning Objectives

About this Hands-on Lab

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

The student is asked to expand the NGINX configuration so that an explicit request to renders the status page. This will require generating a self-signed certificate to use in the SSL configuration.

HTTP Requests for Redirect to HTTPS Equivalent

Requests to port 80 (HTTP) for should redirect to the same URL over HTTPS with a status code of 301 or 302.

Additional Resources

NGINX has been well received by your organization. You've talked your entire organization into utilizing HTTPS for all servers as the default because there isn't a reason not to. You need to modify an existing virtual host configuration to force traffic over HTTPS. The virtual host for is only used internally, so you have decided that a self-signed certificate will do.

What are Hands-on Labs

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.

Sign In
Welcome Back!

Psst…this one if you’ve been moved to ACG!

Get Started
Who’s going to be learning?