Kyauta Bayanin Lambobin Matsayin HTTP

Ana amfani da shi don buƙatun tare da Expect: 100-continue. Sabar tana tabbatar da cewa a shirye take ta karɓi jiki kafin abokin ciniki ya aika shi. Ba a saba gani a manhajojin yanar gizo na zamani ba.

Mafi yawan amfani da shi don haɓaka WebSocket — abokin ciniki yana buƙatar Upgrade: websocket sannan sabar ta amsa 101 don musayar.

Amsa ta wucin gadi ta WebDAV da ake aikawa don hana lokacin jiran abokin ciniki ya ƙare yayin ayyuka masu tsawo. An dakatar da amfani da ita — sabobin zamani bai kamata su aika ta ba.

Yana bawa sabobin damar aika kanun Link (preload/preconnect) yayin da ake shirya amsar ƙarshe, don masu binciken yanar gizo su fara samun muhimman kayan gaba da wuri.

Amsar nasara ta ƙa'ida. Ma'anarta ta dogara da hanyar HTTP: GET → an mayar da kayan aiki, POST/PUT → an kammala aiki.

Ana samun sa yawanci bayan POST. Amsar ta kamata ta ƙunshi kanun Location wanda ke nuni ga URL na sabon kayan.

Don ayyuka marasa daidaici — sabar tana jera aikin. Abokin ciniki ya kamata ya bincika matsayin ko dawo daga baya.

Buƙatar ta yi nasara, amma wani tsaka-tsaki (kamar tsaka-tsakin ajiya ko sauyawa) ya canza kaya daga sabar asali — misali, sake matsa hotuna. Ba a saba gani a aikace ba.

Ana amfani da shi sau da yawa don ayyukan DELETE ko sabunta PUT waɗanda ba sa buƙatar mayar da jiki. Abokin ciniki bai kamata ya bar shafin da yake a kai ba.

Kamar 204, ba a mayar da jiki ba — amma an ƙara gaya wa abokin ciniki ya sake saita fom ko ganin da ya samar da buƙatar (misali, share filayen fom don shigarwa ta gaba).

Amsa ga buƙatar Range. Ana amfani da ita ta masu kunna bidiyo da masu sarrafa saukewa don ci gaba da saukewar da ta tsaya ko watsa manyan fayiloli.

WebDAV: jikin XML yana bayar da rahoton sakamakon ayyuka da dama daban-daban — misali, matsar taro inda wasu abubuwa suka yi nasara wasu kuma suka gaza.

WebDAV: ana amfani da shi a cikin amsoshin 207 Multi-Status don guje wa maimaita lissafin membobin tarin ɗaya lokacin da haɗe-haɗe suka haifar da madauki.

Delta encoding: sabar tana mayar da bambanci daga sigar da ta gabata maimakon cikakken albarkatun, don adana bandwidth. Ba a cika amfani da shi ba.

Sabar tana bayar da zaɓuɓɓuka da yawa (misali, salo ko harsuna daban-daban) kuma ya kamata mai amfani ya zaɓi ɗaya. Ba a cika amfani da shi ba, domin sarrafa yarjejeniyar abun ciki ta atomatik yakan magance wannan.

Yi amfani da wannan don sauye-sauyen URL na dindindin — injunan bincike za su sabunta fihirisarsu. Ikon SEO yana ƙaura zuwa sabon URL ɗin.

Yana nuna cewa juyawar ba ta dindindin ba ce. Adanawa (caching) ba ta da tsauri kamar 301. Yi amfani da shi don abubuwa kamar 'ana buƙatar shiga, ana juyawa zuwa /login'.

Ana amfani da shi bayan aikawar POST — amsar tana cewa 'POST ɗinka ya yi aiki, duba wannan GET URL don sakamakon'. Burauzoji koyaushe suna yin GET ga sabon URL.

Amsa ga buƙata mai sharaɗi (tare da headers ɗin If-None-Match ko If-Modified-Since). Yana adana bandwidth — ba a mayar da jiki (body) ba.

Idan na asali POST ne, juyawar ma tana amfani da POST. Madadin zamani na 302 lokacin da riƙe hanyar ke da muhimmanci.

