HTTP Status Codes: Easy Guide

By /

Listen to this Post

Featured Image
HTTP status codes are essential for web developers, system administrators, and cybersecurity professionals. They help diagnose issues, optimize performance, and improve security. Below is an expanded guide with practical commands and tools for testing and debugging HTTP responses.

1XX: Information

  • 100 Continue – The server acknowledges the initial part of the request.
  • 101 Switching Protocols – Used in WebSocket upgrades.
  • 102 Processing – Common in long-running requests.
  • 103 Early Hints – Helps preload resources for faster rendering.

You Should Know:

  • Test HTTP/2 early hints with: 
    curl -I --http2 https://example.com
  • Use `telnet` to manually send HTTP requests: 
    telnet example.com 80
GET / HTTP/1.1
Host: example.com

2XX: Success

  • 200 OK – Standard successful response.
  • 201 Created – Confirms resource creation (common in REST APIs).
  • 204 No Content – Used in APIs where no response body is needed.
  • 206 Partial Content – Supports resumable downloads.

You Should Know:

  • Check partial content requests with: 
    curl -H "Range: bytes=0-100" -I https://example.com/file.zip
  • Verify API responses using httpie: 
    http POST https://api.example.com/data name="test"

3XX: Redirection

  • 301 Moved Permanently – SEO-critical, updates browser cache.
  • 302 Found – Temporary redirect (may cause SEO issues).
  • 304 Not Modified – Saves bandwidth via cached responses.

You Should Know:

  • Follow redirects with curl: 
    curl -L https://example.com/old-link
  • Check caching behavior: 
    curl -I https://example.com | grep -i "cache-control"

4XX: Client Errors

  • 400 Bad Request – Malformed syntax.
  • 401 Unauthorized – Missing/wrong credentials.
  • 403 Forbidden – Access denied (check permissions).
  • 404 Not Found – Resource doesn’t exist.
  • 429 Too Many Requests – Rate-limiting in action.

You Should Know:

  • Test authentication with curl: 
    curl -u username:password https://api.example.com
  • Bypass rate-limiting (ethically!): 
    curl --proxy "http://proxy-server:port" https://example.com

5XX: Server Errors

  • 500 Internal Server Error – Generic server failure.
  • 502 Bad Gateway – Proxy/reverse proxy issues.
  • 503 Service Unavailable – Server overloaded.
  • 504 Gateway Timeout – Upstream server too slow.

You Should Know:

  • Debug server errors with netcat: 
    nc -zv example.com 80
  • Simulate downtime monitoring: 
    while true; do curl -I https://example.com; sleep 5; done

What Undercode Say

Understanding HTTP status codes is crucial for debugging, security, and performance tuning. Use curl, httpie, and `telnet` for manual testing. Monitor APIs with tools like `Postman` and automate checks with scripting.

Prediction

As web applications grow more complex, HTTP/3 and QUIC protocols will make status codes even more critical for real-time debugging.

Expected Output:

HTTP/2 200 
server: nginx 
cache-control: max-age=3600

(No direct URLs extracted, but relevant tools: curl.se, httpie.io)

References:

Reported By: Aaronsimca Http – Hackers Feeds
Extra Hub: Undercode MoN
Basic Verification: Pass ✅

Join Our Cyber World:

💬 Whatsapp | 💬 Telegram

Related Posts: