Buƙatun wakili na HTTP: cikakkun URL da kanun Host
Ka riƙe cikakken maƙasudin buƙata da filin Host su daidaita yayin yin buƙatar HTTP/1.1 ta wakili bayyananne.
Wane mahalli ne wannan buƙatar wakili ta HTTP/1.1 take nufi?
GET http://first.example/path HTTP/1.1
Host: second.exampleSaƙon bai daidaita ba. A cikin buƙata mai cikakken tsari da ake aikawa ga wakili, RFC 9112 na buƙatar darajar Host da aka tura ta fito daga maƙasudin buƙatar. Tura Host: first.example shine halin da ake tsammani.
A gwajin rukunin yanar gizo na ci gaba, ka riƙe sunan mahalli na albarkatun daidai a cikin URL da kuma a cikin ikon HTTP. Ka samar da taswirar suna-zuwa-adireshin da ake so a matakin da ke da alhakin warwarewa. Maye gurbin Host mai cin karo ba umarni mai ɗaukuwa ba ne don zaɓar backend.
HTTPS ya bambanta. Bayan buɗe ramin CONNECT na yau da kullum, TLS da musayar HTTP ta ciki suna faruwa a cikinsa. Wakili marar shiga tsakani ba zai iya sake rubuta wannan filin Host da aka ɓoye ba. Makomar CONNECT, sunan TLS da asalin takardar shaida sun kasance ayyuka daban-daban.
Share Via, Referer ko Cache-Control ba ya sulhunta hukumomin biyu. Yi rikodin siffar buƙatar da wurin da ka lura da kanun kafin ka tantance sake rubutun wakili.