Sababta APT uusan u isticmaalin CONNECT soo dejinta kasta
Gudbinta HTTP caadiga ah iyo tunnel-ka HTTPS waxay isticmaalaan wada-tashiin proxy oo kala duwan. Adeeg ku saleysan CONNECT oo kaliya ayaa laga yaabaa inuusan taageerin codsiyada kaydka HTTP soo saaro.
“Proxy-gu wuxuu aqbalaa CONNECT” macnaheedu maaha inuu aqbalo codsi kasta oo APT soo diro.
Kaydka HTTP caadiga ah, APT waxa uu isticmaali karaa gudbinta proxy HTTP caadiga ah: proxy-gu waxa uu helaa codsi HTTP oo tilmaamaya kheyraadka loo socdo. HTTPS ee loo maro proxy HTTP, macmiilku waxa uu caadi ahaan dhisaa tunnel CONNECT, ka dibna wuxuu ku wada xaajoodaa fadhiga TLS ee loo socdo.
| Ujeeddo | Wada-tashiin caadi ah oo lala yeesho proxy HTTP |
|---|---|
| Kaydka HTTP | Gudbi codsi HTTP |
| Kaydka HTTPS | CONNECT, ka dib TLS-ka loo socdo |
Adeeg aqbalaya tunnel-kaliya ayaa laga yaabaa inuu diido codsi caadi ah oo la gudbiyay. HTTP 405 waxa uu mudan yahay in la eego habka dhabta ah, soo saaraha jawaabta iyo siyaasadda proxy-ga; ma caddeeyo in APT uusan taageero SOCKS lahayn ama in furaha sirta ah uu khaldan yahay.
Isbarbardhig hab-dhaqanka la taageeray ee adeegga iyo dukumentiyada gaadiidka APT iyo macnaha CONNECT. Isticmaal adeeg la ansixiyay oo waafaqsan ama URL kayd la taageeray. Kaydka dadweynaha halkaas oo dhexdhexaadiyeyaasha dadweynaha la oggolaaday, liiska proxy HTTP waxa uu bixiyaa musharrixiinta in lagu hubiyo shuruudahaas. Ha u malayn in ku darista https:// ciwaanka proxy-ga ay beddesho borotokoolka kaydka ama ay codsi kasta u rogtay tunnel.