HTTP compared with 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.
Understanding HTTP compared with HTTPS in IGCSE Computer Science Paper 1
What it does: Pages that handle sensitive data need HTTPS so the data is encrypted when it travels across the internet. HTTP does not encrypt data, so anyone who intercepts it can read it. HTTPS encrypts it first. A digital certificate is used with HTTPS to show the site is who it says it is, not a fake copy. SSL/TLS is the security layer that encrypts the data. Cookies are a separate topic. The https:// protocol adds SSL/TLS encryption, so any intercepted data is scrambled and unreadable.
Common mistakes: 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. A payment page must use HTTPS so the card details are encrypted and the padlock shows. The URL should start with https://, not http://.
Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.
This module's key terms are also in a printable crossword (Modules 464–476) and word search (Modules 464–489).
Take this worksheet further — free with Cloodit
Each concept is reinforced from every angle — learned, then applied, then tested.
Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.
Over 100 of them, across seven natural biomes.
Turns their work into revision material ready for Flash Cards and Exam study.
Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.
Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.
Quick Questions
Match the Pairs
Key Term
HTTPSFill in the Blanks
Spot the Error
Student with a class code? Join your class →