Sanya manyan CONNECT na Go a kan Transport

Kan da aka ƙara a http.Request.Header yana bayyana buƙatar manufa. Sa'ad da HTTPS ke amfani da wakilin HTTP, transport ɗin yakan fara yin CONNECT. Manyan kan buƙatar manufa ba babbar hanyar API ta daidaita saiti ba ce don wannan musayar da ta gabata.

Don wani kan da ba ya canzawa wanda wakilinka ke buƙata, saita ProxyConnectHeader na transport:

transport := &http.Transport{
    Proxy: http.ProxyURL(proxyURL),
    ProxyConnectHeader: http.Header{
        "X-Proxy-Account": []string{"example-account"},
    },
}

A nan proxyURL ita ce URL ɗin ƙarshen da aka yi nazari. Kan ɗin misali ne kuma yana da amfani ne kawai lokacin da mai gudanar da wakilin ya bayyana irin wannan fili.

Don ƙimar da ake zaɓa ta kowace wakili ko manufa, yi amfani da GetProxyConnectHeader. Taron dawowa da aka rubuta yana karɓar URL ɗin wakili da makasudin CONNECT. Lokacin da wannan taron ba nil ba ne, ana watsi da filin ProxyConnectHeader da ba ya canzawa.

Ka riƙe ƙimomi a cikin iyakar da aka nufa. Alamar asusu ta wakili kaɗai tana cikin musayar wakili; ƙimar izinin gidan yanar gizo tana cikin buƙatar manufa. Idan taron dawowa ba zai iya samar da ƙimar musafaha da ake buƙata ba, mayar da kuskurensa maimakon aika buƙatar da aka saita daban cikin shiru.

Waɗannan saitunan suna daidaita yadda ake gudanar da CONNECT. Ba su ƙirƙira wata hanyar tabbatarwa ta musamman ba kuma ba su canza manufar shiga sabis ɗin wakili ba.