BThddlZddlZddlmZddlmZmZddlmZm Z eje Z GddZ Gdd eZy) N)BytesIO) parse_qslurlparse)CaseInsensitiveDict_is_nonsequence_iteratorceZdZdZdZedZejdZedZejdZdZ edZ ed Z ed Z ed Z ed Zed ZedZdZdZdZedZy)Requestz, VCR's representation of a request. c<||_||_t|d|_t ||_|jr|j |_n$|j rt||_n||_||_ tjd|jy)NreadzInvoking Request %s) methodurihasattr _was_filer _was_iterr bodylistheaderslogdebug)selfr rrrs ]/var/www/catia.catastroantioquia-mas.com/valormas/lib/python3.12/site-packages/vcr/request.py__init__zRequest.__init__sq  v.1$7 >> DI ^^T DIDI  '2c|jSN)_headersrs rrzRequest.headerss }}rcHt|ts t|}||_yr) isinstance HeadersDictrrvalues rrzRequest.headers"s%-&E rc|jrt|jS|jrt |jS|jSr)rr_bodyriterrs rrz Request.body(s8 >>4::& & >> # #zzrcTt|tr|jd}||_y)Nzutf-8)r strencoder%r"s rrz Request.body0s! eS !LL)E rcZtjdtd||j|<y)NzKRequest.add_header is deprecated. Please assign to request.headers instead.) stacklevel)warningswarnDeprecationWarningr)rkeyr#s r add_headerzRequest.add_header6s' Y  " Src@t|jjSr)rrschemers rr3zRequest.scheme>s!(((rc@t|jjSr)rrhostnamers rhostz Request.hostBs!***rct|j}|j}| ddd|j}|S|S#t$rY|SwxYw)NiP)httpshttp)rrportr3KeyError)r parse_urir;s rr;z Request.portFs\TXX& ~~ < !$b1)2B2BC t    s; AAc@t|jjSr)rrpathrs rr?z Request.pathQs!&&&rcht|jj}tt |Sr)rrquerysortedr)rqs rrAz Request.queryUs% TXX  $ $il##rc|jSr)rrs rurlz Request.url[s xxrc|jSr)r3rs rprotocolzRequest.protocol`s {{rc<d|jd|jdS)Nz )r rrs r__str__zRequest.__str__dsDKK=488*A66rc"|jSr)rJrs r__repr__zRequest.__repr__gs||~rc |j|j|j|jj Dcic] \}}||g c}}dScc}}w)N)r rrr)r rrritems)rkvs r_to_dictzRequest._to_dictjsLkk88II+/<<+=+=+?@41aA3@   AsA ctdi|S)N)r )clsdcts r _from_dictzRequest._from_dictrs~~rN)__name__ __module__ __qualname____doc__rpropertyrsetterrr1r3r6r;r?rArErGrJrLrQ classmethodrVrSrrr r s 3 ^^  [[ "))++''$$ 7 rr c"eZdZdZfdZxZS)r!aY There is a weird quirk in HTTP. You can send the same header twice. For this reason, headers are represented by a dict, with lists as the values. However, it appears that HTTPlib is completely incapable of sending the same header twice. This puts me in a weird position: I want to be able to accurately represent HTTP headers in cassettes, but I don't want the extra step of always having to do [0] in the general case, i.e. request.headers['key'][0] In addition, some servers sometimes send the same header more than once, and httplib *can* deal with this situation. Furthermore, I wanted to keep the request and response cassette format as similar as possible. For this reason, in cassettes I keep a dict with lists as keys, but once deserialized into VCR, I keep them as plain, naked dicts. ct|ttfr|d}|jj |j }|r|d}t |||y)Nr)r tupler_storegetlowersuper __setitem__)rr0r#old __class__s rrezHeadersDict.__setitem__sO eeT] +!HEkkoociik* a&C C'r)rWrXrYrZre __classcell__)rgs@rr!r!ws& ( (rr!)loggingr-ior urllib.parserrutilrr getLoggerrWrr r!rSrrrns@,?g!iiX(%(r