CONNECT timeouts na proxy bayan nasarar haɗin TCP
Gano lokacin da ke aiki yayin CONNECT maimakon ɗauka cewa haɗin TCP da ya cika ya kammala saitin ramin kuma.
Lokacin haɗin TCP ya yi aikinsa da zarar abokin ciniki ya haɗu da proxy. Jira na gaba—karɓar cikakkiyar amsar CONNECT—na iya kasancewa ƙarƙashin wani mai ƙididdige lokaci dabam.
Wataƙila proxy ɗin har yanzu yana haɗawa zuwa sama, yana musayar saƙonnin tabbatarwa ko yana jira wata sabis. Amsar yau da kullum ta gidan yanar gizon ba ta fara ba tukuna.
| Matakin ƙarshe da ya cika | Me har yanzu ake jira? |
|---|---|
| TCP ya haɗu da proxy | Musaƙar hannu ta proxy, haɗe da karɓar CONNECT |
| An karɓi CONNECT | TLS na manufa, lokacin da manufar ke amfani da shi |
| An aika buƙatar manufa | Amsar manufar |
Nemo mai ƙididdige lokacin da ke aiki yayin da mai haɗawa ke karantawa da rubuta wannan musaƙar hannu. Ƙayyadaddun da ake kira “response timeout” na iya aiki ne kawai bayan an kafa hanyar. Da HttpClient 5, bambanta ConnectionConfig da lokacin soket ɗinsa, saitin musaƙar hannu na TLS, da lokacin amsa a matakin buƙata. Yi amfani da saitin haɗin da ya dace ta hanyar mai sarrafawa da ainihin abokin ciniki ke amfani da shi. Tsofaffin ƙarni na Apache HttpClient suna amfani da API daban-daban, don haka tsohon guntun lamba ba ingantaccen taswirar waɗannan nauyin ba.
Riƙe ƙin CONNECT na ƙarshe a matsayin amsar proxy. Amsa mai nasara da ke biye da tsayawar TLS wani matakin gazawa ne. “TCP ya haɗu; babu cikakkiyar amsar CONNECT kafin lokacin saiti” ya bayyana matsalar daidai fiye da janar ɗin lokacin proxy.
Cikakken wa'adi na iya iyakance jiran mai kira tare da waɗannan iyakokin matakai. Idan ya ƙare, soke ko rufe aikin ta hanyar tsarin rayuwa da abokin ciniki ke goyon baya kafin wani yunƙuri ya cinye ƙarfin haɗi.