HTTP Methods and Status Codes

What are the main HTTP methods and what do common status codes like 200, 404, and 500 mean?

Networkingbeginner

// interview question

What are the main HTTP methods and what do common status codes like 200, 404, and 500 mean?

Sample answer

The main HTTP methods are: GET (retrieve data), POST (create data), PUT (update/replace data), PATCH (partial update), and DELETE (remove data). Status code 200 means success, 201 means created, 301/302 are redirects, 400 is bad request, 401 is unauthorized, 403 is forbidden, 404 is not found, and 500 is internal server error. Understanding these is essential for API troubleshooting.

Why this matters

HTTP is the foundation of web communication. DevOps engineers troubleshoot APIs, configure load balancers, set up monitoring, and read access logs daily. Knowing HTTP methods and status codes helps quickly diagnose issues and communicate with developers effectively.

Code examples

Test HTTP endpoints with curl

bash

# GET request
curl -X GET https://api.example.com/users

# POST request with JSON data
curl -X POST https://api.example.com/users \
  -H 'Content-Type: application/json' \
  -d '{"name": "John"}'

# Check response headers and status
curl -I https://example.com

# Verbose output for debugging
curl -v https://example.com

Common mistakes to avoid

Using GET requests to modify data
Not checking response status codes in scripts
Confusing 401 (authentication) with 403 (authorization)

Likely follow-ups

What is the difference between PUT and PATCH?
What does a 502 Bad Gateway error typically indicate?
What is the difference between 401 and 403 status codes?

Answer out loud first, then check yourself against the model answer.

Practice all Junior questions More Networking questions

#http#api#web#networking#troubleshooting

Also worth your time on this topic

Interview

DNS Basics

What is DNS and how does the DNS resolution process work step by step?

junior

Article

How to Check Which Process is Using a Specific Port from Command Line

Learn how to identify which processes are listening on specific ports using netstat, lsof, and ss commands across different operating systems.

Quiz

eBPF for Network Observability and Security Quiz

Test your understanding of eBPF with real scenarios covering the verifier, maps, XDP and tc hooks, CO-RE portability, kube-proxy replacement, runtime security, and debugging programs that won't load.

16-22 minutes

HTTP Methods and Status Codes

More Networking interview questions

Also worth your time on this topic

DNS Basics

How to Check Which Process is Using a Specific Port from Command Line

eBPF for Network Observability and Security Quiz