Madadin zamani na 301 idan kana son buƙatun POST su kasance POST bayan juyawar.

Abubuwan da suka fi haddasawa: JSON mara kyau a jiki, sigogin bincike marasa inganci, ko rasa filayen da ake buƙata. Duba jikin buƙatar da headers.

Dole ne mai amfani ya haɗa da bayanan tantancewa (header ɗin Authorization, cookie, token). 'Unauthorized' kalma ce marar daidai — ainihin ma'anarta ita ce 'ba a tantance ba'.

Da farko an tsara shi don biyan kuɗi na dijital. Amfani na zamani: API sukan mayar da 402 lokacin da mai amfani ya wuce adadin da aka biya.

Ya bambanta da 401 — mai amfani YA shiga, amma asusunsa ba shi da izinin wannan albarkatun. Duba dabarun rawa/izini.

Ko dai URL ba daidai ba ne, an goge albarkatun, ko kuwa bai taɓa wanzuwa ba. Wani lokaci sabobi kan mayar da 404 don ɓoye cewa 403 zai fi dacewa.

Misali, buƙatar GET zuwa wurin da ke karɓar POST kaɗai. Amsar ya kamata ta haɗa da header ɗin Allow wanda ke lissafa hanyoyin da suka dace.

Mai amfani ya nemi nau'in abun ciki, harshe, ko sigar rufewa (ta Accept, Accept-Language, Accept-Encoding) da sabar ba za ta iya biya ba. Yawancin sabobi suna tsallake shawarwari masu tsauri suna mayar da tsohon zaɓi maimakon.

Kamar 401, amma proxy ne ke bayarwa: mai amfani dole ya aika bayanan Proxy-Authorization. Ana ganin wannan a hanyoyin sadarwa na kamfanoni masu proxy na tantancewa.

Mai amfani ya ɗauki lokaci mai yawa wajen aika jikin buƙatar ko ya bar haɗin ba tare da aiki ba. A sake gwada buƙatar.

Yawanci ana mayar da shi don rikice-rikicen gyara na lokaci guda ko ƙirƙirar albarkatu masu kwafi (misali, ƙirƙirar mai amfani da imel da ya riga ya wanzu).

Ya fi ƙarfi da 404 — sabar ta sani a fili cewa albarkatun SUN taɓa wanzuwa amma an goge su har abada. Injunan bincike za su cire su daga fihirisa.

An ƙi buƙatar saboda babu header ɗin Content-Length kuma sabar ba ta karɓar jikkuna marasa sanannen tsawo. A ƙara header ɗin sannan a sake gwadawa.

Ana mayar da shi lokacin da headers masu sharaɗi kamar If-Match ko If-Unmodified-Since suka gaza — yawanci kulle-kullen kyautatawa (optimistic locking): wani ya canza albarkatun tun bayan sigar da kake da ita. A sake dawo da sabon bayani a sake gwadawa.

Yawanci yana faruwa lokacin ɗora manyan fayiloli. Saitunan sabar (nginx, apache) suna saita iyakar girman jiki. Duba saitunan sabar.

Yawanci ana haifar da shi ta hanyar dogayen kirtani na bincike (misali, ɓoye bayanai a GET). A canza zuwa jikin POST, ko a ƙara iyakar sabar idan kana da ikon yin hakan.

Misali, aika application/xml zuwa sabar da ke karɓar application/json kaɗai. A saita header ɗin Content-Type daidai.

Header ɗin Range yana neman wani ɓangare da fayil ɗin ba shi da shi — misali, ci gaba da zazzagewa bayan ƙarshen fayil ɗin. Amsar ya kamata ta haɗa da Content-Range mai ainihin girman.

Ana aika shi lokacin da sabar ba ta goyi bayan Expect: 100-continue ba. Wasu abokan ciniki suna aika wannan header ɗin ta tsohuwa akan manyan POST; kashe shi yakan warware kuskuren.

Barkwancin ranar Wawaye ta Afrilu daga 1998 (RFC 2324). Wasu API na gaskiya suna amfani da shi don barkwanci ko don nuna wurare da ba a amfani da su. Kada a yi amfani da shi wajen samarwa.

