Tixraaca Koodhadhka HTTP Status oo Bilaash ah

Waxaa loo isticmaalaa codsiyada leh Expect: 100-continue. Serverku wuxuu xaqiijinayaa inuu diyaar u yahay inuu helo jidhka ka hor intaan macmiilku dirin. Dhif ayaa ku muuqda app-yada web ee casriga ah.

Badiyaa waxaa loo isticmaalaa kor-u-qaadista WebSocket — macmiilku wuxuu codsadaa Upgrade: websocket serverkuna wuxuu ka jawaabaa 101 si uu u bedelo.

Jawaab WebDAV ah oo ku-meel-gaar ah oo loo diro si looga hortago in macmiilku wakhtiga dhammaado inta lagu jiro howlaha dheer. Waa la eryay — serverrada casriga ah ma ay diri karaan.

Wuxuu u ogolaadaa serverrada inay diraan madaxyada Link (preload/preconnect) inta jawaabta kama dambaysta ah la diyaarinayo, si biraawsarrada u bilaabaan soo qaadista alaabta muhiimka ah sida ugu dhaqsaha badan.

Jawaabta caadiga ah ee guusha. Macnaheedu wuxuu ku xiran yahay habka HTTP: GET → alaab ayaa la soo celiyay, POST/PUT → ficilku wuu dhammaaday.

Caadi ahaan waxay ka dhacdaa POST ka dib. Jawaabtu waa inay ku jirtaa madax Location ah oo u tilmaamaya URL-ka alaabta cusub.

Loogu talagalay hawlaha async ah — serverku wuxuu safka geliyaa shaqada. Macmiilku waa inuu weydiiyo xaalada endpoint-ka ama mar kale hubiyo.

Codsigu wuu guulaystay, laakiin dhexdhexaadiye (sida proxy kaydinta ama bedelka) ayaa bedelay xamuulka ka yimid serverka asalka ah — tusaale ahaan, dib-u-cadaadinta sawirrada. Dhif ayaa ku dhacda.

Badiyaa waxaa loo isticmaalaa hawlaha DELETE ama cusboonaysiinta PUT ee aan u baahnayn inay soo celiyaan jidh. Macmiilku waa inuusan ka tegin bogga hadda.

Sida 204, jidh lama soo celiyo — laakiin macmiilka waxaa sidoo kale loo sheegayaa inuu dib-u-dejiyo foomka ama muuqaalka soo saaray codsiga (tusaale, nadiifi meelaha foomka gelitaanka xiga).

Jawaab codsi Range ah. Waxaa isticmaala daawadayaasha video iyo maamulayaasha soo dejinta si ay dib ugu bilaabaan soo dejinta kala go'day ama u sii daayaan faylasha waaweyn.

WebDAV: jidh XML ah ayaa si madax-bannaan u soo warramaya natiijada hawlo-yar dhowr ah — tusaale ahaan dhaqaaqid kooxeed oo qaar ka mid ah alaabtu ay guulaysteen kuwa kalena ay fashilmeen.

WebDAV: waxaa loo isticmaalaa gudaha jawaabaha 207 Multi-Status si looga fogaado in mar walba la soo koobo xubnaha isla ururka marka isku-xidhku (bindings) sameeyo wareeg xaddidan la'aan ah.

Delta encoding: server-ku wuxuu soo celiyaa farqiga (diff) laga sameeyay nooc hore halkii uu soo celin lahaa khayraadka oo dhan, taasoo keydisa bandwidth-ka. Aad ayaa loo isticmaalaa marar dhif ah.

Server-ku wuxuu bixiyaa xulashooyin badan (tusaale ahaan, qaabab ama luqado kala duwan) markaasna macmiilku waa inuu doortaa mid. Aad looma isticmaalo, sababtoo ah wax-ka-doorashada content-ka otomaatigga ah ayaa badanaa xallisa tan.

Isticmaal marka URL-ku si joogto ah u beddelo — makhaayadaha raadinta ayaa cusboonaysiin doona kaydkooda. Awoodda SEO-da waxay u wareegtaa URL-ka cusub.

Waxay tusaysaa in redirect-ku aanu ahayn mid joogto ah. Kaydinta (caching) ayaa ka yar 301. Isticmaal xaaladaha sida 'gelitaanka baa loo baahan yahay, waxaa lagu wareejinayaa /login'.

Waxaa loo isticmaalaa ka dib marka POST la gudbiyo — jawaabtu waxay tidhaahdaa 'POST-kaagu wuu shaqeeyay, arag URL-kan GET ah natiijada'. Browsers-ku had iyo jeer wuxuu GET u sameeyaa URL-ka cusub.

Jawaab loogu talagalay codsi shuruudaysan (leh header-ka If-None-Match ama If-Modified-Since). Waxay keydisaa bandwidth — body lama soo celiyo.

