HTTP Status Codes Flashcards
41 cards · EN → EN · Coding
60 learners cloned this deck
All essential HTTP response status codes grouped by class (1xx–5xx), with meanings and real-world context. Based on IETF RFCs 7231, 7235, 6585, and 9110. Indispensable for web developers, API designers, and anyone who builds or debugs networked applications.
This page covers HTTP Status Codes: 41 flashcards in the coding category. Cards are oriented around the EN → EN language pair, so each prompt trains recognition in the direction you actually need. Difficulty is tagged beginner, so you can expect a beginner-friendly progression rather than a random dump of trivia.
FSRS keeps interview and engineering flashcards efficient: stable HTTP or complexity facts drift further out, while shaky ones return sooner. That is how you keep all 41 prompts in "HTTP Status Codes" cold-start ready without grinding the whole list every night.
Scroll the first twenty cards for a feel of the fronts and backs, then download the app or open the web signup flow to keep studying with adaptive intervals.
Card preview
First 20 cards from this deck (front / back).
| # | Front | Back |
|---|---|---|
| 1 | 100 Continue | Informational — Server received request headers; client should proceed to send the request body. |
| 2 | 101 Switching Protocols | Informational — Server agrees to switch protocols as requested by client (e.g., HTTP → WebSocket). |
| 3 | 103 Early Hints | Informational — Preliminary response with Link headers to let browser preload resources before the final response is ready. |
| 4 | 200 OK | Success — The request succeeded. Response body contains the requested resource or result. |
| 5 | 201 Created | Success — The request succeeded and a new resource was created. Location header usually points to the new resource. |
| 6 | 202 Accepted | Success — Request accepted for processing, but processing is not yet complete (async operations). |
| 7 | 204 No Content | Success — Request succeeded; no content to return in body. Common for DELETE or PUT responses. |
| 8 | 206 Partial Content | Success — Server is delivering only part of the resource (range request), using the `Range` header. |
| 9 | 301 Moved Permanently | Redirect — Resource has permanently moved to a new URL (in Location header). Browser and SEO bots update their records. |
| 10 | 302 Found | Redirect — Resource temporarily at a different URL. Client should continue using the original URL for future requests. |
| 11 | 304 Not Modified | Redirect (cache) — Requested resource hasn't changed since the client's last request. Use cached version. |
| 12 | 307 Temporary Redirect | Redirect — Like 302 but guarantees the HTTP method is preserved (POST stays POST). Temporary redirect. |
| 13 | 308 Permanent Redirect | Redirect — Like 301 but preserves HTTP method. Permanent redirect that keeps POST/PUT method intact. |
| 14 | 400 Bad Request | Client Error — Server cannot process request due to malformed syntax, invalid framing, or deceptive routing. |
| 15 | 401 Unauthorized | Client Error — Authentication required but missing or invalid. Response must include `WWW-Authenticate` header. |
| 16 | 403 Forbidden | Client Error — Server understood the request but refuses to authorize it. Authentication won't help. |
| 17 | 404 Not Found | Client Error — Requested resource doesn't exist on this server. |
| 18 | 405 Method Not Allowed | Client Error — HTTP method is not supported for this resource. Response includes `Allow` header listing valid methods. |
| 19 | 408 Request Timeout | Client Error — Server timed out waiting for the client to send the complete request. |
| 20 | 409 Conflict | Client Error — Request conflicts with the current state of the target resource (e.g., duplicate entry, edit conflict). |
How to study with FSRS
Rate each card Honestly after you recall. FSRS uses that rating to set the next interval—hard cards return sooner, easy ones wait longer. Keep sessions short and daily rather than cramming the full deck.
Study this deck in Neurako
Clone-style study on web and mobile with FSRS from day one. Prefer Anki? Convert decks with our free CSV and APKG tools.
Frequently asked questions
Are these HTTP Status Codes flashcards free?
Yes. You can preview cards here and start studying free in Neurako on web or mobile. Pro adds higher AI limits and advanced FSRS optimizer controls.
Can I import HTTP Status Codes cards into Anki?
Export or convert with our free csv-to-anki and apkg-to-csv tools on tools.neurako.com, then study in Anki or Neurako—whichever you prefer.
How many HTTP Status Codes cards are in this deck?
This deck includes 41 cards. The preview on this page shows the first 20 so you can judge style and difficulty before cloning.
How is Neurako different from Quizlet for HTTP Status Codes?
Neurako schedules reviews with FSRS adaptive spaced repetition. Quizlet is stronger for quick social sets and games; Neurako is built for long-term retention.
Related flashcard decks
Big-O Complexity Flashcards
Master algorithm time and space complexity analysis. Covers all major complexity classes, common algorithm complexities,
ExploreAmino Acids Flashcards
All 20 standard amino acids with one-letter codes, three-letter codes, and side-chain chemical properties. Built for bio
ExploreHuman Anatomy Flashcards
About fifty major bones and bony landmarks of the human skeleton with their body region or location. Anatomical naming f
ExploreArabic Flashcards
100 of the most common Modern Standard Arabic (MSA / Fusha) words. MSA is used in formal communication, news, and educat
ExploreStart your atelier of knowledge today.
Download on iOS or Android, or keep studying in the browser—the same decks, FSRS reviews, and quiz practice, with clear Free vs Pro limits.