HTTP Status Codes

Introduction to HTTP Status Codes

When a browser requests a service from a web server, the server always returns an HTTP status code along with the response. These three-digit codes indicate whether a request was successful, redirected, or resulted in an error. While often called "HTML error messages," they're technically HTTP status messages that provide crucial information about the request's outcome.

Here's a complete reference table of all standard HTTP status codes, organized by their classification.

Complete HTTP Status Codes Table

1xx: Informational Responses

These codes indicate that the request was received and understood, and the process is continuing.

2xx: Success Responses

These codes indicate that the request was successfully received, understood, and accepted.

3xx: Redirection Responses

These codes indicate that further action needs to be taken by the client to complete the request.

4xx: Client Error Responses

These codes indicate that the client seems to have made an error in the request.

5xx: Server Error Responses

These codes indicate that the server failed to fulfill a valid request.

Quick Reference: Most Common Status Codes

Browser Developer Tools Quick Guide

To view status codes in your browser:

1. Chrome/Firefox/Edge:

   • Press F12 or right-click → Inspect
   • Go to "Network" tab
   • Refresh the page
   • View status codes in the "Status" column

2. Common Status Code Colors:

   • 🟢 Green (2xx): Success
   • 🟡 Yellow (3xx): Redirect
   • 🔴 Red (4xx/5xx): Error
   • 🔵 Blue (1xx): Informational

Best Practices for Web Developers

For Client-Side Errors (4xx):

• 400: Provide specific error messages about what's wrong
• 401: Include WWW-Authenticate header for authentication methods
• 403: Clearly explain why access is denied (without revealing sensitive info)
• 404: Offer helpful alternatives, search, or navigation
• 429: Include Retry-After header indicating when to retry

For Server-Side Errors (5xx):

• 500: Log detailed errors server-side but show user-friendly messages
• 503: Include Retry-After header if downtime is scheduled
• Always have custom error pages for better user experience
• Monitor 5xx errors as they indicate server problems

For Redirects (3xx):

• Use 301 for permanent moves (SEO-friendly)
• Use 302/307 for temporary redirects
• Minimize redirect chains (multiple consecutive redirects)
• Test redirects to ensure they work correctly

Interactive Learning Activity

Try this exercise to reinforce your understanding:

1. Visit a website and open Developer Tools (F12)
2. Go to Network tab and check "Preserve log"
3. Navigate through the site
4. Identify different status codes in requests
5. Note which resources get 200, 304, or other codes

Common findings:

• HTML pages: Usually 200 (or 304 if cached)
• CSS/JS files: 200, 304, or sometimes 404 if missing
• Images: 200, 304, or 404
• API calls: Various codes based on functionality

Frequently Asked Questions

Q: What's the difference between 404 and 410? A: 404 means "not found" but might be available later. 410 means "gone" permanently with no forwarding address.

Q: When should I use 500 vs 503? A: Use 500 for unexpected server errors. Use 503 when you know the service is unavailable (maintenance, overload).

Q: Are status codes case-sensitive? A: No, "404 Not Found" and "404 not found" are equivalent, though the standard capitalization is typically used.

Q: Can I create custom status codes? A: You can use non-standard codes, but clients may not understand them. Stick to standard codes when possible.

Q: Do all HTTP methods return the same status codes? A: No, some codes are method-specific. For example, 201 is typically for POST, 204 for DELETE, etc.