Continue
Initial part of a request was received and the client should continue with it.
رموز حالة HTTP
مرجع قابل للبحث لأكواد حالة HTTP مع الأوصاف ومراجع RFC.
62 معروضة
1xxInformational · 4
RFC 9110
Switching Protocols
Server agrees to switch protocols based on the Upgrade header.
Processing
Server has accepted the request but is still processing it (WebDAV).
Early Hints
Send preliminary headers (Link, etc.) before the final response.
2xxSuccess · 10
OK
Request succeeded.
Created
Request succeeded and a new resource was created.
Accepted
Request was accepted for processing but has not yet completed.
Non-Authoritative Information
Returned metainformation differs from the origin server's response.
No Content
Request succeeded; no body to return.
Reset Content
Request succeeded; the client should reset the document view.
Partial Content
Range request succeeded.
Multi-Status
Body is an XML message with status for multiple resources (WebDAV).
Already Reported
Members of a WebDAV binding were already enumerated.
IM Used
Server fulfilled a GET request and the response is a representation of one or more instance manipulations.
3xxRedirection · 8
Multiple Choices
Multiple representations are available; the client may choose.
Moved Permanently
Resource has a new permanent URI.
Found
Resource is temporarily under a different URI.
See Other
Response is found under a different URI; client should GET it.
Not Modified
Conditional GET: the cached representation is still fresh.
Use Proxy
Deprecated. Resource must be accessed through a proxy.
Temporary Redirect
Resource is temporarily under a different URI; method must not change.
Permanent Redirect
Resource has a new permanent URI; method must not change.
4xxClient error · 29
Bad Request
Server cannot or will not process the request due to a client error.
Unauthorized
Authentication is required and has failed or has not been provided.
Payment Required
Reserved for future use.
Forbidden
Server understood the request but refuses to authorize it.
Not Found
Server can't find the requested resource.
Method Not Allowed
Method is known but not supported by the target resource.
Not Acceptable
Resource cannot generate content matching the Accept headers.
Proxy Authentication Required
Client must authenticate with a proxy first.
Request Timeout
Server timed out waiting for the client.
Conflict
Request conflicts with the current state of the resource.
Gone
Resource is permanently unavailable.
Length Required
Server requires the Content-Length header.
Precondition Failed
Precondition in request headers failed.
Content Too Large
Request body is larger than the server is willing to process.
URI Too Long
Request URI is longer than the server is willing to interpret.
Unsupported Media Type
Request body is in a format the server doesn't support.
Range Not Satisfiable
None of the ranges in the Range header overlap the resource.
Expectation Failed
Expectation in the Expect header could not be met.
I'm a teapot
Server is a teapot. April Fools' joke from RFC 2324; widely implemented as an Easter egg.
Misdirected Request
Request was directed to a server unable to produce a response.
Unprocessable Content
Request is well-formed but semantically invalid.
Locked
Resource is locked (WebDAV).
Failed Dependency
Request failed because of a previous request (WebDAV).
Too Early
Server is unwilling to risk processing a request that might be replayed.
Upgrade Required
Client must switch to a different protocol.
Precondition Required
Server requires the request to be conditional.
Too Many Requests
Client has sent too many requests in a given time (rate limited).
Request Header Fields Too Large
One or more request headers (or all of them) are too large.
Unavailable For Legal Reasons
Resource is unavailable due to legal demands.
5xxServer error · 11
Internal Server Error
Server encountered an unexpected condition.
Not Implemented
Server does not support the functionality required.
Bad Gateway
Server, while acting as a gateway, got an invalid response from upstream.
Service Unavailable
Server is currently unable to handle the request (overloaded or down).
Gateway Timeout
Server, while acting as a gateway, didn't get a response in time.
HTTP Version Not Supported
Server doesn't support the HTTP version in the request.
Variant Also Negotiates
Transparent content negotiation results in a circular reference.
Insufficient Storage
Server cannot store the representation needed to complete the request (WebDAV).
Loop Detected
Server detected an infinite loop while processing (WebDAV).
Not Extended
Further extensions to the request are required.
Network Authentication Required
Client needs to authenticate to gain network access (captive portal).
إدخالاتك تبقى على جهازك. كل أدوات المطورين في TaskKit تعمل في متصفحك. الرموز والـ payloads وما تلصقه لا يُرسل لخوادم TaskKit ولا لأي طرف ثالث.
ما الذي تفعله هذه الأداة
مرجع قابل للبحث لكل رمز حالة HTTP قياسي، منظَّم بالفئات (1xx معلوماتية، 2xx نجاح، 3xx إعادة توجيه، 4xx خطأ من العميل، 5xx خطأ من الخادم). ابحث بالرقم أو بالاسم أو بالوصف. كل مدخلة تتضمّن العبارة الرسمية للسبب وقياس RFC الذي يُعرّفها.
متى تستخدمها
- الاختيار بين
401 Unauthorizedو403 Forbiddenلطلب مرفوض. - التأكد هل ينبغي أن تكون إعادة التوجيه
302أو303أو307أو308. - البحث عن رمز غير مألوف ظهر للتو في سطر سجلّ.
- التحقّق أيّ RFC قدّم رمزاً ما (مثلاً
451 Unavailable For Legal Reasonsهو RFC 7725).
كيف تعمل
مجموعة البيانات ساكنة وتأتي ضمن حزمة الصفحة. لا يوجد استدعاء API — يجري البحث على فهرس في الذاكرة، فهو فوري حتى على الاتصالات البطيئة. تأتي بيانات كل رمز مباشرةً من سجلّ IANA لرموز حالة HTTP والـ RFCs ذات الصلة (في معظمها 9110، مع بعض الرموز الأقدم التي لا تزال تشير إلى 7231 وما قبلها).
ملاحظات
401 مقابل 403؟ 401 تعني «لم تثبت من أنت — حاول مجدّداً مع اعتمادات». 403 تعني «أعرف من أنت ولا يحقّ لك هذا». إن كان تسجيل دخول المستخدم سيغيّر الإجابة فأعد 401؛ وإلا فأعد 403.
302 مقابل 307؟ كان المقصود من 302 أصلاً الحفاظ على طريقة الطلب عند إعادة التوجيه، لكن المتصفحات تاريخياً أعادت كتابة POST إلى GET. أُضيفت 303 و 307 لجعل النيّة صريحة: 303 See Other تجلب دائماً الرابط الجديد بـ GET، و 307 Temporary Redirect تحفظ دائماً الطريقة. استخدم 303 بعد POST ناجح، و 307 لإعادة توجيه مؤقّتة تحفظ الطريقة.
هل 418 I'm a teapot حقيقي؟ نعم، ولا يزال في RFC 2324 (1 أبريل 1998) ومُعترَفاً به في RFC 9110 §15.5.19. استخدمه باعتدال.
أدوات ذات صلة
- cURL ↔ fetch — أعد تشغيل الطلبات لرؤية الرموز حية
- منسّق JSON — لفحص أجسام الاستجابات