Skip to content
Explore the learning library ☟
◎ Google Translate
SanchitGurukulTechnology · Education · Innovation Take a quiz

SG HTTP Status Reference

SanchitGurukulTechnology • Education • Innovation
SG Utility
WEB & API TROUBLESHOOTING REFERENCE

HTTP Status Reference

Search HTTP response codes, understand what they mean, and see practical troubleshooting guidance.

✓ 1xx–5xx coverage✓ Search & filters✓ Troubleshooting notes✓ Local reference data
● Local & private
Common codes
HTTP status codes 0 codes

How to read HTTP status codes

1xxInformational

The request is continuing or protocol negotiation is in progress.

2xxSuccess

The server received, understood and successfully processed the request.

3xxRedirection

The client needs another step, usually following a different URL or using cached content.

4xxClient Error

The request is invalid, unauthorized, forbidden, missing, rate-limited or otherwise cannot be fulfilled as sent.

5xxServer Error

The server, proxy, gateway or upstream service failed while handling an otherwise valid request.

Export reference

Download the built-in reference table for offline troubleshooting or documentation.

Examples & troubleshooting tips

Example: 404 Not Found

Check the URL, application route, rewrite rules, deployment path and whether the requested resource was removed or renamed.

Example: 502 Bad Gateway

Check proxy-to-upstream connectivity, upstream health, DNS resolution, TLS handshake, application listener and load-balancer target status.

Example: 429 Too Many Requests

Respect Retry-After when provided, reduce request rate, use exponential backoff and review API or WAF rate limits.

Browser vs API behavior

The same code can have different practical meaning depending on redirects, authentication, caching, reverse proxies and application-specific response bodies.

Namaste! I’m SG Saarthi 👋Need help learning or finding something?