HTTP Status Codes
Complete reference for HTTP status codes and their meanings with examples and troubleshooting
HTTP Status Codes
Complete reference for HTTP status codes and their meanings with examples and troubleshooting
Search HTTP Status Codes
Search HTTP Status Codes
Enter a status code, name, or category to search
Popular searches:
About HTTP Status Codes
HTTP status codes are three-digit numbers returned by web servers to indicate the result of a client's request. Our comprehensive reference covers all standard HTTP status codes from 100 to 599, including common codes like 200 (OK), 404 (Not Found), and 500 (Internal Server Error), with detailed explanations, examples, and troubleshooting tips.
- Complete 1xx-5xx status code coverage
- Detailed descriptions and use cases
- Common causes and solutions
- Server configuration examples
- SEO and performance implications
Understanding HTTP Status Codes
- 1xx Informational - Request received, server is continuing the process
- 2xx Success - Request was successfully received, understood, and accepted
- 3xx Redirection - Further action needs to be taken to complete the request
- 4xx Client Error - Request contains bad syntax or cannot be fulfilled
- 5xx Server Error - Server failed to fulfill an apparently valid request
Frequently Asked Questions
What are http status codes?
HTTP status codes are three-digit numbers returned by a web server in response to a browser or client request. They indicate whether a request was successful, redirected, or resulted in an error. Status codes are grouped into five categories: 1xx (informational), 2xx (success), 3xx (redirection), 4xx (client error), and 5xx (server error). utilAZ provides a complete reference for all standard HTTP status codes with explanations and troubleshooting tips.
How to fix 404 not found errors?
To fix 404 errors, first verify that the URL is spelled correctly and matches the actual file path on the server. Check if the page was moved or deleted, and set up a 301 redirect to the new location if applicable. Review your server configuration files and .htaccess rules for rewrite errors. You can use utilAZ to look up the 404 status code details and recommended solutions.
What does 200 ok mean in http?
The 200 OK status code means the server successfully processed the request and returned the expected content to the client. It is the standard response for a successful GET, POST, or other HTTP request. This is the most common status code on the web and indicates that everything is working as intended.
Difference between 301 and 302 redirects?
A 301 redirect indicates that a resource has permanently moved to a new URL, and search engines will transfer link equity to the new address. A 302 redirect signals a temporary move, meaning search engines keep the original URL indexed and do not pass full ranking power. Use 301 for permanent URL changes and 302 when you plan to restore the original URL later.
How to troubleshoot 500 internal server errors?
Start by checking your server error logs for specific error messages that reveal the root cause. Verify file permissions are set correctly (644 for files, 755 for directories) and review recent changes to configuration files or deployed code. Test with a minimal setup to isolate the issue, and ensure your server has enough memory and CPU resources. If the problem persists, contact your hosting provider for server-level diagnostics.
HTTP Status Code Categories
2xx Success Codes
- 200 OK: Request successful
- 201 Created: Resource created successfully
- 202 Accepted: Request accepted for processing
- 204 No Content: Successful but no content to return
- 206 Partial Content: Range request fulfilled
3xx Redirection Codes
- 301 Moved Permanently: Resource permanently moved
- 302 Found: Temporary redirect
- 304 Not Modified: Resource not modified
- 307 Temporary Redirect: Temporary redirect (method preserved)
- 308 Permanent Redirect: Permanent redirect (method preserved)
4xx Client Error Codes
- 400 Bad Request: Invalid request syntax
- 401 Unauthorized: Authentication required
- 403 Forbidden: Server understands but refuses
- 404 Not Found: Resource not found
- 429 Too Many Requests: Rate limit exceeded
5xx Server Error Codes
- 500 Internal Server Error: Generic server error
- 502 Bad Gateway: Invalid response from upstream
- 503 Service Unavailable: Server temporarily unavailable
- 504 Gateway Timeout: Upstream server timeout
- 505 HTTP Version Not Supported: Unsupported HTTP version
Troubleshooting Common HTTP Errors
404 Not Found Solutions
- • Check URL spelling and capitalization
- • Verify file exists in correct directory
- • Check server configuration and redirects
- • Review .htaccess rules
- • Clear browser cache and try again
500 Internal Server Error Solutions
- • Check server error logs for details
- • Verify file permissions (typically 644 for files, 755 for folders)
- • Review server configuration files
- • Check for resource limits (memory, CPU)
- • Test with minimal configuration
403 Forbidden Solutions
- • Check file and directory permissions
- • Verify index file exists (index.html, index.php)
- • Review server access rules
- • Check IP restrictions
- • Verify authentication credentials
HTTP Status Codes and SEO
HTTP status codes play a crucial role in SEO by communicating page status to search engines. Understanding their impact helps maintain good search rankings and user experience.
SEO-Friendly Codes
- • 200 OK - Pages indexed normally
- • 301 Redirect - Passes link equity
- • 304 Not Modified - Improves caching
Caution Codes
- • 302 Redirect - Temporary, no equity transfer
- • 404 Errors - Remove from index if persistent
- • 410 Gone - Permanently removed
SEO-Damaging Codes
- • 5xx Errors - Server reliability issues
- • High 4xx rates - Site quality problems
- • Redirect chains - Dilute link equity
Server Configuration Examples
Proper server configuration ensures correct HTTP status codes are returned. Here are common configuration examples for different servers.
Apache .htaccess Examples:
Nginx Configuration Examples:
}
