Computer Science · Grade 10

Active learning ideas

HTTP/HTTPS and the World Wide Web

Active learning helps students grasp HTTP/HTTPS because these protocols are invisible in everyday browsing. When students manipulate browser tools, simulate exchanges, and configure servers themselves, they transform abstract concepts into tangible evidence they can analyze and test.

• Ontario Curriculum Expectations
• CS.HS.N.4
• CS.HS.N.5

• 30–50 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Flipped Classroom
• 40 min · Small Groups

Demo Lab: Browser Dev Tools Traffic Inspection

Have students open browser developer tools and visit HTTP and HTTPS sites. They capture network requests, note differences in headers and padlock icons, then discuss encryption indicators. Follow with a class share-out of findings.

Differentiate between HTTP and HTTPS and explain the need for secure protocols.

Facilitation Tip

During the Dev Tools Traffic Inspection, have students pause after each capture to predict what they will see before revealing the packets, reinforcing hypothesis testing.

What to look for

Students will receive cards with scenarios: 'Logging into your bank account,' 'Browsing a news website.' They must write one sentence for each, stating whether HTTP or HTTPS is more appropriate and why, referencing security.

• Understand
• Apply
• Analyze
• Self-Management
• Self-Awareness

Activity 02

• Simulation Game
• 30 min · Pairs

Simulation Game: Client-Server Role Play

Assign roles as clients and servers using printed request/response cards. Clients send HTTP/HTTPS requests; servers reply with mock pages. Groups rotate roles and identify when encryption is needed for secure data.

Analyze the client-server model in the context of web browsing.

Facilitation Tip

In the Client-Server Role Play, assign clear roles and require students to document each step of the request-response cycle in their notebooks.

What to look for

Present students with a diagram of a browser requesting a webpage from a server. Ask them to label the client, server, and the protocol used. Then, ask them to describe one key difference between HTTP and HTTPS in their own words.

• Apply
• Analyze
• Evaluate
• Create
• Social Awareness
• Decision-Making

Activity 03

• Flipped Classroom
• 50 min · Pairs

Hands-On: Local HTTPS Server Setup

Use free tools like Node.js or Python to run a simple server. Students generate self-signed certificates, access via HTTPS, and compare to HTTP versions. Troubleshoot errors to understand protocol requirements.

Explain how web browsers and servers interact to display web pages.

Facilitation Tip

For the Local HTTPS Server Setup, model the certificate generation command first, then circulate to troubleshoot common errors like port conflicts or expired certificates.

What to look for

Facilitate a class discussion: 'Imagine you are developing a new social media app. What protocol would you use for user logins and why? What are the risks if you chose the less secure option?' Encourage students to use vocabulary like encryption and vulnerabilities.

• Understand
• Apply
• Analyze
• Self-Management
• Self-Awareness

Activity 04

• Case Study Analysis
• 35 min · Small Groups

Case Study Analysis: Website Security Audit

Provide site lists; students check for HTTPS, mixed content warnings, and certificate validity using browser tools. Groups compile reports on risks and recommend fixes, presenting to the class.

Differentiate between HTTP and HTTPS and explain the need for secure protocols.

Facilitation Tip

In the Website Security Audit, provide a checklist of items to verify, such as padlock icons, certificate validity dates, and mixed-content warnings.

What to look for

Students will receive cards with scenarios: 'Logging into your bank account,' 'Browsing a news website.' They must write one sentence for each, stating whether HTTP or HTTPS is more appropriate and why, referencing security.

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management

A few notes on teaching this unit

Teachers should avoid assuming students understand the difference between speed and security; instead, let data comparisons guide their conclusions. Emphasize the physical act of inspecting packets and certificates to build credibility. Research shows that hands-on encryption tasks, even with self-signed certificates, help students internalize why HTTPS matters beyond just seeing a green padlock.

By the end of these activities, students should confidently explain the client-server model, compare HTTP and HTTPS packet contents, and justify security choices for real websites. They should also be able to set up a local HTTPS server and identify insecure protocols in live sites.

---

Watch Out for These Misconceptions

• During Demo Lab: Browser Dev Tools Traffic Inspection, watch for students assuming HTTPS improves speed because pages load faster.

  After students inspect HTTP and HTTPS packets side-by-side in Dev Tools, ask them to compare the size and content of each request and response. Guide them to notice that encryption adds overhead but secures data, not speed.

• During Case Study: Website Security Audit, watch for students believing all websites use HTTPS automatically.

  During the audit, provide a mix of HTTP and HTTPS sites, including some deliberately insecure examples. Have groups document which sites lack HTTPS and discuss why older domains might still use HTTP.

• During Simulation: Client-Server Role Play, watch for students thinking communication happens without any rules.

  After the role play, display the sequence of steps on the board and ask students to compare their recorded exchanges to the actual HTTP protocol standards. Highlight how each step follows defined rules.

---

Methods used in this brief

• Flipped Classroom
• Simulation Game
• Case Study Analysis