HTTP and HTTPS protocols in Intro to Computing - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does HTTP stand for?

HTTP stands for HyperText Transfer Protocol. It is the basic protocol used to transfer web pages on the internet.

beginner

What is the main difference between HTTP and HTTPS?

HTTPS is HTTP with encryption. It uses SSL/TLS to secure data between your browser and the website, protecting it from eavesdropping.

beginner

Why is HTTPS important when entering passwords on websites?

HTTPS encrypts the data you send, like passwords, so hackers cannot easily read it if they intercept the connection. This keeps your information safe.

intermediate

What port numbers do HTTP and HTTPS typically use?

HTTP usually uses port <strong>80</strong>, while HTTPS uses port <strong>443</strong>. Ports are like doors that let data in and out of your computer.

beginner

Explain in simple terms how HTTPS protects your data using a real-world analogy.

Think of HTTP as sending a postcard anyone can read. HTTPS is like sending a locked box that only you and the receiver have the key to open, keeping the message private.

Which protocol encrypts data to keep it secure?

A FTP

B HTTP

C HTTPS

D SMTP

HTTPS encrypts data using SSL/TLS, while HTTP does not.

What port does HTTPS usually use?

A 443

B 21

C 80

D 25

HTTPS typically uses port 443 for secure communication.

What does HTTP stand for?

A Hyper Transfer Text Protocol

B HyperText Transfer Protocol

C Hyperlink Text Transfer Protocol

D HyperText Transmission Process

HTTP stands for HyperText Transfer Protocol.

Which of these is NOT a feature of HTTPS?

A Faster loading than HTTP

B Data integrity

C Data encryption

D Authentication of website

HTTPS does not necessarily load faster than HTTP; its main features are encryption, integrity, and authentication.

If a website URL starts with 'http://', what does it mean?

A The connection is secure

B The website uses FTP

C The website is offline

D The connection is not encrypted

URLs starting with 'http://' do not use encryption, so the connection is not secure.

Describe the difference between HTTP and HTTPS and why HTTPS is important for online security.

Think about how data travels and what risks exist without encryption.

Explain the role of port numbers in HTTP and HTTPS communication using a simple analogy.

Imagine your computer as a house with many doors.

Practice

1. What is the main difference between HTTP and HTTPS?

easy

A. HTTPS encrypts data while HTTP does not

B. HTTP encrypts data while HTTPS does not

C. HTTP is faster because it uses encryption

D. HTTPS is only used for email communication

Solution

1. Step 1: Understand HTTP basics

   HTTP is a protocol used for communication between browsers and websites without encryption.

2. Step 2: Understand HTTPS security

   HTTPS adds encryption to protect data during transmission, making it secure.

3. Final Answer:

   HTTPS encrypts data while HTTP does not -> Option A

4. Quick Check:

   Encryption = HTTPS [OK]

Hint: HTTPS means secure, HTTP does not [OK]

Common Mistakes:

• Confusing which protocol encrypts data
• Thinking HTTP is secure by default
• Believing HTTPS is only for emails

2. Which of the following is the correct way to write a URL using HTTPS?

easy

A. http://www.example.com

B. htpps://www.example.com

C. htp://www.example.com

D. https://www.example.com

Solution

1. Step 1: Identify correct HTTPS syntax

   The correct prefix for secure websites is https:// with 'https' fully spelled and followed by '://'.

2. Step 2: Check each option

   https://www.example.com matches the correct syntax exactly; others have typos or use HTTP.

3. Final Answer:

   https://www.example.com -> Option D

4. Quick Check:

   Correct HTTPS URL = https://www.example.com [OK]

Hint: HTTPS URLs start with 'https://' exactly [OK]

Common Mistakes:

• Typing 'htp' or 'htpps' instead of 'https'
• Using 'http' instead of 'https' for secure sites
• Missing the '://' after the protocol

3. Consider this simplified flowchart of a browser requesting a webpage:



If the protocol is HTTPS, what extra step happens during the 'Browser sends request' phase?

medium

A. The browser encrypts the request before sending

B. The browser sends the request without encryption

C. The browser skips sending the request

D. The browser sends the request twice

Solution

1. Step 1: Analyze HTTPS request process

   HTTPS requires encrypting data before sending it to protect privacy.

2. Step 2: Compare options with HTTPS behavior

   Only The browser encrypts the request before sending describes encryption before sending, which matches HTTPS protocol.

3. Final Answer:

   The browser encrypts the request before sending -> Option A

4. Quick Check:

   Encryption before sending = The browser encrypts the request before sending [OK]

Hint: HTTPS encrypts data before sending [OK]

Common Mistakes:

• Thinking HTTPS sends data unencrypted
• Assuming browser sends request twice
• Believing browser skips sending request

4. A developer wrote this code snippet to fetch a webpage securely:

fetch('http://secure-site.com/data')

What is the main problem here?

medium

A. The URL is missing a domain extension

B. The fetch function is misspelled

C. The URL uses HTTP instead of HTTPS

D. The code is missing a semicolon

Solution

1. Step 1: Check URL protocol

   The URL uses http:// which is not secure for sensitive data.

2. Step 2: Identify correct secure protocol

   To fetch data securely, the URL should start with https://.

3. Final Answer:

   The URL uses HTTP instead of HTTPS -> Option C

4. Quick Check:

   Secure fetch needs HTTPS URL [OK]

Hint: Secure fetch requires HTTPS URL [OK]

Common Mistakes:

• Ignoring the protocol difference
• Thinking semicolon is mandatory in JavaScript fetch
• Assuming fetch is misspelled

5. You want to ensure a website always uses HTTPS even if a user types HTTP. Which method should you use?

hard

A. Disable HTTP protocol on the user's browser

B. Set up a redirect from HTTP to HTTPS on the server

C. Use HTTP for all pages and HTTPS only for login

D. Ask users to manually type HTTPS every time

Solution

1. Step 1: Understand how to enforce HTTPS

   Redirecting HTTP requests to HTTPS ensures all traffic is secure automatically.

2. Step 2: Evaluate other options

   Disabling HTTP on user browsers or manual typing is impractical; partial HTTPS use is insecure.

3. Final Answer:

   Set up a redirect from HTTP to HTTPS on the server -> Option B

4. Quick Check:

   Redirect HTTP to HTTPS = Set up a redirect from HTTP to HTTPS on the server [OK]

Hint: Use server redirect to force HTTPS [OK]

Common Mistakes:

• Thinking users must type HTTPS manually
• Believing disabling HTTP on browsers is feasible
• Using HTTP for some pages weakens security