Lungisa i-proxy yeklayenti le-YouTube .NET nge-HttpClientFactory.ForProxy
Sebenzisa i-Google.Apis.Http.HttpClientFactory.ForProxy kusiqalisi sesevisi esikhundleni sokushintsha isiphathi sangaphakathi sekhayenti ye-YouTube ngemva kokwakhiwa.
I-Google.Apis ihlinzeka ngefekthri yokwakha amaklayenti e-HTTP ane-IWebProxy. Yinike lapho wakha isevisi ekhiqiziwe:
var proxy = new System.Net.WebProxy("http://proxy.example:8080");
proxy.Credentials = new System.Net.NetworkCredential(
proxyUser, proxyPassword);
using var youtube = new Google.Apis.YouTube.v3.YouTubeService(
new Google.Apis.Services.BaseClientService.Initializer
{
ApplicationName = "ExampleVideoClient",
ApiKey = apiKey,
HttpClientFactory =
Google.Apis.Http.HttpClientFactory.ForProxy(proxy)
});Isibonelo sisebenzisa ukufinyelela kokhiye we-API emsebenzini wedatha yomphakathi osekelwe. Shiya ukwabiwa kwezimpawu zokufakaza zeproxy ku-proxy engenakho ukuqinisekiswa. Kulelo gatsha ledatha yomphakathi, khetha ingeno ye-HTTP kusuka kuhlu lwama-proxy e-HTTP uma abaxhumanisi bomphakathi bevunyelwe. I-akhawunti yeproxy nokhiye we-API basebenza izindawo zokugcina ezihlukene.
Ku-Google.Apis 1.73.0, i-BaseClientService.Initializer.HttpClientFactory iyihuku lokwakha elisekelwe. I-ForProxy ibeka iproxy enikeziwe kumaklayenti adalwe yileyo fekthri. Ukwakhiwa kwezicelo, ukulandelana kanye nengxenye esele ye-SDK pipeline kuhlala kusevisi.
Lungisa lokhu ngaphambi kokuthumela izicelo. Ukushintsha i-MessageHandler.InnerHandler kuklayenti elakhiwe akudingekile kuleli cala futhi kungalahla ezinye izinketho zesiphathi.
Imibhalo yokufakaza ye-OAuth ingathola noma ivuselele ithokheni yayo ngohlelo lwayo lwe-HTTP. Ukusetha ifekthri yesevisi akunqumi ukuthi imibhalo eyakhiwe ngokwehlukana ithola kanjani amathokheni. Hlola leyo ndlela ngokwehlukana uma ukutholwa kwethokheni kuwumsebenzi ohlulekayo nge-proxy. Uma usebenzisa i-GoogleCredential, gcina ikhophi elenziwe umzila isuka ku-CreateWithHttpClientFactory walowo msebenzi wethokheni.