← Public decks·Computer Science

HTTP Status Codes and REST Basics

Web/API interview cards — key HTTP methods, status code families, and REST constraints.

12 cards· by GuruOwl

Make a deck like this from your own PDF — free.

Try it
  1. 01
    What does HTTP 200 mean?
    OK — the request succeeded.
    2xx
  2. 02
    What does HTTP 201 mean?
    Created — a new resource was successfully created (often after POST).
    2xx
  3. 03
    What does HTTP 204 mean?
    No Content — success with empty response body (common after DELETE).
    2xx
  4. 04
    What does HTTP 301 mean vs 302?
    301 Permanent Redirect; 302 Found/temporary redirect. 301 signals the resource moved permanently for caching/SEO.
    3xx
  5. 05
    What does HTTP 400 mean?
    Bad Request — the client sent an invalid request.
    4xx
  6. 06
    What does HTTP 401 mean vs 403?
    401 Unauthorized (unauthenticated / bad credentials); 403 Forbidden (authenticated but not allowed).
    4xx
  7. 07
    What does HTTP 404 mean?
    Not Found — no resource at the URI (or not disclosed).
    4xx
  8. 08
    What does HTTP 409 mean?
    Conflict — request conflicts with current resource state (e.g., version conflict).
    4xx
  9. 09
    What does HTTP 500 mean?
    Internal Server Error — unexpected server-side failure.
    5xx
  10. 10
    Is GET supposed to be safe and idempotent?
    Yes — safe (no state change) and idempotent (same effect when repeated).
    methods
  11. 11
    Is PUT idempotent? Is POST?
    PUT is idempotent (replace resource); POST is generally not (each call may create/side-effect again).
    methods
  12. 12
    What does REST emphasize about resources and representations?
    Resources identified by URIs; manipulated via standard methods; representations (JSON/HTML) transferred over a uniform interface; often stateless servers.
    rest