kjJdZddlZddlZddlmZddlmZddlZddlm Z ddlm Z erddl ZGddZ Gd d e Z Gd d e ZGd deZGddeZGddeZGddeZGdde ej&j(ZGdde Zy)a& Commands make it possible for layers to communicate with the "outer world", e.g. to perform IO or to ask the master. A command is issued by a proxy layer and is then passed upwards to the proxy server, and from there possibly to the master and addons. The counterpart to commands are events. N) TYPE_CHECKING)Union) Connection)Serverc2eZdZUdZdZeedfed< dZy)Commandz% Base class for all commands Fzmitmproxy.proxy.layer.Layerblockingc|jj}|jddt|jd|dS)Nr ())__dict__copypoptype__name__)selfxs a/home/ubuntu/.cache/pipx/cdb5059130eadca/lib/python3.12/site-packages/mitmproxy/proxy/commands.py__repr__zCommand.__repr__)s@ MM    j$t*%%&auA..N) r __module__ __qualname____doc__r rbool__annotations__rrrrrs)eZdZUdZeed<dedeffd ZdZxZ S)SendDataz$ Send data to a remote peer datar&c2t||||_yr!)superr"r*)rr&r* __class__s rr"zSendData.__init__Ls $ rct|jjdddj}d|d|jdS)Nr rz SendData(, r )strr&splitlowerr*)rtargets rrzSendData.__repr__PsDT__%++C3A6<<>6("TYYM33r) rrrrbytesrrr"r __classcell__r-s@rr)r)Es' K:U4rr)c eZdZUdZeed<dZy)OpenConnectionz Open a new connection r&TN)rrrrrrr rrrr9r9UsHrr9ceZdZdZy)CloseConnectionz Close a connection. If the client connection is closed, all other connections will ultimately be closed during cleanup. N)rrrrrrrr;r;^srr;c8eZdZUeed< ddedeffd ZxZS)CloseTcpConnection half_closer&c2t||||_yr!)r,r"r>)rr&r>r-s rr"zCloseTcpConnection.__init__ms $$r)F)rrrrrrr"r6r7s@rr=r=es& %:%4%%rr=c*eZdZdZdZdZfdZxZS) StartHookz Start an event hook in the mitmproxy core. This triggers a particular function (derived from the class name) in all addons. TcP|tur tdt| |g|i|S)Nz+StartHook may not be instantiated directly.)rA TypeErrorr,__new__)clsargskwargsr-s rrEzStartHook.__new__{s0 ) IJ Jws4T4V44r)rrrrnamer rEr6r7s@rrArArs DH55rrAcTeZdZUdZeed<eed<ejfdedefdZ dZ y)Loga Log a message. Layers could technically call `logging.log` directly, but the use of a command allows us to write more expressive playbook tests. Put differently, by using commands we can assert that a specific log message is a direct consequence of a particular I/O event. This could also be implemented with some more playbook magic in the future, but for now we keep the current approach as the fully sans-io one. messagelevelct|tr:tjdtdt t |j}||_||_ y)Nz>commands.Log() now expects an integer log level, not a string.) stacklevel) isinstancer1warningswarnDeprecationWarninggetattrloggingupperrLrM)rrLrMs rr"z Log.__init__sE eS ! MMP"  GU[[]3E  rc~d|jdtj|jj dS)NzLog(r0r )rLrV getLevelNamerMr3)rs rrz Log.__repr__s6dll%R(<(rcs +' //0G%% 4 4 &' % % 5-- 5T'Tr