Kuhlelo lokusebenza oludala lwe-HttpClient 4.2.2, umhlinzeki wemininingwane yokuqinisekisa kanye ne-cache yokuqinisekisa benza imisebenzi ehlukene. Umhlinzeki unikeza i-akhawunti; i-cache ivumela uhlelo lokuqinisekisa oluhlelwe ngamabomu kusengaphambili ukuthi lubambe iqhaza ngaphambi kokufika enye inselelo.

Kusakhiwo esidala se-BasicScheme esiqondene ne-proxy, ukudluliswa kubukeka kanje:

AuthCache cache = new BasicAuthCache();
cache.put(proxy, new BasicScheme(ChallengeState.PROXY));

HttpContext context = new BasicHttpContext();
context.setAttribute(ClientContext.AUTH_CACHE, cache);
HttpResponse response = client.execute(request, context);

Le ngxenye icabanga ukuthi i-client isivele inendlela ye-proxy efanele kanye nomhlinzeki wemininingwane yokuqinisekisa. I-proxy iyi-HttpHost yayo, futhi i-request umsebenzi wangempela. Ukhiye we-cache kufanele uchaze lowo mxhumanisi, hhayi iwebhusayithi okuyiwa kuyo.

Dlulisa umongo ogcwalisiwe ku-execute. Ukuwakahlela bese usebenzisa ukulayisha ngokweqile okudala omunye umongo kushiya i-cache ngaphandle kokushintshana. Emisebenzini elandelayo okufanele yabelane ngaleyo simo yokuqinisekisa, gcina umongo ofanele esikhundleni sokwakha kabusha ongenalutho ngaso sonke isikhathi.

Isimo esicacile se-PROXY singesase-API esidala. I-TARGET iphathelene nokuqinisekisa kwendawo okuyiwa kuyo. Izizukulwane ezintsha ze-HttpClient zishintshe amaphakethe kanye ne-API yokuqinisekisa, ngakho sebenzisa lokhu njengomhlahlandlela wokunakekela wokhodi olukhona lwe-4.2, hhayi njengendlela ye-client entsha.

Ukushintshana okuvamile okuqhutshwa inselelo kusengaba ngcono. Hlanyela ukuqinisekisa kwe-Basic kuphela ku-proxy eyaziwayo nehlosiwe, futhi sebenzisa noma khulula impendulo ngayinye ngaphambi kokuthi umsebenzi olandelayo udinge uxhumano lwayo. Umphumela owusizo i-akhawunti kanye nohlelo olugciniwe oluxhunywe ekwenziweni okuthumela ngempela isicelo.

Izihloko ezihlobene