Lungiselela i-SOCKS5 proxy ye-Azure Blob Python client

Lungiselela i-Requests session enikeziwe ngokwayo, bese ugcina impilo yayo ngaphandle kwe-Blob client ehambisanayo nge-session_owner=False.

import requests
from azure.core.pipeline.transport import RequestsTransport
from azure.storage.blob import BlobServiceClient

with requests.Session() as session:
    session.trust_env = False
    session.proxies["https"] = "socks5h://proxy.example:1080"
    transport = RequestsTransport(session=session, session_owner=False)
    with BlobServiceClient(
        account_url=account_url,
        credential=credential,
        transport=transport,
    ) as client:
        pass

Yenza umsebenzi we-Blob ohlosiwe esikhundleni sika-pass, usebenzisa i-account_url ne-credential yohlelo lokusebenza. Izincikamizelo ze-SOCKS ezikhethekayo ze-Requests kumele zibe khona kakade. I-socks5h idlulisela i-DNS yendawo ekuyiwa kuyo ku-proxy. Endaweni yokugcina ye-Blob efinyeleleka esidlangalaleni lapho abalamuli bomphakathi bevunyelwe, uhlu lwe-proxy ye-SOCKS5 lunikeza abazakheli be-URL ye-proxy yesikhathi.

Setha i-trust_env kule session ukuze ulawule ukuhlanganiswa kwe-Requests nendawo. I-RequestsTransport isebenzisa ukuqaliswa kwendawo lapho idala isikhathi, hhayi lapho inikezwa esivele sikhona. Inani elicacile le-false livimbela okokufaka kwendawo ye-proxy ekuthatheni indawo yalo mzila.

Lokho kukhetha kuphinda kudeactivate ukukhethwa kwe-CA okususelwa endaweni. Uma kudingeka, nikeza i-connection_verify="/path/to/ca-bundle.pem" ku-RequestsTransport, nezimpande ezidingekayo zensizakalo yangempela.

I-Blob client ivalwa ngaphambi komongo we-session wangaphandle. I-session_owner=False ishiya ubunikazi kulelo blokhi langaphandle. Ubufakazi betoken obudalwe ngokwahlukile bungaba nokunye ukuthutha kwe-HTTP; buqalise futhi uma ukutholwa kwabo kudinga i-SOCKS.

Izihloko ezihlobene