HTTP and HTTPS in Computer Networks - Time & Space Complexity

Time Complexity: HTTP and HTTPS

O(n)

Understanding Time Complexity

When we use HTTP or HTTPS, our devices send and receive data over the internet. Understanding how the time it takes to complete these exchanges grows as the amount of data or number of requests increases helps us see how fast or slow web communication can be.

We want to know: How does the time to load a webpage or send data change when more information or more users are involved?

Scenario Under Consideration

Analyze the time complexity of the following simplified HTTP request process.

function sendHttpRequest(url, isHttps) {
  establishConnection(url);       // Open connection to server
  if (isHttps) {
    performTlsHandshake();        // Secure connection setup
  }
  sendRequestHeaders();           // Send headers
  receiveResponse();              // Get data from server
  closeConnection();              // Close connection
}
    

This code shows the steps a device takes to send an HTTP or HTTPS request and get a response.

Identify Repeating Operations

Look for parts that repeat or take time depending on input size.

• Primary operation: Receiving the response data from the server.
• How many times: This depends on the size of the data sent back; larger data means more time receiving.

How Execution Grows With Input

As the amount of data from the server grows, the time to receive it grows roughly in direct proportion.

Input Size (data in KB)	Approx. Operations (time units)
10	10 units
100	100 units
1000	1000 units

Pattern observation: The time to receive data grows linearly with the size of the data. More data means more time.

Final Time Complexity

Time Complexity: O(n)

This means the time to complete the request grows in direct proportion to the amount of data received.

Common Mistake

[X] Wrong: "HTTPS always takes twice as long as HTTP because of encryption overhead."

[OK] Correct: While HTTPS adds extra steps for security, the main time depends on data size. For small data, the difference is small; for large data, receiving data dominates time.

Interview Connect

Understanding how data size affects request time helps you explain real-world web performance. This skill shows you can think about how network steps impact user experience.

Self-Check

"What if the connection used HTTP/2 with multiplexing? How would the time complexity change when sending multiple requests?"

Practice

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

easy

A. HTTPS encrypts data, HTTP does not

B. HTTP encrypts data, HTTPS does not

C. HTTP is faster than HTTPS

D. HTTPS uses a different port than HTTP but no encryption

Solution

1. Step 1: Understand HTTP basics

   HTTP is a protocol used to load websites but it sends data in plain text.

2. Step 2: Understand HTTPS security

   HTTPS adds encryption to protect data from being read by others during transmission.

3. Final Answer:

   HTTPS encrypts data, HTTP does not -> Option A

4. Quick Check:

   Encryption = HTTPS [OK]

Hint: HTTPS means secure by encrypting data [OK]

Common Mistakes:

• Thinking HTTP encrypts data
• Believing HTTPS is slower without reason
• Confusing port difference as main feature

2. Which URL prefix indicates a secure website connection?

easy

A. https://

B. ftp://

C. http://

D. file://

Solution

1. Step 1: Identify URL prefixes

   Common URL prefixes include http:// for normal sites and https:// for secure sites.

2. Step 2: Match secure prefix

   HTTPS means the connection is encrypted and secure.

3. Final Answer:

   https:// -> Option A

4. Quick Check:

   Secure URL = https:// [OK]

Hint: Look for 'https://' to know site is secure [OK]

Common Mistakes:

• Choosing http:// as secure
• Confusing ftp:// with secure web protocol
• Not recognizing https:// as secure

3. What will happen if you try to access a website with https:// but the server only supports http://?

medium

A. The browser will automatically switch to http:// and load the site

B. The browser will show a security warning or error

C. The website will load but without encryption

D. The connection will be blocked by the internet provider

Solution

1. Step 1: Understand HTTPS requirement

   HTTPS requires the server to support encryption with a valid certificate.

2. Step 2: Browser behavior on unsupported HTTPS

   If the server does not support HTTPS, the browser cannot establish a secure connection and will warn the user.

3. Final Answer:

   The browser will show a security warning or error -> Option B

4. Quick Check:

   Unsupported HTTPS = Warning [OK]

Hint: No HTTPS support means browser warns user [OK]

Common Mistakes:

• Assuming browser silently switches to HTTP
• Thinking site loads without encryption anyway
• Believing ISP blocks connection

4. A user reports that their browser shows a "Not Secure" message on a website using https://. What is the most likely cause?

medium

A. The browser does not support HTTPS

B. The website is using HTTP instead of HTTPS

C. The user's internet connection is slow

D. The website's SSL certificate is expired or invalid

Solution

1. Step 1: Understand HTTPS and SSL certificates

   HTTPS requires a valid SSL certificate to prove the site's identity and encrypt data.

2. Step 2: Identify cause of "Not Secure" message

   If the certificate is expired, invalid, or missing, browsers warn users even if URL starts with https://.

3. Final Answer:

   The website's SSL certificate is expired or invalid -> Option D

4. Quick Check:

   Invalid SSL = Not Secure warning [OK]

Hint: Expired SSL causes 'Not Secure' warning [OK]

Common Mistakes:

• Thinking HTTP URL causes warning when URL is https://
• Blaming slow internet for security warnings
• Assuming old browsers don't support HTTPS

5. You want to ensure your website visitors' data is safe. Which combination of actions best achieves this?

hard

A. Use HTTP only but add a password to your website

B. Use HTTPS but allow users to access HTTP versions optionally

C. Use HTTPS with a valid SSL certificate and redirect all HTTP traffic to HTTPS

D. Use HTTP and rely on browser security warnings

Solution

1. Step 1: Importance of HTTPS and SSL

   HTTPS with a valid SSL certificate encrypts data and verifies website identity.

2. Step 2: Redirecting HTTP to HTTPS

   Redirecting all HTTP traffic to HTTPS ensures users always use the secure version.

3. Final Answer:

   Use HTTPS with a valid SSL certificate and redirect all HTTP traffic to HTTPS -> Option C

4. Quick Check:

   HTTPS + Redirect = Safe data [OK]

Hint: Always redirect HTTP to HTTPS with valid SSL [OK]

Common Mistakes:

• Thinking password alone secures HTTP
• Allowing HTTP access weakens security
• Ignoring SSL certificate validity