Zeep yana bukatar proxy kafin ya karanta WSDL

Gina Zeep Client daga WSDL mai nisa na iya ɗauko wannan takarda da imports ɗinta nan take. Saita Transport da farko, maimakon sanya proxy bayan Client ya riga ya yi ƙoƙarin loda bayanin sabis ɗin.

from requests import Session
from zeep import Client
from zeep.transports import Transport

session = Session()
session.proxies.update({
    "http": "http://proxy.example.net:8080",
    "https": "http://proxy.example.net:8080",
})

transport = Transport(
    session=session,
    timeout=10,
    operation_timeout=30,
)
client = Client(wsdl_url, transport=transport)

wsdl_url shine ainihin URL na bayanin sabis ɗin. Idan wannan sabis ɗin da imports ɗinsa suna isa ga kowa kuma an yarda da proxy na jama'a, jerin proxy na HTTP yana ba da 'yan takara don URL ɗin proxy na zaman. Ci gaba da zaman da aka saita don ayyukan SOAP na gaba, sannan rufe shi idan aikin ya ƙare.

Transport.timeout yana sarrafa loda WSDL da XSD. operation_timeout yana sarrafa buƙatun HTTP na ayyukan sabis. Don haka lokacin ƙarewar metadata yayin gina Client wani mataki ne dabam da lokacin ƙarewar kiran hanya daga baya.

A wannan misalin haɗin muhalli na Requests yana ci gaba da aiki. Idan ƙimar proxy ta muhalli ta ci karo da hanyar da ake buƙata a fili, yi amfani da session.trust_env=False kuma bayar da CA bundle da saitunan tabbatarwa da ake buƙata a fili.

Duba URL na takardar da aka shigo da ita idan fara aikin har yanzu ya kasa. WSDL na matakin sama na iya lodawa cikin nasara yayin da schema da aka shigo da shi ke amfani da wani sunan mai masauki ko ka'idar manufa.