iU SSKJr SSKrSSKrSSKrSSKrSSKrSSKrSSK J r J r SSK J r JrJr SSKJrJr SSKJrJrJrJrJrJrJr SSKJrJr SS KJrJ r J!r!J"r"J#r# SS K$J%r%J&r& SS K'J(r( SS K)J*r*J+r+J,r,J-r-J.r. SS K J/r/J0r0J1r1J2r2J3r3J4r4J5r5 SSK6J7r7 S/r8"SS\-5r9"SS\95r:\("\;"5SSSSSS.S9 g)) annotationsN) GeneratorSequence)AnyCallablecast)HeadersMultipleValuesError)InvalidHandshake InvalidHeaderInvalidHeaderValueInvalidMessage InvalidOriginInvalidUpgradeNegotiationError) ExtensionServerExtensionFactory)build_extensionparse_connectionparse_extensionparse_subprotocol parse_upgrade)RequestResponse) lazy_import) CONNECTINGOPENSERVERProtocolState)ConnectionOptionExtensionHeader LoggerLikeOrigin StatusLike SubprotocolUpgradeProtocol) accept_keyServerProtocolc^\rSrSrSrSSSS\SSS.SU4SjjjrSSjrSSjrSS jr SS jr SS jr SS jr SS jr SSjrSU4SjjrSrU=r$)r*0a Sans-I/O implementation of a WebSocket server connection. Args: origins: Acceptable values of the ``Origin`` header. Values can be :class:`str` to test for an exact match or regular expressions compiled by :func:`re.compile` to test against a pattern. Include :obj:`None` in the list if the lack of an origin is acceptable. This is useful for defending against Cross-Site WebSocket Hijacking attacks. extensions: List of supported extensions, in order in which they should be tried. subprotocols: List of supported subprotocols, in order of decreasing preference. select_subprotocol: Callback for selecting a subprotocol among those supported by the client and the server. It has the same signature as the :meth:`select_subprotocol` method, including a :class:`ServerProtocol` instance as first argument. state: Initial state of the WebSocket connection. max_size: Maximum size of incoming messages in bytes. :obj:`None` disables the limit. You may pass a ``(max_message_size, max_fragment_size)`` tuple to set different limits for messages and fragments when you expect long messages sent in short fragments. logger: Logger for this connection; defaults to ``logging.getLogger("websockets.server")``; see the :doc:`logging guide <../../topics/logging>` for details. Ni)origins extensions subprotocolsselect_subprotocolstatemax_sizeloggerc>[TU][UUUS9 XlX lX0lUb'[ USURXR55 gg)N)sider1r2r3r0) super__init__rr-available_extensionsavailable_subprotocolssetattr__get__ __class__) selfr-r.r/r0r1r2r3r<s N/home/mande/repo/quber/.venv/lib/python3.13/site-packages/websockets/server.pyr7ServerProtocol.__init__Nsc"    $.!&2#  ) $"**4@  *cURU5unnn[+5n [,R.R1SS9U S'S U S 'S U S'X)S'UbX9S'UbXIS'[3SSU 5$![aonXQlXPlUR(aUR R SSS9 UR [RRSUS35sSnA$SnAf[anXQlXPlUR(aUR R SSS9 UR [RRSUS35nS URS 'UsSnA$SnAf[anXQlXPlUR(aUR R S SS9 [[U5nUnUR b#UR nUS U3- nUR bM#UR [RR"SUS35sSnA$SnAf[$aZnXQlXPlUR R'S SS9 UR [RR(S5sSnA$SnAff=f)a] Create a handshake response to accept the connection. If the handshake request is valid and the handshake successful, :meth:`accept` returns an HTTP response with status code 101. Else, it returns an HTTP response with another status code. This rejects the connection, like :meth:`reject` would. You must send the handshake response with :meth:`send_response`. You may modify the response before sending it, typically by adding HTTP headers. Args: request: WebSocket handshake request received from the client. Returns: WebSocket handshake response or HTTP response to send to the client. z! invalid originT)exc_infoz'Failed to open a WebSocket connection: z. Nz! invalid upgradez^. You cannot access a WebSocket server directly with a browser. You need a WebSocket client. websocketUpgradez! invalid handshakez; zopening handshake failedzLFailed to open a WebSocket connection. See server log for more information. usegmtDate ConnectionzSec-WebSocket-AcceptSec-WebSocket-ExtensionsSec-WebSocket-ProtocolezSwitching Protocols)process_requestr _exception handshake_excdebugr3rejecthttp HTTPStatus FORBIDDENrUPGRADE_REQUIREDheadersr r BaseException __cause__ BAD_REQUEST ExceptionerrorINTERNAL_SERVER_ERRORr emailutils formatdater) r=request accept_headerextensions_headerprotocol_headerexcresponse exc_chainexc_strrUs r>acceptServerProtocol.acceptqsv,9  $$W-  !n)++000=(  ) *7&'  (2C. /  &0?, -2G<<} !$ !$ zz !!"4t!D;;))9#cB  !$ !$ zz !!"5!E{{00=cUCEFH+6H  Y 'O !$ !$ zz !!"7$!G]C0I" G%%1%// R {++%%1;;++9'#F  "% !$  KK  84  H;;55=  s]A** J4A$CJ J+A5E& J& J3A8H --H J J-AJ<JJcURn[URS5Vs/sHn[U5PM sn/5n[ SU55(d([ SU(aSR U55eS5e[URS5Vs/sHn[U5PM sn/5n[U5S:XaUSR5S:Xd([ SU(aSR U55eS5eUS n[R"UR5S S 9n[U5S :wa [%S U5e['U5n USn U S:wa [%SU 5eUR)U5UlUR-U5uolUR1U5=olXU 4$s snfs snf![a [S 5Se[a [S S 5Sef=f![ R"an[%S U5UeSnAff=f![a [S5Se[a [SS 5Sef=f)a Check a handshake request and negotiate extensions and subprotocol. This function doesn't verify that the request is an HTTP/1.1 or higher GET request and doesn't check the ``Host`` header. These controls are usually performed earlier in the HTTP request handling code. They're the responsibility of the caller. Args: request: WebSocket handshake request received from the client. Returns: ``Sec-WebSocket-Accept``, ``Sec-WebSocket-Extensions``, and ``Sec-WebSocket-Protocol`` headers for the handshake response. Raises: InvalidHandshake: If the handshake request is invalid; then the server must return 400 Bad Request error. rHc3F# UHoR5S:Hv M g7f)upgradeN)lower).0values r> 1ServerProtocol.process_request..sF:%;;=I-:s!, NrDr rrCzSec-WebSocket-Keymultiple valuesT)validatezSec-WebSocket-Version13)rUsumget_allranyrjoinrlenrlKeyErrorr r base64 b64decodeencodebinasciiErrorrr)process_originoriginprocess_extensionsr.process_subprotocol subprotocol) r=r_rUrn connectionrkkeyraw_keyrcr`versionrarbs r>rLServerProtocol.process_requestsZ0//-029//,2O P2O e $2O PRT. F:FFF zdii 3 GK *-/6y/I J/Ie]5 !/I JB*  G !gaj&6&6&8K&G 'DIIg,>T TtT T R-.C  H&&szz|dCG w<2 $%8#> >"3  V56G d?$%" R 35FGT Q R~~ H$%8#>C G H C 78d B" V 79JKQU U Vs;F5F:F? #G/H?-G,/H HH-Ic\URS5nUb[[U5nUR b^UR HCnX2:Xd:[ U[R5(dM)UcM.URU5cMB U$ [U5eU$![a [SS5Sef=f)z Handle the Origin HTTP request header. Args: headers: WebSocket handshake request headers. Returns: origin, if it is acceptable. Raises: InvalidHandshake: If the Origin header is invalid. InvalidOrigin: If the origin isn't acceptable. r%rrN) getr r rr%r- isinstancerePattern fullmatchr)r=rUrorigin_or_regexs r>rServerProtocol.process_origins" G[[*F  &&)F << ##'<<", ;;*'11&9E $0$F++ # G*;<$ F Gs BB+cSn/n/nURS5nU(aUR(a[UVs/sHn[U5PM sn/5nUHbupURHMn U RU:waMU R X5upURX45 URU 5 M` Md U(a [U5nX$4$s snf![ a M|f=f)a Handle the Sec-WebSocket-Extensions HTTP request header. Accept or reject each extension proposed in the client request. Negotiate parameters for accepted extensions. Per :rfc:`6455`, negotiation rules are defined by the specification of each extension. To provide this level of flexibility, for each extension proposed by the client, we check for a match with each extension available in the server configuration. If no match is found, the extension is ignored. If several variants of the same extension are proposed by the client, it may be accepted several times, which won't make sense in general. Extensions must implement their own requirements. For this purpose, the list of previously accepted extensions is provided. This process doesn't allow the server to reorder extensions. It can only select a subset of the extensions proposed by the client. Other requirements, for example related to mandatory extensions or the order of extensions, may be implemented by overriding this method. Args: headers: WebSocket handshake request headers. Returns: ``Sec-WebSocket-Extensions`` HTTP response header and list of accepted extensions. Raises: InvalidHandshake: If the Sec-WebSocket-Extensions header is invalid. NrI) rwr8rvrnameprocess_request_paramsrappendr) r=rUresponse_header_valueextension_headersaccepted_extensions header_values header_valueparsed_header_valuesrrequest_params ext_factoryresponse_params extensions r>r!ServerProtocol.process_extensions8sN-135/1(BC T66:=CPQ=<.=QSU; )=$#'#<#r"ServerProtocol.process_subprotocolsW/2%,OO4L$M $ML",/$M   / &&|44  sAcUR(dgU(d [S5e[U5nURH nX2;dM Us $ [SSRUR5-5e)a Pick a subprotocol among those offered by the client. If several subprotocols are supported by both the client and the server, pick the first one in the list declared the server. If the server doesn't support any subprotocols, continue without a subprotocol, regardless of what the client offers. If the server supports at least one subprotocol and the client doesn't offer any, abort the handshake with an HTTP 400 error. You provide a ``select_subprotocol`` argument to :class:`ServerProtocol` to override this logic. For example, you could accept the connection even if client doesn't offer a subprotocol, rather than reject it. Here's how to negotiate the ``chat`` subprotocol if the client supports it and continue without a subprotocol otherwise:: def select_subprotocol(protocol, subprotocols): if "chat" in subprotocols: return "chat" Args: subprotocols: List of subprotocols offered by the client. Returns: Selected subprotocol, if a common subprotocol was found. :obj:`None` to continue without a subprotocol. Raises: NegotiationError: Custom implementations may raise this exception to abort the handshake with an HTTP 400 error. Nzmissing subprotocolz%invalid subprotocol; expected one of rq)r9rsetry)r=r/proposed_subprotocolsrs r>r0!ServerProtocol.select_subprotocolstR**"#89 9!$L 166K3""7  3ii334 5  r@c [R"U5nUR5n[S[R R SS94SS[[U554S/5n[URURXC5$)a Create a handshake response to reject the connection. A short plain text response is the best fallback when failing to establish a WebSocket connection. You must send the handshake response with :meth:`send_response`. You may modify the response before sending it, for example by changing HTTP headers. Args: status: HTTP status code. text: HTTP response body; it will be encoded to UTF-8. Returns: HTTP response to send to the client. rGTrE)rHclosezContent-Length)z Content-Typeztext/plain; charset=utf-8) rQrRr~r r\r]r^strrzrrnphrase)r=statustextbodyrUs r>rPServerProtocol.rejectsu*({{}//t/<='!3s4y>2=    fmmWCCr@cJUR(aURURp2URRSX#5 URR 5H!upEURRSXE5 M# UR (a/URRS[UR 55 URRUR55 URS:Xa<UR[Lde[Ul URRS5 gURRSURUR5 UR5 UR!5Ul[%UR"5 g)zl Send a handshake response to the client. Args: response: WebSocket handshake response event to send. z> HTTP/1.1 %d %sz> %s: %sz> [body] (%d bytes)rKzconnection openzconnection rejected (%d %s)N)rO status_code reason_phraser3rU raw_itemsrrzwritesr serializer1rrinfosend_eofdiscardparsernext)r=rdcoderrrns r> send_responseServerProtocol.send_responses) ::#//1G1G& KK  0$ ?&..88:  !!*c9;}} !!"7X]]9KL 8--/0   3 &::+ ++DJ KK  . / KK  -$$&&  MMO,,.DK  r@c#># UR[La[R"URR 5ShvN nUR(aeURRSWR 5 UR"R%5H!up4URRSX45 M# UR&R)W5 [*TU] 5ShvN gN![ ain[S5UlX Rl UR5 UR5Ul [UR5 Sv SnAGNSnAff=fN}7f)Nz$did not receive a valid HTTP requestz< GET %s HTTP/1.1z< %s: %s)r1rrparsereader read_linerYrrNrWrrrrrOr3pathrUreventsrr6)r=r_rcrrnr<s r>rServerProtocol.parse s  :: # %,]]KK))&zz !!"5w||D")//";";"=JCKK%%j#=#> KK  w '7=?"") %3:&"03"", "lln T[[! " #sNE,-C4C2C4 B"E,,E*-E,2C44 E'>AE"E,"E''E,) r8r9r.rNrr-rr1r)r-z0Sequence[Origin | re.Pattern[str] | None] | Noner.z'Sequence[ServerExtensionFactory] | Noner/zSequence[Subprotocol] | Noner0zLCallable[[ServerProtocol, Sequence[Subprotocol]], Subprotocol | None] | Noner1r!r2z*int | None | tuple[int | None, int | None]r3zLoggerLike | NonereturnNone)r_rrr)r_rrz"tuple[str, str | None, str | None])rUr rz Origin | None)rUr rz"tuple[str | None, list[Extension]])rUr rSubprotocol | None)r/zSequence[Subprotocol]rr)rr&rrrr)rdrrr)rzGenerator[None])__name__ __module__ __qualname____firstlineno____doc__rr7rgrLrrrr0rPrr__static_attributes__ __classcell__r<s@r>r*r*0s@EI>B59 !?D$(!B!< ! 3 ! !!=!"! !!!FZ=xFCFC ,FCP!FO:O: ,O:b50: +:  : xDB D##r@c,^\rSrSrSU4SjjrSrU=r$)ServerConnectioni:c\>[R"S[5 [TU]"U0UD6 g)Nz.ServerConnection was renamed to ServerProtocol)warningswarnDeprecationWarningr6r7)r=argskwargsr<s r>r7ServerConnection.__init__;s) <   $)&)r@)rrrrrr)rrrrr7rrrs@r>rr:s **r@rz.legacy.server)WebSocketServerWebSocketServerProtocol broadcastserve unix_serve)deprecated_aliases)< __future__rr|r email.utilsr\rQrrcollections.abcrrtypingrrrdatastructuresr r exceptionsr r rrrrrr.rrrUrrrrrhttp11rrimportsrprotocolrrrr r!r"r#r$r%r&r'r(r]r)__all__r*rglobalsrr@r>rs"  /&&8:& ??  G#XG#T*~*  I,#3%!&  r@