HTTP compared with HTTPS

Tip: Choose Save as PDF in the print dialog to download. Use A4 paper size.

HTTP compared with HTTPS

Name:
Date:
Class:

Quick Questions

Shade in the A or B circle for each question.

1. Which protocol sends data as readable plain text?
A HTTPS
B HTTP
2. What does HTTPS add to HTTP?
A A faster internet connection
B SSL/TLS encryption
3. A hacker intercepts data sent over HTTPS. What do they see?
A Scrambled data they cannot read
B The password in plain text
4. Which page should definitely use HTTPS?
A A payment page that takes card details
B A page of public opening times
5. What does a digital certificate show about a website?
A The website is genuine
B The website has no adverts

Match the Pairs

Draw a line connecting each item on the left to its match on the right.

Left columnRight column
1http://school-shop.com/login AData is encrypted using SSL/TLS, so intercepted data cannot be read
2https://school-shop.com/login BData is sent as plain readable text, so anyone who intercepts it can read it
3A login or payment page should use the secure protocol so passwords and card numbers are protected CHTTP does not encrypt data. It sends plain text that can be intercepted. A payment page needs HTTPS.
4The security layer that HTTPS adds to HTTP to encrypt the data DSSL/TLS
5Enter card details on http://shop.com/pay because HTTP encrypts the data Ehttps://bank.com/payment
6HTTPS is secure because it sends data as plain text FHTTPS does not send plain text. It encrypts data with SSL/TLS so intercepted data cannot be read.

Definitions

HTTPS

Fill in the Blanks

Complete each line of code by filling in the missing parts.

1.
_____://www.mybank.com/login.html
2.
HTTPS = HTTP + _______
3.
IF page = "payment" THEN use _____
4.
HTTPS site shows a digital ___________
5.
http data is sent as _____ text

Spot the Error

Shade in the letter of the line that contains an error.

Question 1
A url ← "https://shop.com/pay"
B IF url STARTS "https" THEN
C send data as plain text
D ENDIF
Question 2
A url ← "http://bank.com/pay"
B IF url STARTS "https" THEN
C OUTPUT "Padlock shown"
D ENDIF
Question 3
A IF page = "payment" THEN
B protocol ← "HTTP"
C ENDIF
Question 4
A browser requests the page
B server sends its cookie
C IF certificate valid THEN
D OUTPUT "Site is genuine"
Question 5
A hacker INTERCEPTS data
B IF protocol = "HTTPS" THEN
C data is scrambled
D hacker can read it easily
E ENDIF

Answer Key

HTTP compared with HTTPS
Section A: Quick Questions
Q1
B — HTTP
Q2
B — SSL/TLS encryption
Q3
A — Scrambled data they cannot read
Q4
A — A payment page that takes card details
Q5
A — The website is genuine
Section B: Match the Pairs
Q1
http://school-shop.com/login → Data is sent as plain readable text, so anyone who intercepts it can read it
Q2
https://school-shop.com/login → Data is encrypted using SSL/TLS, so intercepted data cannot be read
Q3
A login or payment page should use the secure protocol so passwords and card numbers are protected → https://bank.com/payment
Q4
The security layer that HTTPS adds to HTTP to encrypt the data → SSL/TLS
Q5
Enter card details on http://shop.com/pay because HTTP encrypts the data → HTTP does not encrypt data. It sends plain text that can be intercepted. A payment page needs HTTPS.
Q6
HTTPS is secure because it sends data as plain text → HTTPS does not send plain text. It encrypts data with SSL/TLS so intercepted data cannot be read.
Section C: Definitions
Q1
HTTPS — HTTP plus SSL/TLS encryption. Plain HTTP sends readable text that can be intercepted; HTTPS scrambles data so intercepted data can't be read, and a certificate shows the site is genuine.
Section D: Fill in the Blanks
Q1
https://www.mybank.com/login.html
Q2
HTTPS = HTTP + SSL/TLS
Q3
IF page = "payment" THEN use HTTPS
Q4
HTTPS site shows a digital certificate
Q5
http data is sent as plain text
Section E: Spot the Error
Q1
C — An HTTPS address means SSL/TLS is used, so the data is encrypted. Line 3 should be 'encrypt data with SSL/TLS', not send it as plain text.
Q2
A — A payment page must use HTTPS so the card details are encrypted and the padlock shows. The URL should start with https://, not http://.
Q3
B — Payment and login pages need HTTPS so that the data is encrypted. The protocol should be "HTTPS", because plain HTTP is not secure.
Q4
B — The server proves it is genuine by sending its digital certificate. A cookie does not prove the site is genuine, so line 2 should say 'certificate'.
Q5
D — With HTTPS the data is encrypted, so an intercepted copy is scrambled and cannot be read. Line 4 should say the hacker cannot read it.