Kungani i-APT ingasebenzisi i-CONNECT ekulandeni konke
Ukudluliswa kwe-HTTP okujwayelekile kanye nomhubhe we-HTTPS kusebenzisa izingxoxo ze-proxy ezihlukene. Isevisi esekela i-CONNECT kuphela ingase ingazisekeli izicelo ezikhiqizwa yisitoreji se-HTTP.
“I-proxy yamukela i-CONNECT” akusho ukuthi yamukela zonke izicelo i-APT ezizothumela.
Esitoreji se-HTTP esijwayelekile, i-APT ingasebenzisa ukudluliswa kwe-proxy ye-HTTP okujwayelekile: i-proxy ithola isicelo se-HTTP esikhomba insiza okuyiwa kuyo. Nge-HTTPS nge-proxy ye-HTTP, iklayenti ngokuvamile lakha umhubhe we-CONNECT, bese lixoxa ngesikhathi se-TLS sokuya kuyo ngalowo mhubhe.
| Indawo okuyiwa kuyo | Ingxoxo ejwayelekile ne-proxy ye-HTTP |
|---|---|
| Isitoreji se-HTTP | Dlulisa isicelo se-HTTP |
| Isitoreji se-HTTPS | CONNECT, bese kuba yi-TLS yokuya kuyo |
Isevisi eyamukela imihubhe kuphela ingase yenqabe isicelo esidluliswe ngokujwayelekile. I-HTTP 405 ifanele ukubhekwa ngendlela yangempela, umkhiphi wempendulo kanye nenqubomgomo ye-proxy; akufakazi ukuthi i-APT ayinakho ukusekelwa kwe-SOCKS noma ukuthi iphasiwedi yayo ayilungile.
Qhathanisa ukuziphatha okusekelwayo kwesevisi nedokhumenti yezokuthutha ye-APT kanye nencazelo ye-CONNECT. Sebenzisa isevisi egunyaziwe ehambisanayo noma i-URL yesitoreji esekelwayo. Ezitorejini zomphakathi lapho abalamuli bomphakathi bevunyelwe, uhlu lwe-proxy ye-HTTP lunikeza abazokwethulwa abazohlolwa ngokumelene nalezo zidingo. Ungacabangi ukuthi ukwengeza i-https:// ekhelini le-proxy kushintsha iphrothokholo yesitoreji noma kuguqula zonke izicelo zibe umhubhe.