Yakan faru tare da sake amfani da haɗin HTTP/2: buƙatar ta kai ga sabar da ba a saita ta don sunan wurin da aka nufa ba. Mai amfani ya kamata ya sake gwadawa a sabon haɗi.

Misali, an fassara JSON daidai amma wani fili da ake buƙata ya ɓace, ko darajar filin ta wuce iyaka. Ana ganin wannan sau da yawa a amsoshin tabbatarwa na REST API.

WebDAV: wani abokin ciniki daban ya kulle albarkatun tushe ko na ƙarshe, don haka aikin ba zai iya ci gaba ba. A jira a sake sakin kullin ko a karya shi da tokin da ya dace.

WebDAV: a cikin sarkar ayyuka masu dogaro da juna, wani aiki na baya ya gaza, don haka ba a yi wannan ba. Duba gazawar da ta gabata don ainihin dalili.

Yana da alaƙa da TLS 1.3 0-RTT (early data): sabar ba za ta ɗauki haɗarin sarrafa buƙatar da ana yiwuwa an sake aikawa da ita ba. Mai amfani ya kamata ya sake gwadawa bayan handshake ya cika.

Sabar ta ƙi hidimar buƙatar ta yarjejeniya ta yanzu amma za ta yi bayan haɓakawa — amsar ta haɗa da header ɗin Upgrade wanda ke suna yarjejeniyar da ake buƙata.

Sabar tana buƙatar headers masu sharaɗi (kamar If-Match) don hana rikice-rikicen sabuntawa da suka ɓace. A samo albarkatun, a kama ETag ɗinsa, sannan a sake aikawa da If-Match.

A jinkirta. Amsar ya kamata ta haɗa da header ɗin Retry-After wanda ke nuna lokacin da za a sake gwadawa. Ana ganin wannan sau da yawa a API masu iyakar buƙatu.

Ko dai header ɗaya ko jimillar girman headers ya wuce iyaka — mafi yawa saboda manyan cookies. A share cookies ko a rage abin da app ɗinka ke adanawa a cikinsu.

An toshe albarkatun saboda dalilan shari'a — takunkumi, umarnin kotu, ko dokoki na yanki. Lambar tana nuni ga littafin Fahrenheit 451.

Wani babban kuskure na sabar da ba a bayyana ba. Duba log ɗin sabar don ainihin dalili: keɓancewa da ba a sarrafa ba, kuskuren bayanai, da sauransu.

Misali, sabar ba ta gane hanyar HTTP ba. Ba safai ake gani ba a aikace — ana ganin 405 ne fiye da haka.

Ana ganin wannan sau da yawa a tsarin microservice. Load balancer ko reverse proxy ɗinka ya samu amsa mara tsari daga sabis na baya.

Ko dai an rufe don gyara ko kuwa an cika ta. Amsar ya kamata ta haɗa da header ɗin Retry-After. Ana ganinsa sau da yawa yayin aiwatarwa.

Sabis na baya bai amsa da sauri isashe ba. Duba lafiyar sabis na baya da saitunan lokacin ƙarewa.

Babbar sigar HTTP na buƙatar ba a goyi bayanta a sabar ba. Ba a taɓa ganin wannan tare da abokan ciniki na zamani ba.

Shawarwarin abun ciki bayyananne ya ƙare a madauki: nau'in da aka zaɓa shi kansa an saita shi don shawarwari. Yana nuna kuskuren saitin sabar.

Asalinsa na WebDAV ne amma wani lokaci ana amfani da shi a sabobi na gaba ɗaya. Yana nufin sabar ba za ta iya adana buƙatar ba saboda ƙarancin ajiya.

WebDAV: sarrafa buƙatar Depth: infinity ya shiga cikin madauki (misali, haɗe-haɗe masu madauki). An dakatar da aikin.

Daga tsohon tsarin HTTP Extension Framework: sabar tana buƙatar ƙarin bayani kafin ta iya biyan buƙatar. A zahiri ba a amfani da shi a yanar gizo ta zamani.

Ana amfani da shi ta hanyoyin sadarwar da suka kama (captive portals) (WiFi na otel/filin jirgin sama) don nuna cewa mai amfani dole ya shiga hanyar sadarwa kafin samun damar shafuka na waje.