Haddii kii asalku ahaa POST, redirect-ku sidoo kale wuxuu isticmaalaa POST. Waa beddelka casriga ah ee 302 marka ilaalinta habku muhiim tahay.

Beddelka casriga ah ee 301 marka aad rabto in codsiyada POST ay POST ahaadaan ka dib redirect-ka.

Sababaha caadiga ah: JSON qaab-xun oo ku jira body-ga, query parameters aan sax ahayn, ama goobo waajib ah oo maqan. Hubi body-ga codsiga iyo headers-ka.

Macmiilku waa inuu ku daraa caddaymaha aqoonsiga (Authorization header, cookie, token). 'Unauthorized' waa magac khaldan — dhab ahaantii macnaheedu waa 'aan la aqoonsan'.

Asal ahaan waxaa loogu talagalay lacag-bixinada dijitaalka ah. Isticmaalka casriga ah: API-yadu mararka qaarkood waxay soo celiyaan 402 marka isticmaalaha uu dhaafay quotada uu lacagta bixiyay.

Way ka duwan tahay 401 — isticmaaluhu WUXUU ku jiraa gelitaanka, laakiin akoonkiisu uma laha oggolaansho khayraadkan. Hubi habraaca doorka/oggolaanshaha.

Ama URL-ku waa qalad, khayraadka waa la tirtiray, ama waligiis ma jirin. Marmarka qaarkood server-yadu waxay soo celiyaan 404 si ay u qariyaan in 403 ay saxsan tahay.

Tusaale ahaan, codsi GET ah oo loo diray endpoint aan aqbalin PO ST mooyee. Jawaabtu waa inay ku jirto header-ka Allow oo taxaya hababka sax ah.

Macmiilku wuxuu codsaday nooc content ah, luqad, ama encoding (via Accept, Accept-Language, Accept-Encoding) oo server-ku aan bixin karin. Server-yo badan ayaa ka boodaya wax-ka-doorashada adag oo bixinaya mid caadi ah beddelkeeda.

La mid ah 401, laakiin waxaa soo diraya proxy: macmiilku waa inuu dhiibo caddaymaha Proxy-Authorization. Waxaa laga arkaa shabakadaha shirkadaha oo leh proxy-yo aqoonsan.

Macmiilku wuxuu ku qaatay wakhti dheer inuu diro body-ga codsiga ama wuxuu ka dhigay isku xirku shil (idle). Isku day mar kale.

Caadi ahaan waxaa loo soo celiyaa iskhilaafyada wax-ka-beddelka isku mar ah ama abuurista khayraad nuqul ah (tusaale ahaan, isticmaale abuurista email horey u jiray).

Ka xoog badan 404 — server-ku si toos ah ayuu u ogyahay in khayraadku HORE u jiray laakiin si joogto ah loo saaray. Makhaayadaha raadinta ayaa ka saari doona kaydkooda.

Codsiga waa la diiday sababtoo ah wuu ka maqnaa header-ka Content-Length oo server-ku diiday body-yo dhererkoodu aan la ogayn. Ku dar header-ka oo isku day mar kale.

Waxaa la soo celiyaa marka headers shuruudaysan sida If-Match ama If-Unmodified-Since ay fashilmaan — inta badan waa xulqaanka fiican (optimistic locking): qof kale ayaa beddelay khayraadka tan iyo noocaagii. Dib u soo hel oo isku day.

Caadi ah marka la soo shubayo faylal waaweyn. Habaynta server-ka (nginx, apache) ayaa dejisa cabbirka ugu weyn ee body-ga. Hubi habaynta server-kaaga.

Badanaa waxaa keena query strings aad u dheer (tusaale, encoding-ka xogta gudaha GET). U beddel body-ga POST, ama kordhi xadka server-ka haddii aad gacanta ku hayso.

Tusaale ahaan, application/xml oo loo diray server aan aqbalin application/json mooyee. Si sax ah u deji header-ka Content-Type.

Header-ka Range wuxuu codsanayaa qayb aan faylku lahayn — tusaale ahaan, dib-u-soo-shubidda faylka ka dib intii uu dhammaaday. Jawaabtu waa inay ku jirto Content-Range oo tusaya cabbirka dhabta ah.

Waxaa la soo diraa marka server-ku aanu taageerin Expect: 100-continue. Macmiilo qaarkood waxay si toos ah u diraan header-kan gudaha POST-yada waaweyn; iska damin karaa lagaga baxo qaladkan.

Waa mid ka mid ah kaftanka Maalinta Nacasyada 1998 (RFC 2324). API-yo dhab ah ayaa mararka qaarkood isticmaala kaftan ahaan ama si loo calaamadiyo endpoint-yo aan hadda la isticmaalin. Uma habboona isticmaal dhab ah.

