I-NO_PROXY ayilususi umzila we-Requests osobala
Hlukanisa ukucindezela ukutholakala kwe-proxy endaweni nokususa i-proxy enikezwe ngamabomu kumephu ye-Requests.
Lapho uhlelo lunikeza i-Requests inqubomgomo yalo ye-proxy, nikeza okukhishiwe okuqondile kuleyo nqubomgomo. Nge-Session ekhona kanye nocingo olunomkhawulo omncane:
direct_routes = {'http': '', 'https': ''}
response = session.get(url, proxies=direct_routes, timeout=15)Amavelu angenalutho asobala akhetha ukuhamba okuqondile kuma-scheme afanele. Hlola futhi ucingo lwangempela kanye namavelu aphansi e-Session kumazitshudeni abamukeli athile kakhulu; ukubhala ngaphezulu kwezinga le-scheme kuphela akususi umzila ohlukile oqondene nomamukeli.
Kungani ukufaka umamukeli ku-NO_PROXY kushiye i-proxy esobala endaweni yayo? Isixazululi se-Requests 2.34.2 sikhophisha imephu enikeziwe futhi sicabangela ukuthi ingabe imvelo kufanele igcwalise imibhalo engekho. Ukufana kokudlula kungacindezela lokho kutholakala ngaphandle kokususa umzila uhlelo olwawusunikezile.
Hlola imephu esetshenziswa yilo msebenzi ngaphambi kokufaka okukhishiwe kwelinye ungqimba. Gcina ukuqinisekiswa kwe-TLS kuvuliwe emzileni oqondile. Uma ukuhambisa kabusha kushintsha umzila futhi, hlola None uma kuqhathaniswa namavelu e-proxy angenalutho kukho konke lokho kuguquka. Iphutha lesitifiketi lapho liwubufakazi mayelana nokwethenjwa kwendawo ekuyiwa kuyo kuleyo ndlela, okuhlukile ekutheni i-proxy yakhethwa yini.