HTTP Status Code Reference
Searchable reference of all HTTP status codes with descriptions and use cases.
HTTP status codes communicate the outcome of every web request — success, failure, redirect, or server error. A solid understanding of status codes is essential for building robust APIs, configuring reverse proxies, debugging client-server interactions, and writing meaningful test assertions. Both the exact code and its semantics matter: a 401 and a 403 both block access but require fundamentally different client responses.
This reference covers every standardised code across the 1xx–5xx classes, including recently standardised additions like 103 Early Hints and 425 Too Early, with descriptions, common causes, appropriate server usage, and recommended client behaviour for each.
كيفية البحث عن معنى رموز حالة HTTP
- 1
أدخل رمز الحالة أو الكلمة المفتاحية
أدخل رمز حالة HTTP (مثل 404) أو كلمة مفتاحية (مثل «غير موجود») في مربع البحث؛ ستعرض الأداة معلومات رموز الحالة المطابقة.
- 2
عرض الشرح التفصيلي
اطّلع على الاسم الرسمي لرمز الحالة والفئة التي ينتمي إليها (1xx–5xx) والشرح التفصيلي وسيناريوهات الاستخدام الشائعة.
- 3
الرجوع إلى معيار RFC
اطّلع على مراجع مواصفات RFC ذات الصلة لفهم التعريف التقني لرمز الحالة هذا ومتطلبات المعيار.
How HTTP Status Codes Are Standardised
HTTP status codes are defined primarily in RFC 9110 (the 2022 update to RFC 7231), with additional codes specified in protocol extensions. The IANA HTTP Status Code Registry is the authoritative list, maintained as a living document. New codes require an RFC or similar specification and must fit into the class structure defined by the first digit.
The extensibility model means that new codes can be added without breaking existing clients, because a client that does not recognise a specific code can fall back to the class-level default (e.g., treating 451 as 400). Some codes like 418 (I'm a Teapot, from RFC 2324) are technically not in the IANA registry as reserved but are widely known and protected from assignment to serious uses.
لماذا تستخدم مرجع FileCrank لرموز حالة HTTP؟
- ✓ يشمل جميع رموز حالة HTTP القياسية (1xx–5xx)
- ✓ يدعم البحث برقم رمز الحالة أو الكلمة المفتاحية
- ✓ يقدم شرحاً تفصيلياً وسيناريوهات استخدام ومراجع مواصفات RFC
- ✓ يعمل بالكامل في المتصفح — لا يُنقَل أي بيانات
- ✓ مجاني ومثالي لتطوير الويب وتشخيص واجهات برمجة التطبيقات
الميزات والمواصفات
الأسئلة الشائعة
How do I use the HTTP Status Code Reference?
Enter any HTTP status code (e.g., 404) or a description keyword (e.g., 'not found') and the tool instantly displays matching codes with explanations.
What is an HTTP status code?
An HTTP status code is a 3-digit numeric response from a web server indicating the outcome of a request. Codes 2xx indicate success, 3xx indicate redirection, 4xx indicate client error, and 5xx indicate server error.
What does a 404 error mean?
404 means 'Not Found.' The server received the request but could not locate the requested resource (webpage, file, API endpoint). Check the URL spelling and verify the resource exists.
What is the difference between a 301 and 302 redirect?
301 (Moved Permanently) indicates the resource has permanently moved and browsers should update bookmarks. 302 (Found) indicates a temporary redirect; browsers should keep the original URL. Use 301 for permanent moves.
What causes a 500 Internal Server Error?
A 500 error indicates a server-side application crash or unhandled exception. Check server logs, verify application code, and ensure dependencies are correctly configured. This is a server problem, not a client problem.
What does 429 Too Many Requests mean?
429 means the client sent too many requests in a short time. The server is rate-limiting to prevent abuse. Wait before retrying; some servers provide a 'Retry-After' header indicating when to retry.
HTTP Status Code Reference vs. RFC 9110
RFC 9110 is the authoritative specification but spans hundreds of pages covering the entire HTTP semantics, making it impractical to browse for a quick status code lookup. This reference extracts and organises only the status code information in a searchable format, presenting descriptions and guidance concisely — designed for developers who need an answer in seconds, not a full protocol specification read.
أدوات ذات صلة
يشمل مرجع FileCrank لرموز حالة HTTP جميعَ رموز الحالة القياسية (1xx–5xx) ويقدم الاسم الرسمي والشرح التفصيلي وسيناريوهات الاستخدام ومراجع مواصفات RFC. يتم البحث محلياً في المتصفح دون تخزين البيانات. مجاني دون حساب.
Advertisement