Why curl for HTTP requests in Linux CLI? - Purpose & Use Cases

The Big Idea

What if you could talk to websites without opening a browser, all from your keyboard?

The Scenario

Imagine you need to check the status of a website or download a file. Without tools, you might open a browser, click around, and manually copy information. Doing this repeatedly for many sites or automating checks is tiring and slow.

The Problem

Manually opening browsers or apps to get data is slow and boring. It's easy to make mistakes copying URLs or missing updates. You can't quickly repeat tasks or use the data in scripts, so you waste time and energy.

The Solution

curl lets you send HTTP requests right from the command line. It quickly fetches web pages, downloads files, or talks to APIs without opening a browser. This makes repetitive tasks fast, reliable, and easy to automate.

Before vs After

✗ Before

Open browser -> Type URL -> Copy content -> Save manually

✓ After

curl https://example.com -o page.html

What It Enables

With curl, you can automate web requests and data downloads, making your scripts powerful and your work faster.

Real Life Example

System admins use curl to check if servers are online by sending quick HTTP requests, saving time and avoiding manual checks.

Key Takeaways

Manual web checks are slow and error-prone.

curl automates HTTP requests from the command line.

This saves time and enables powerful scripting.

Practice

1. What does the curl command primarily do in Linux?

easy

A. Monitor system processes

B. Send HTTP requests to websites

C. Manage file permissions

D. Compile source code

Solution

1. Step 1: Understand the purpose of curl

   The curl command is designed to send HTTP requests and interact with web servers.

2. Step 2: Compare with other options

   Compiling code, managing permissions, and monitoring processes are unrelated to curl's function.

3. Final Answer:

   Send HTTP requests to websites -> Option B

4. Quick Check:

   curl = HTTP requests [OK]

Hint: curl is for web requests, not system tasks [OK]

Common Mistakes:

• Confusing curl with system commands like chmod or ps
• Thinking curl compiles code
• Assuming curl manages files locally

2. Which of the following is the correct syntax to fetch the content of http://example.com using curl?

easy

A. curl http://example.com

B. curl --head http://example.com

C. curl -x http://example.com

D. curl -d http://example.com

Solution

1. Step 1: Identify basic curl usage

   To fetch a webpage, simply use curl URL. No extra flags are needed for a simple GET request.

2. Step 2: Analyze other options

   -x is for proxy, --head fetches headers only, -d sends data (POST), so they are incorrect for simple fetch.

3. Final Answer:

   curl http://example.com -> Option A

4. Quick Check:

   Basic fetch = curl URL [OK]

Hint: Use curl followed by URL to fetch page [OK]

Common Mistakes:

• Using -x which is for proxy
• Using -d which sends data instead of fetching
• Using --head which fetches headers only

3. What will be the output of this command?

curl -I https://example.com

medium

A. An error because -I is invalid

B. The full HTML content of the page

C. Only the HTTP headers of the response

D. The page content saved to a file

Solution

1. Step 1: Understand the -I option in curl

   The -I flag tells curl to fetch only the HTTP headers, not the full content.

2. Step 2: Check other options

   The full HTML content of the page is full content, which -I does not do. An error because -I is invalid is wrong because -I is valid. The page content saved to a file requires -o flag, not present here.

3. Final Answer:

   Only the HTTP headers of the response -> Option C

4. Quick Check:

   -I = headers only [OK]

Hint: Remember -I fetches headers only [OK]

Common Mistakes:

• Thinking -I fetches full page
• Confusing -I with -o for output file
• Assuming -I is invalid flag

4. You want to send JSON data {"name":"John"} to http://api.example.com/users using curl. Which command has an error?

medium

A. curl -d '{name:John}' -X POST -H "Content-Type: application/json" http://api.example.com/users

B. curl -X POST -H "Content-Type: application/json" -d '{"name":"John"}' http://api.example.com/users

C. curl -d '{"name":"John"}' http://api.example.com/users -H "Content-Type: application/json" -X POST

D. curl -X POST -d '{"name":"John"}' -H "Content-Type: application/json" http://api.example.com/users

Solution

1. Step 1: Check JSON data format

   curl -d '{name:John}' -X POST -H "Content-Type: application/json" http://api.example.com/users uses '{name:John}' which misses double quotes around keys and values, making it invalid JSON. Options A, C, D use correct JSON '{"name":"John"}'.

2. Step 2: Confirm curl flags order

   Order of flags does not matter in curl, so A, C, D are valid. Only data format in B is wrong.

3. Final Answer:

   curl -d '{name:John}' -X POST -H "Content-Type: application/json" http://api.example.com/users -> Option A

4. Quick Check:

   JSON must have quotes [OK]

Hint: JSON keys and values need quotes [OK]

Common Mistakes:

• Omitting quotes in JSON data
• Thinking flag order matters in curl
• Using wrong content-type header

5. You want to download a file from http://example.com/file.zip and save it as myfile.zip. Which curl command does this correctly?

hard

A. curl --save myfile.zip http://example.com/file.zip

B. curl -O http://example.com/file.zip > myfile.zip

C. curl -O myfile.zip http://example.com/file.zip

D. curl -o myfile.zip http://example.com/file.zip

Solution

1. Step 1: Understand curl file saving options

   -o filename saves the download to the specified filename. -O saves with original name from URL.

2. Step 2: Analyze each option

   B: curl -O http://example.com/file.zip > myfile.zip saves to 'file.zip' via -O and redirects empty stdout to myfile.zip. C: curl -O myfile.zip http://example.com/file.zip uses -O incorrectly, treating myfile.zip as URL. D: uses invalid flag --save.

3. Final Answer:

   curl -o myfile.zip http://example.com/file.zip -> Option D

4. Quick Check:

   -o sets output filename [OK]

Hint: Use -o to name downloaded file [OK]

Common Mistakes:

• Using > redirection for binary files
• Confusing -O and -o flags
• Using non-existent flags like --save