Waxaa caadi ah dib-u-isticmaalka xiriirka HTTP/2: codsigu wuxuu gaadhay server aan loo habayn magaca goobta (hostname) la beegsanayo. Macmiilku waa inuu isku dayo xiriir cusub.

Tusaale ahaan, JSON-ka si sax ah ayaa loo fasiray laakiin goob waajib ah ayaa maqnayd, ama qiimo goob ayaa ka baxsanayd xadka. Waa mid caadi ah jawaabaha xaqiijinta REST API.

WebDAV: khayraadka isha ama meesha loo wado ayaa uu xidhay macmiil kale, sidaa darteed howsha lama sii wadi karo. Sug ilaa xidhitaanku furmo ama ku jebi lakab (token) sax ah.

WebDAV: silsilad ficilo isku xiran, mid hore ayaa fashilmay, sidaa darteed tan lama fulin. Eeg fashilkii hore si aad u ogaato sababta asalka ah.

Wuxuu la xiriiraa TLS 1.3 0-RTT (xogta hore): server-ku ma qaadanayo halista uu geeyo codsi laga yaabo in dib loo diro. Macmiilku waa inuu isku dayo mar kale ka dib marka handshake-ku dhammaado.

Server-ku wuu diiday inuu ku adeego codsiga protocol-ka hadda jira laakiin wuu samayn doonaa ka dib kor-u-qaad — jawaabtu waxay ku jirtaa header-ka Upgrade oo magacaabaya protocol-ka loo baahan yahay.

Server-ku wuxuu codsanayaa headers shuruudaysan (sida If-Match) si looga hortago iskhilaafyada wax-ka-beddel lumay. Soo hel khayraadka, qabo ETag-kiisa, dabadeedna dib u dir isla adigoo isticmaalaya If-Match.

Gaabi. Jawaabtu waa inay ku jirto header-ka Retry-After oo sheegaya waqtiga la isku dayi karo mar kale. Waa caadi API-yada leh quotas codsi.

Ama hal header ama wadarta cabbirka headers-ka ayaa dhaafay xadka — inta badan waxaa keena cookies aad u waaweyn. Nadiifi cookies-ka ama yaree waxa app-kaagu ku kaydiyo gudahooda.

Khayraadka waa la xannibay sababo sharci awgood — cesenso, amarro maxkamadeed, ama sharciyo gobolku sameeyay. Lambarkani wuxuu tixraacayaa buugga Fahrenheit 451.

Waa qeybta guud ee khaladaadka dhinaca server-ka. Hubi server logs si aad u aragto sababta dhabta ah: exception aan la maareyn, khalad database, iwm.

Tusaale ahaan, server-ku ma aqoonsan habka HTTP-ga. Aad bay u dhif tahay — badanaa waxaad arki doontaa 405.

Waa caadi maamulka microservices. Load balancer-kaaga ama reverse proxy-gaaga ayaa ka helay jawaab qaab-xun oo ka timid adeegga backend-ka.

Ama waa dayactir ama waa culays xad-dhaaf ah. Jawaabtu waa inay ku jirto header-ka Retry-After. Badanaa waxaa la arkaa intii deploy-yo socdaan.

Adeegga backend-ku si degdeg ah uma jawaabin. Hubi caafimaadka adeegga sare iyo habaynta wakhtiyada sugitaanka.

Nooca weyn ee HTTP-ga codsigu ma taageerto server-ku. Marar aad u dhif ah ayaa lagu arkaa macmiilada casriga ah.

Wax-ka-doorashada content-ka bannaanka ah waxay ku dhammaatay wareeg: nooca la doortay isla markaana ayaa laftiisu loo habeeyay inuu sameeyo wax-ka-doorasho. Waxay muujinaysaa khalad habaynta server-ka.

Asal ahaan waxaa loo sameeyay WebDAV laakiin mararka qaarkood waxaa isticmaala server-yo guud. Macnaheedu waa in server-ku uu awoodi waayo inuu keydiyo codsiga xaddidaadaha kaydka darteed.

WebDAV: habaynta codsi Depth: infinity ayaa gashay wareeg (tusaale, isku-xidho wareegsan). Howshii waa la joojiyay.

Waxaa laga soo qaatay HTTP Extension Framework-kii la iska daayay: server-ku wuxuu u baahan yahay macluumaad dheeri ah ka hor inta uu buuxin karo codsiga. Dhab ahaantii lama isticmaalo internetka casriga ah.

Waxaa isticmaala captive portals (WiFi-ga huteelada/madaarada) si loo tuso in isticmaaluhu ay tahay inuu ku galo shabakadda ka hor inta uusan booqan bogagga dibadda.