🔍 Search Status Codes

Quick Search:

📊 Results (27 codes)

100 Continue

ℹ️ informational

The server has received the request headers and the client should proceed to send the request body.

🔍 Common Causes:

Large file uploads
POST requests with Expect: 100-continue header

💡 Solutions:

Normal behavior - continue with request

📋 RFC: RFC 7231

101 Switching Protocols

ℹ️ informational

The requester has asked the server to switch protocols and the server has agreed to do so.

🔍 Common Causes:

WebSocket upgrade requests
Protocol upgrade negotiations

💡 Solutions:

Normal behavior for protocol upgrades

📋 RFC: RFC 7231

102 Processing

ℹ️ informational

The server has received and is processing the request, but no response is available yet.

🔍 Common Causes:

Long-running operations
WebDAV requests

💡 Solutions:

Wait for the operation to complete

📋 RFC: RFC 2518

200 OK

✅ success

The request has succeeded.

🔍 Common Causes:

Successful GET, POST, PUT, or DELETE requests

💡 Solutions:

Request completed successfully - no action needed

📋 RFC: RFC 7231

201 Created

✅ success

The request has been fulfilled and resulted in a new resource being created.

🔍 Common Causes:

Successful POST requests that create new resources

💡 Solutions:

Resource created successfully - no action needed

📋 RFC: RFC 7231

202 Accepted

✅ success

The request has been accepted for processing, but the processing has not been completed.

🔍 Common Causes:

Asynchronous processing
Batch operations
Queue-based systems

💡 Solutions:

Check processing status using provided location or polling

📋 RFC: RFC 7231

204 No Content

✅ success

The server successfully processed the request and is not returning any content.

🔍 Common Causes:

Successful DELETE requests
PUT requests with no response body

💡 Solutions:

Request completed successfully - no action needed

📋 RFC: RFC 7231

301 Moved Permanently

↩️ redirection

The resource has been permanently moved to a new location.

🔍 Common Causes:

URL structure changes
Domain migrations
SEO redirects

💡 Solutions:

Update bookmarks and links
Follow the Location header

📋 RFC: RFC 7231

302 Found

↩️ redirection

The resource temporarily resides under a different URI.

🔍 Common Causes:

Temporary redirects
A/B testing
Maintenance pages

💡 Solutions:

Follow the Location header
Original URL may work later

📋 RFC: RFC 7231

304 Not Modified

↩️ redirection

The resource has not been modified since the version specified by request headers.

🔍 Common Causes:

Conditional GET requests
Browser caching
If-None-Match headers

💡 Solutions:

Use cached version - no action needed

📋 RFC: RFC 7232

307 Temporary Redirect

↩️ redirection

The request should be repeated with another URI, but future requests should still use the original URI.

🔍 Common Causes:

Temporary server maintenance
Load balancing
A/B testing

💡 Solutions:

Follow the Location header with same HTTP method

📋 RFC: RFC 7231

308 Permanent Redirect

↩️ redirection

The resource has been permanently moved to another URI and future requests should use the new URI.

🔍 Common Causes:

Permanent URL changes
HTTPS enforcement
API versioning

💡 Solutions:

Update all references to use the new URI

📋 RFC: RFC 7538

400 Bad Request

❌ client error

The request could not be understood by the server due to malformed syntax.

🔍 Common Causes:

Invalid JSON
Missing required parameters
Malformed URLs
Invalid headers

💡 Solutions:

Check request syntax
Validate JSON format
Verify required parameters

📋 RFC: RFC 7231

401 Unauthorized

❌ client error

The request requires user authentication.

🔍 Common Causes:

Missing credentials
Invalid API keys
Expired tokens
Incorrect login

💡 Solutions:

Provide valid credentials
Check API key
Refresh authentication token

📋 RFC: RFC 7235

403 Forbidden

❌ client error

The server understood the request but refuses to authorize it.

🔍 Common Causes:

Insufficient permissions
IP restrictions
Resource access denied
API rate limits

💡 Solutions:

Check user permissions
Verify IP whitelist
Contact administrator

📋 RFC: RFC 7231

404 Not Found

❌ client error

The requested resource could not be found on the server.

🔍 Common Causes:

Incorrect URL
Deleted resources
Broken links
Typos in path

💡 Solutions:

Check URL spelling
Verify resource exists
Update broken links

📋 RFC: RFC 7231

405 Method Not Allowed

❌ client error

The method specified in the request is not allowed for the resource.

🔍 Common Causes:

Using POST instead of GET
Unsupported HTTP methods
API endpoint restrictions

💡 Solutions:

Check allowed methods in response headers
Use correct HTTP method

📋 RFC: RFC 7231

409 Conflict

❌ client error

The request could not be completed due to a conflict with the current state of the resource.

🔍 Common Causes:

Concurrent modifications
Duplicate entries
Version conflicts
Resource locks

💡 Solutions:

Resolve conflicts manually
Retry with updated data
Check resource state

📋 RFC: RFC 7231

410 Gone

❌ client error

The requested resource is no longer available and will not be available again.

🔍 Common Causes:

Permanently deleted resources
Discontinued APIs
Expired content

💡 Solutions:

Remove references to resource
Find alternative resources

📋 RFC: RFC 7231

422 Unprocessable Entity

❌ client error

The request was well-formed but was unable to be followed due to semantic errors.

🔍 Common Causes:

Validation errors
Invalid data format
Business rule violations

💡 Solutions:

Fix validation errors
Check data format
Review business rules

📋 RFC: RFC 4918

429 Too Many Requests

❌ client error

The user has sent too many requests in a given amount of time.

🔍 Common Causes:

Rate limiting
API quota exceeded
DDoS protection

💡 Solutions:

Implement request throttling
Wait before retrying
Check rate limits

📋 RFC: RFC 6585

500 Internal Server Error

💥 server error

The server encountered an unexpected condition that prevented it from fulfilling the request.

🔍 Common Causes:

Server-side code errors
Database issues
Configuration problems
Resource exhaustion

💡 Solutions:

Check server logs
Contact server administrator
Retry request later

📋 RFC: RFC 7231

501 Not Implemented

💥 server error

The server does not support the functionality required to fulfill the request.

🔍 Common Causes:

Unsupported HTTP methods
Missing features
Legacy server software

💡 Solutions:

Use supported methods
Contact server administrator
Use alternative approach

📋 RFC: RFC 7231

502 Bad Gateway

💥 server error

The server received an invalid response from an upstream server.

🔍 Common Causes:

Proxy server issues
Upstream server down
Network connectivity problems

💡 Solutions:

Check upstream servers
Verify proxy configuration
Retry request

📋 RFC: RFC 7231

503 Service Unavailable

💥 server error

The server is currently unable to handle the request due to temporary overloading or maintenance.

🔍 Common Causes:

Server maintenance
High traffic
Resource exhaustion
Planned downtime

💡 Solutions:

Wait and retry
Check Retry-After header
Use alternative servers

📋 RFC: RFC 7231

504 Gateway Timeout

💥 server error

The server did not receive a timely response from an upstream server.

🔍 Common Causes:

Slow upstream servers
Network latency
Timeout configurations
Long-running operations

💡 Solutions:

Increase timeout values
Check upstream server performance
Optimize requests

📋 RFC: RFC 7231

505 HTTP Version Not Supported

💥 server error

The server does not support the HTTP protocol version used in the request.

🔍 Common Causes:

Old server software
HTTP/2 or HTTP/3 not supported
Protocol mismatches

💡 Solutions:

Use supported HTTP version
Upgrade server software
Check client configuration

📋 RFC: RFC 7231

📚 HTTP Status Code Reference

ℹ️ 1xx Informational

These codes indicate that the request was received and understood, and processing continues.

✅ 2xx Success

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

↩️ 3xx Redirection

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

❌ 4xx Client Error

These codes indicate that the request contains bad syntax or cannot be fulfilled by the server.

💥 5xx Server Error

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