An haɗa HTTP status codes zuwa rukunai biyar ta lambar farko, kuma zaɓen madaidaici yana barin clients su amsa daidai ba tare da parse ɗin body ba.
2xx Success — the request worked
3xx Redirection — further action / resource moved
4xx Client error — the caller did something wrong
5xx Server error — the server failed
2xx
200 OK — nasara ta gaba ɗaya (GET, PUT, PATCH).201 Created — an ƙirƙiri resource (mayar da Location header).202 Accepted — an karɓa don sarrafa async, ba a gama ba tukuna.204 No Content — nasara ba tare da body ba (na kowa ga DELETE).4xx
400 Bad Request — syntax mara kyau ko input mara inganci.401 Unauthorized — ba a tantance ba (babu/marar inganci credentials).403 Forbidden — an tantance amma ba a yarda ba.404 Not Found — resource ba ya nan.409 Conflict — yana cin karo da yanayin yanzu (misali email kwafi).422 Unprocessable Entity — an tsara shi da kyau amma ya gaza validation.429 Too Many Requests — an iyakance rate.5xx
500 Internal Server Error — kuskuren server da ba a tsammani ba.503 Service Unavailable — ya sauka na ɗan lokaci/cika da nauyi.POST /users → 201 Created
Location: /users/42
DELETE /users/42 → 204 No Content
GET /users/999 → 404 Not Found
{ "error": "user not found" }
Babban bambancin da masu hira ke bincike: 401 ("wanene kai?") vs 403 ("na san ka, amma a'a"), da 400 (syntax mara kyau) vs 422 (syntax mai inganci, bayanai marasa inganci).
Status codes su ne babbar sigina a cikin response na REST — clients, proxies, monitoring, da logic na retry duk suna dogara da su, don haka samun su daidai yana da muhimmanci ga interoperability. Gazawar da ta fi kowa ita ce mayar da 200 OK da body na { "error": ... }: yana tilasta kowane client ya parse body don sanin ko kiran ya yi nasara, yana lalata tooling na HTTP na gaba ɗaya, kuma yana ɓoye gazawa daga monitoring. Codes madaidaita suna kuma jagorantar hali na atomatik: 429 ko 503 yana gaya wa client da aka gina da kyau ya ja da baya ya sake gwadawa, yayin da 4xx ke cewa "kada ka sake gwadawa, gyara request." Masu hira suna amfani da wannan tambaya don duba ko ka fahimci HTTP a matsayin yarjejeniya maimakon jigilar wawa, kuma ka bambanta nau'i-nau'i masu dabara (401/403, 400/422) daidai — alamar wanda ya gina kuma ya yi amfani da APIs na gaske.
Ɗakin karatu na tambayoyin hira na IT tare da amsoshi cikakke — daga Junior zuwa Senior.
Ba da Gudummawa