🎓 Free Capstone Projects with Full Documentation, ER Diagrams & Source Code — Updated Weekly for 2026
👨‍💻 Free Source Code & Capstone Projects for Developers

Frequently Asked Questions

What is the difference between 4xx and 5xx errors?
4xx means YOUR request was wrong — you need to fix the request (wrong URL, missing auth, bad payload, too many requests). 5xx means the server received your request but failed to fulfill it — the server admin needs to fix the server (crash, config, dependency down). As an API consumer hitting 5xx, your options are: retry with backoff, contact the API provider, or wait.
What does 403 Forbidden actually mean?
The server understood your request but is refusing to fulfill it because you do not have permission for THIS specific resource. 403 is different from 401 (you are not authenticated at all) and 404 (resource does not exist). 403 says: "you exist, the resource exists, but you cannot have it." Common causes: file permissions, CDN blocking your country/IP, missing roles/scopes, Cloudflare bot challenge.
What does 429 Too Many Requests mean?
You hit a rate limit. The server is telling you to slow down. Look at the Retry-After response header — it tells you how many seconds to wait before retrying. Best practice: implement exponential backoff (wait 1s, 2s, 4s, 8s...) with jitter. For APIs, also check if there is a X-RateLimit-Reset header that tells you when the bucket refills.
What does 502 Bad Gateway mean?
A reverse proxy or gateway (nginx, Cloudflare, AWS ALB) tried to pass your request to an upstream server, and the upstream server returned an invalid response (or no response). Common causes: the upstream is down/crashed, networking issue between proxy and upstream, upstream timeout, response too large. Check the upstream's health first.
What does 504 Gateway Timeout mean?
Similar to 502, but specifically: the upstream server did not respond in time. The reverse proxy gave up waiting. Common causes: long-running database query, blocked async operation, deadlock, infinite loop, network latency. Increase the proxy's read timeout temporarily to diagnose, but the real fix is making the upstream respond faster.
Should I retry on every 5xx?
Generally yes, with exponential backoff and a max attempt count. 500/502/503/504 are usually transient — the server might recover. But: (1) Only retry idempotent requests (GET, PUT, DELETE — not POST that creates duplicate resources). (2) Cap retries at 3-5. (3) Add jitter to avoid thundering-herd retries from many clients at once. (4) Do not retry on 501 (not implemented) — it will never work.
Why does my site keep returning 503?
503 Service Unavailable typically means: (1) your server is overwhelmed (out of CPU/memory), (2) your app is in maintenance mode, (3) your reverse proxy cannot connect to the app (app crashed, process pool exhausted), or (4) a rate limiter at the infrastructure level is shedding load. Check application monitoring plus server resources plus recent deploys.
How often is this HTTP error reference updated?
New posts are added when HTTP standards add codes (rare) or when major web platforms ship new error patterns. Existing posts are revised periodically. Last refreshed: May 2026.