Me yasa APT ba ya amfani da CONNECT don kowane saukewa
Tura HTTP na yau da kullun da ramin HTTPS suna amfani da tattaunawar wakili daban-daban. Sabis ɗin CONNECT kawai ƙila ba zai goyi bayan buƙatun da rumbun HTTP ke samarwa ba.
“Wakilin yana karɓar CONNECT” ba ya nufin yana karɓar kowace buƙata da APT zai aika.
Don rumbun HTTP na yau da kullun, APT na iya amfani da tura wakilin HTTP na al'ada: wakilin yana karɓar buƙatar HTTP da ke gano albarkatun manufa. Don HTTPS ta wakilin HTTP, abokin ciniki yakan kafa ramin CONNECT, sannan ya tattauna zaman TLS na manufa ta cikinsa.
| Manufa | Tattaunawa ta al'ada da wakilin HTTP |
|---|---|
| Rumbun HTTP | Tura buƙatar HTTP |
| Rumbun HTTPS | CONNECT, sannan TLS na manufa |
Sabis ɗin da ke karɓar ramuka kawai na iya ƙin buƙatar da aka tura ta al'ada. HTTP 405 ya cancanci duba ainihin hanyar, mai ba da amsa da manufofin wakili; ba ya tabbatar da cewa APT ba shi da goyon bayan SOCKS ko kalmar sirrinsa ba daidai ba ce.
Kwatanta halin da sabis ɗin ke goyan bayansa da takardun jigilar APT da ma'anar CONNECT. Yi amfani da sabis ɗin da aka amince da shi mai jituwa ko URL na rumbun da aka goyi baya. Don rumbunan jama'a inda aka yarda da masu shiga tsakani na jama'a, jerin wakilan HTTP yana ba da 'yan takara don bincika su da waɗannan buƙatun. Kada ka ɗauka cewa ƙara https:// a adireshin wakili yana canza ka'idar rumbun ko yana mai da kowace buƙata rami.