Computer Science · Class 12

Active learning ideas

Application Layer Protocols: HTTP, HTTPS, FTP

Active learning works well for this topic because students need to see protocols in action to understand their purpose and limits. When they capture packets or role-play transfers, abstract ideas like encryption and ports become concrete, helping them spot real-world security gaps that textbooks often miss.

• CBSE Learning Outcomes
• CBSE: Computer Networks - Network Protocols - Class 12

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

Activity 01

• Simulation Game
• 40 min · Small Groups

Packet Capture Lab: HTTP vs HTTPS

Install Wireshark on school computers. Have students visit http://example.com and https://example.com sites, capture packets, and compare plaintext headers to encrypted payloads. Groups note port differences and discuss eavesdropping risks in a shared report.

Explain the function of HTTP and how HTTPS enhances its security.

Facilitation Tip

During Packet Capture Lab, remind students to clear browser caches before capturing HTTPS traffic to get clean, decrypted packets for analysis.

What to look for

Present students with scenarios: 'A user is logging into their bank account.' or 'A user is downloading a public software manual.' Ask them to identify which protocol (HTTP, HTTPS, FTP) is most appropriate and why, citing security considerations.

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

Activity 02

• Role Play
• 30 min · Pairs

Role Play: Client-Server FTP Transfer

Assign roles as FTP client and server. Clients issue commands like USER, PASS, RETR on paper scripts; servers respond with status codes. Switch roles, then analyse why credentials appear in cleartext and suggest secure fixes.

Compare HTTP and FTP in terms of their primary use cases and security implications.

Facilitation Tip

In Role Play: Client-Server FTP Transfer, assign clear roles like 'Bank Clerk' and 'Customer' to make the plaintext credential exposure tangible.

What to look for

Pose the question: 'Imagine the internet without DNS. How would you access your favourite website if you only knew its IP address?' Facilitate a discussion on the role of DNS and its dependency on application layer protocols for actual content delivery.

• Apply
• Analyze
• Evaluate
• Social Awareness
• Self-Awareness

Activity 03

• Jigsaw
• 45 min · Small Groups

Jigsaw: HTTP, HTTPS, FTP

Divide class into expert groups for one protocol, researching ports, security, and uses. Experts teach home groups via posters, then complete a class comparison matrix collaboratively.

Predict the consequences of a global DNS failure on internet accessibility.

Facilitation Tip

For Protocol Comparison Jigsaw, group students by protocol first, then mix groups so each new team gets a quick expert summary before comparing features.

What to look for

Ask students to write down one key difference between HTTP and HTTPS, and one key difference between HTTP and FTP, focusing on their primary use and security aspects.

• Understand
• Analyze
• Evaluate
• Relationship Skills
• Self-Management

Activity 04

• Simulation Game
• 35 min · Pairs

Command Line Demo: FTP Operations

Use school lab terminals to connect to ftp sites with ftp command. Upload/download test files, observe active/passive modes. Log sessions and debate FTPS upgrades for security.

Explain the function of HTTP and how HTTPS enhances its security.

Facilitation Tip

During Command Line Demo, ask students to predict commands like 'ls' or 'get' before typing to connect prior knowledge to new CLI actions.

What to look for

Present students with scenarios: 'A user is logging into their bank account.' or 'A user is downloading a public software manual.' Ask them to identify which protocol (HTTP, HTTPS, FTP) is most appropriate and why, citing security considerations.

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

A few notes on teaching this unit

Teach this topic by moving from simulation to reality. Start with role plays to build intuition, then use packet captures to show what actually happens on the wire. Avoid diving straight into port numbers or TLS handshakes without context, as students retain concepts better when they see problems first. Research shows hands-on labs improve retention of security concepts by nearly 40% compared to lectures alone.

By the end of these activities, students should confidently compare HTTP, HTTPS, and FTP, explain their ports and security traits, and choose appropriate protocols for given tasks. They should also recognise that security depends on layers, not just one protocol.

---

Watch Out for These Misconceptions

• During Packet Capture Lab, watch for students assuming HTTPS makes all data safe forever.

  Have students note how data remains encrypted only during transit; once decrypted on the server, it is as vulnerable as HTTP data. Ask them to trace where data goes after decryption to highlight server-side risks.

• During Role Play: Client-Server FTP Transfer, listen for claims that FTP is secure because it is designed for files.

  Use the role-play to show plaintext credentials and files being captured. Then, ask students to switch to SFTP in the same demo to see how encryption changes the outcome.

• During Protocol Comparison Jigsaw, watch for students conflating all ports with port 80.

  Have groups build a chart with port numbers and protocols. Then, simulate a 'wrong port' scenario where a student tries to use port 80 for FTP and observe the failure to reinforce port-specific roles.

---

Methods used in this brief

• Simulation Game
• Role Play
• Jigsaw