U Mf@sddlmZddlZddlZddlZddlZddlZddlZddl Z ddl Z ddl m Z ddl mZmZmZmZmZmZmZmZmZmZmZmZmZddlmZmZmZddlm Z m!Z!m"Z"m#Z#m$Z$m%Z%m&Z&ddl'm(Z(m)Z)dd l*m+Z+dd l,m-Z-m.Z.m/Z/m0Z0dd lm1Z1dd l2m3Z3dd l m4Z4m5Z5m6Z6m7Z7m8Z8ddl9m:Z:ddl;mZ>ddl2m?Z?ddddgZ@eeeeAegeffZBee7eeCfZDGddde?ZEGdddZFGdddZGeGZHd$dddddddZIdd d!d"d#ZJdS)%) annotationsN) TracebackType) Any AwaitableCallable GeneratorIterableListOptionalSequenceSetTupleTypeUnioncast)Headers HeadersLikeMultipleValuesError)AbortHandshakeInvalidHandshake InvalidHeaderInvalidMessage InvalidOriginInvalidUpgradeNegotiationError) ExtensionServerExtensionFactory) enable_server_permessage_deflate)build_extensionparse_extensionparse_subprotocolvalidate_subprotocols) USER_AGENT)State)ExtensionHeader LoggerLikeOrigin StatusLike Subprotocol)asyncio_timeout)build_response check_request) read_request)WebSocketCommonProtocolserve unix_serveWebSocketServerProtocolWebSocketServercseZdZdZdZdZdddddedddd ddd d d d d ddddddd fddZdddfdd ZddddZ dddd Z d?d!d"d#dd$d%d&Z d'd"d(d)d*d+Z e d@d"d d,d-d.d/Ze d"d d0d1d2d3Zd"d d4d5d6d7Zd8d8d4d9d:d;ZdAd d d d d'd<d=d>ZZS)Br2a WebSocket server connection. :class:`WebSocketServerProtocol` provides :meth:`recv` and :meth:`send` coroutines for receiving and sending messages. It supports asynchronous iteration to receive messages:: async for message in websocket: await process(message) The iterator exits normally when the connection is closed with close code 1000 (OK) or 1001 (going away) or without a close code. It raises a :exc:`~websockets.exceptions.ConnectionClosedError` when the connection is closed with any other code. You may customize the opening handshake in a subclass by overriding :meth:`process_request` or :meth:`select_subprotocol`. Args: ws_server: WebSocket server that created this connection. See :func:`serve` for the documentation of ``ws_handler``, ``logger``, ``origins``, ``extensions``, ``subprotocols``, ``extra_headers``, and ``server_header``. See :class:`~websockets.legacy.protocol.WebSocketCommonProtocol` for the documentation of ``ping_interval``, ``ping_timeout``, ``close_timeout``, ``max_size``, ``max_queue``, ``read_limit``, and ``write_limit``. FserverN ) loggerorigins extensions subprotocols extra_headers server_headerprocess_requestselect_subprotocol open_timeouttUnion[Callable[[WebSocketServerProtocol], Awaitable[Any]], Callable[[WebSocketServerProtocol, str], Awaitable[Any]]]r3Optional[LoggerLike]$Optional[Sequence[Optional[Origin]]]*Optional[Sequence[ServerExtensionFactory]]Optional[Sequence[Subprotocol]]Optional[HeadersLikeOrCallable] Optional[str]EOptional[Callable[[str, Headers], Awaitable[Optional[HTTPResponse]]]]OOptional[Callable[[Sequence[Subprotocol], Sequence[Subprotocol]], Subprotocol]]Optional[float]rNone) ws_handler ws_serverr6r7r8r9r:r;r<r=r>kwargsreturnc  s|dkrtd}tjfd|i| |dk rRd|krRtdtdd|D}t||_||_ ||_ ||_ ||_ ||_ ||_| |_| |_| |_dS)Nwebsockets.serverr6z!use None instead of '' in originscSsg|]}|dkrdn|qS)rON).0originrPrPsz4WebSocketServerProtocol.__init__..)logging getLoggersuper__init__warningswarnDeprecationWarningremove_path_argumentrJrKr7available_extensionsavailable_subprotocolsr:r;_process_request_select_subprotocolr>) selfrJrKr6r7r8r9r:r;r<r=r>rL __class__rPrSrXbs    z WebSocketServerProtocol.__init__zasyncio.BaseTransport) transportrMcs.t||j||j||_dS)zJ Register connection and initialize a task to handle it. N)rWconnection_maderKregisterloop create_taskhandler handler_task)rardrbrPrSres  z'WebSocketServerProtocol.connection_maderMc sdzBzzJt|j4IdH&|j|j|j|j |j dIdHW5QIdHRXWn t j k rlYnt k rYntk r^}zt|tr|j|j|j}}}nt|tr|jr|jjdddtjjtd|d}}}nt|trH|jr |jjd ddtjjtd gd|d }}}nnt|tr|jrl|jjd ddtjjtd|d}}}n&|jjd ddtjj td}}}|!dt"j#j$dd|j%dk r|!d|j%|!dt&t'||!dd|!dd|(||||jd|j)|j*|+IdHWY WWdSd}~XYnXz|,|IdHWn:tk r|jjddd|j-s|.dYnXz|/IdHWn>t k rYn(tk r|jjdddYnXWn<tk r@z|j0/Wntk r:YnXYnXW5|j||jdXdS)a Handle the lifecycle of a WebSocket connection. Since this method doesn't have a caller able to handle exceptions, it attempts to log relevant ones and guarantees that the TCP connection is closed before exiting. zconnection closedN)r7r]r^r:z! invalid originT)exc_infoz'Failed to open a WebSocket connection: z. z! invalid upgrade)ZUpgrade websocketz^. You cannot access a WebSocket server directly with a browser. You need a WebSocket client. z! invalid handshakezopening handshake failedsLFailed to open a WebSocket connection. See server log for more information. DateusegmtServerzContent-Lengthz Content-Typez text/plain Connectionclosezconnection rejected (%d %s)zconnection handler failedizclosing handshake failed)1rK unregisterr6infor+r> handshaker7r]r^r:asyncio TimeoutErrorConnectionError Exception isinstancerstatusheadersbodyrdebughttp HTTPStatus FORBIDDENrencoderUPGRADE_REQUIREDr BAD_REQUESTerrorINTERNAL_SERVER_ERROR setdefaultemailutils formatdater;strlenwrite_http_responsevaluephraseZclose_transportrJclosedZfail_connectionrsrd)raexcr|r}r~rPrPrSris "              zWebSocketServerProtocol.handlerzTuple[str, Headers]c szt|jIdH\}}WnBtjk r0Yn,tk rZ}ztd|W5d}~XYnX|jr|jd||D]\}}|jd||qx||_ ||_ ||fS)a: Read request line and headers from the HTTP request. If the request contains a body, it may be read from ``self.reader`` after this coroutine returns. Raises: InvalidMessage: if the HTTP message is malformed or isn't an HTTP/1.1 GET request. Nz$did not receive a valid HTTP requestz< GET %s HTTP/1.1z< %s: %s) r.readerrwZCancelledErrorrzrrr6 raw_itemspathrequest_headers)rarr}rkeyrrPrPrSread_http_request s z)WebSocketServerProtocol.read_http_requestzhttp.HTTPStatusrzOptional[bytes])r|r}r~rMcCs||_|jr\|jd|j|j|D]\}}|jd||q(|dk r\|jdt|d|jd|jd}|t|7}|j | |dk r|j |dS)z Write status line and headers to the HTTP response. This coroutine is also able to write a response body. z> HTTP/1.1 %d %sz> %s: %sNz> [body] (%d bytes)z HTTP/1.1  z ) response_headersrr6rrrrrrdwriter)rar|r}r~rrresponserPrPrSr's  z+WebSocketServerProtocol.write_http_responserzOptional[HTTPResponse])rrrMcs>|jdk r:|||}t|tr*|IdHStdt|SdS)a Intercept the HTTP request and return an HTTP response if appropriate. You may override this method in a :class:`WebSocketServerProtocol` subclass, for example: * to return an HTTP 200 OK response on a given path; then a load balancer can use this path for a health check; * to authenticate the request and return an HTTP 401 Unauthorized or an HTTP 403 Forbidden when authentication fails. You may also override this method with the ``process_request`` argument of :func:`serve` and :class:`WebSocketServerProtocol`. This is equivalent, except ``process_request`` won't have access to the protocol instance, so it can't store information for later use. :meth:`process_request` is expected to complete quickly. If it may run for a long time, then it should await :meth:`wait_closed` and exit if :meth:`wait_closed` completes, or else it could prevent the server from shutting down. Args: path: request path, including optional query string. request_headers: request headers. Returns: Optional[Tuple[StatusLike, HeadersLike, bytes]]: :obj:`None` to continue the WebSocket handshake normally. An HTTP response, represented by a 3-uple of the response status, headers, and body, to abort the WebSocket handshake and return that HTTP response instead. N&declare process_request as a coroutine)r_r{rrYrZr[)rarrrrPrPrSr<Cs%    z'WebSocketServerProtocol.process_requestzOptional[Origin])r}r7rMc Csdzttt|d}Wn.tk rF}ztdd|W5d}~XYnX|dk r`||kr`t||S)z Handle the Origin HTTP request header. Args: headers: request headers. origins: optional list of acceptable origins. Raises: InvalidOrigin: if the origin isn't acceptable. r'z!more than one Origin header foundN)rr r'getrrr)r}r7rRrrPrPrSprocess_origintsz&WebSocketServerProtocol.process_originz%Tuple[Optional[str], List[Extension]])r}r]rMc Csd}g}g}|d}|r|rtdd|Dg}|D]h\}}|D]Z} | j|krRqBz| ||\} } Wntk r~YqBYnX||| f|| q6qBq6|rt|}||fS)a Handle the Sec-WebSocket-Extensions HTTP request header. Accept or reject each extension proposed in the client request. Negotiate parameters for accepted extensions. Return the Sec-WebSocket-Extensions HTTP response header and the list of accepted extensions. :rfc:`6455` leaves the rules up to 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: request headers. extensions: optional list of supported extensions. Raises: InvalidHandshake: to abort the handshake with an HTTP 400 error. NSec-WebSocket-ExtensionscSsg|] }t|qSrP)r rQ header_valuerPrPrSrTsz>WebSocketServerProtocol.process_extensions..)get_allsumnameZprocess_request_paramsrappendr) r}r]Zresponse_header_valueZextension_headersZaccepted_extensions header_valuesparsed_header_valuesrZrequest_paramsZ ext_factoryZresponse_params extensionrPrPrSprocess_extensionss4(       z*WebSocketServerProtocol.process_extensionszOptional[Subprotocol])r}r^rMcCs:d}|d}|r6|r6tdd|Dg}|||}|S)a Handle the Sec-WebSocket-Protocol HTTP request header. Return Sec-WebSocket-Protocol HTTP response header, which is the same as the selected subprotocol. Args: headers: request headers. available_subprotocols: optional list of supported subprotocols. Raises: InvalidHandshake: to abort the handshake with an HTTP 400 error. NSec-WebSocket-ProtocolcSsg|] }t|qSrP)r!rrPrPrSrTsz?WebSocketServerProtocol.process_subprotocol..)rrr=)rar}r^ subprotocolrrrPrPrSprocess_subprotocols  z+WebSocketServerProtocol.process_subprotocolzSequence[Subprotocol])client_subprotocolsserver_subprotocolsrMcsH|jdk r|Stt@}|s.dSt|fddddS)a Pick a subprotocol among those supported by the client and the server. If several subprotocols are available, select the preferred subprotocol by giving equal weight to the preferences of the client and the server. If no subprotocol is available, proceed without a subprotocol. You may provide a ``select_subprotocol`` argument to :func:`serve` or :class:`WebSocketServerProtocol` to override this logic. For example, you could reject the handshake if the client doesn't support a particular subprotocol, rather than accept the handshake without that subprotocol. Args: client_subprotocols: list of subprotocols offered by the client. server_subprotocols: list of subprotocols available on the server. Returns: Optional[Subprotocol]: Selected subprotocol, if a common subprotocol was found. :obj:`None` to continue without a subprotocol. Ncs||SN)index)prrrPrS'z.)rr)r`setsorted)rarrr9rPrrSr=s   z*WebSocketServerProtocol.select_subprotocol)r7r]r^r:rMc sj|IdH\}}|||}t|tr4|IdH}ntdt|}|jtj krXt d|j spt jjgdf}|dk rt|t|} ||||_|||\} |_|||} |_t} t| | | dk r| | d<| dk r| | d<t|r|||j}|dk r| || dtjj dd |j!dk rB| d |j!|"t jj#| |j$%d |&|S) a Perform the server side of the opening handshake. Args: origins: list of acceptable values of the Origin HTTP header; include :obj:`None` if the lack of an origin is acceptable. extensions: list of supported extensions, in order in which they should be tried. subprotocols: list of supported subprotocols, in order of decreasing preference. extra_headers: arbitrary HTTP headers to add to the response when the handshake succeeds. Returns: str: path of the URI of the request. Raises: InvalidHandshake: if the handshake fails. Nrz*connection closed during opening handshakesServer is shutting down. rrrnTrorqzconnection open)'rr<r{rrYrZr[stater$ZCLOSEDBrokenPipeErrorrK is_servingrrSERVICE_UNAVAILABLErr-rrRrr8rrrr,callablerupdaterrrrr;rSWITCHING_PROTOCOLSr6ruZconnection_open) rar7r]r^r:rrZearly_response_awaitableZearly_responserZextensions_headerZprotocol_headerrrPrPrSrv*sT              z!WebSocketServerProtocol.handshake)N)N)NNNN)__name__ __module__ __qualname____doc__Z is_clientZsider#rXrerirrr< staticmethodrrrr=rv __classcell__rPrPrbrSr2?s> ., o1R +c@seZdZdZd0ddddZddd d d Zd dd ddZd dd ddZd1dddddZdddddZ ddddZ ddddZ dddd Z ddd!d"Z ddd#d$Zed%dd&d'Zddd(d)Zd*d+d,dd-d.d/ZdS)2r3a WebSocket server returned by :func:`serve`. This class provides the same interface as :class:`~asyncio.Server`, notably the :meth:`~asyncio.Server.close` and :meth:`~asyncio.Server.wait_closed` methods. It keeps track of WebSocket connections in order to close them properly when shutting down. Args: logger: Logger for this server. It defaults to ``logging.getLogger("websockets.server")``. See the :doc:`logging guide <../../topics/logging>` for details. Nr@r6cCs.|dkrtd}||_t|_d|_|dS)NrN)rUrVr6r websockets close_task)rar6rPrPrSrXs  zWebSocketServer.__init__zasyncio.base_events.ServerrI)r4rMcCs||_|jD]p}|jtjkr*d|}nD|jtjkrLd|dd}n"|jtjkrb|}n t|}|j d|q | |_ dS)a Attach to a given :class:`~asyncio.Server`. Since :meth:`~asyncio.loop.create_server` doesn't support injecting a custom ``Server`` class, the easiest solution that doesn't rely on private :mod:`asyncio` APIs is to: - instantiate a :class:`WebSocketServer` - give the protocol factory a reference to that instance - call :meth:`~asyncio.loop.create_server` with the factory - attach the resulting :class:`~asyncio.Server` with this method z%s:%dz[%s]:%dNrzserver listening on %s)r4socketsfamilysocketAF_INET getsocknameAF_INET6AF_UNIXrr6ruget_loopZ create_future closed_waiter)rar4sockrrPrPrSwraps      zWebSocketServer.wrapr2)protocolrMcCs|j|dS)z: Register a connection with this server. N)raddrarrPrPrSrfszWebSocketServer.registercCs|j|dS)z< Unregister a connection with this server. N)rremoverrPrPrSrtszWebSocketServer.unregisterTbool)close_connectionsrMcCs$|jdkr ||||_dS)aw Close the server. * Close the underlying :class:`~asyncio.Server`. * When ``close_connections`` is :obj:`True`, which is the default, close existing connections. Specifically: * Reject opening WebSocket connections with an HTTP 503 (service unavailable) error. This happens when the server accepted the TCP connection but didn't complete the opening handshake before closing. * Close open WebSocket connections with close code 1001 (going away). * Wait until all connection handlers terminate. :meth:`close` is idempotent. N)rrrh_close)rarrPrPrSrss zWebSocketServer.closecs|jd|jtdIdH|rNdd|jD}|rNt|IdH|jIdH|jrtdd|jDIdH|j d|jddS)a Implementation of :meth:`close`. This calls :meth:`~asyncio.Server.close` on the underlying :class:`~asyncio.Server` object to stop accepting new connections and then closes open connections with close code 1001. zserver closingrNcSs(g|] }|jtjk rt|dqS)i)rr$Z CONNECTINGrwrhrsrQrmrPrPrSrTs z*WebSocketServer._close..cSsg|] }|jqSrP)rjrrPrPrSrTsz server closed) r6rur4rsrwsleeprwait wait_closedrZ set_result)rarZ close_tasksrPrPrSrs    zWebSocketServer._closerkcst|jIdHdS)a Wait until the server is closed. When :meth:`wait_closed` returns, all TCP connections are closed and all connection handlers have returned. To ensure a fast shutdown, a connection handler should always be awaiting at least one of: * :meth:`~WebSocketServerProtocol.recv`: when the connection is closed, it raises :exc:`~websockets.exceptions.ConnectionClosedOK`; * :meth:`~WebSocketServerProtocol.wait_closed`: when the connection is closed, it returns. Then the connection handler is immediately notified of the shutdown; it can clean up and exit. N)rwZshieldrrarPrPrSrszWebSocketServer.wait_closedzasyncio.AbstractEventLoopcCs |jS)z7 See :meth:`asyncio.Server.get_loop`. )r4rrrPrPrSr0szWebSocketServer.get_loopcCs |jS)z9 See :meth:`asyncio.Server.is_serving`. )r4rrrPrPrSr7szWebSocketServer.is_servingcs|jIdHdS)a See :meth:`asyncio.Server.start_serving`. Typical use:: server = await serve(..., start_serving=False) # perform additional setup here... # ... then start the server await server.start_serving() N)r4 start_servingrrPrPrSr>s zWebSocketServer.start_servingcs|jIdHdS)a See :meth:`asyncio.Server.serve_forever`. Typical use:: server = await serve(...) # this coroutine doesn't return # canceling it stops the server await server.serve_forever() This is an alternative to using :func:`serve` as an asynchronous context manager. Shutdown is triggered by canceling :meth:`serve_forever` instead of exiting a :func:`serve` context. N)r4 serve_foreverrrPrPrSrLszWebSocketServer.serve_foreverzIterable[socket.socket]cCs|jjS)z6 See :attr:`asyncio.Server.sockets`. )r4rrrPrPrSr^szWebSocketServer.socketscs|SrrPrrPrPrS __aenter__fszWebSocketServer.__aenter__Optional[Type[BaseException]]Optional[BaseException]Optional[TracebackType]exc_type exc_value tracebackrMcs||IdHdSr)rsrrarrrrPrPrS __aexit__iszWebSocketServer.__aexit__)N)T)rrrrrXrrfrtrsrrrrrrpropertyrrrrPrPrPrSr3s  -c@seZdZdZd,dddddddeddddddddddd d d d d dddddddddddddd d dddddddZdddd Zd!d"d#dd$d%d&Zd'dd(d)Zddd*d+Z eZ dS)-Servea Start a WebSocket server listening on ``host`` and ``port``. Whenever a client connects, the server creates a :class:`WebSocketServerProtocol`, performs the opening handshake, and delegates to the connection handler, ``ws_handler``. The handler receives the :class:`WebSocketServerProtocol` and uses it to send and receive messages. Once the handler completes, either normally or with an exception, the server performs the closing handshake and closes the connection. Awaiting :func:`serve` yields a :class:`WebSocketServer`. This object provides a :meth:`~WebSocketServer.close` method to shut down the server:: stop = asyncio.Future() # set this future to exit the server server = await serve(...) await stop await server.close() :func:`serve` can be used as an asynchronous context manager. Then, the server is shut down automatically when exiting the context:: stop = asyncio.Future() # set this future to exit the server async with serve(...): await stop Args: ws_handler: Connection handler. It receives the WebSocket connection, which is a :class:`WebSocketServerProtocol`, in argument. host: Network interfaces the server binds to. See :meth:`~asyncio.loop.create_server` for details. port: TCP port the server listens on. See :meth:`~asyncio.loop.create_server` for details. create_protocol: Factory for the :class:`asyncio.Protocol` managing the connection. It defaults to :class:`WebSocketServerProtocol`. Set it to a wrapper or a subclass to customize connection handling. logger: Logger for this server. It defaults to ``logging.getLogger("websockets.server")``. See the :doc:`logging guide <../../topics/logging>` for details. compression: The "permessage-deflate" extension is enabled by default. Set ``compression`` to :obj:`None` to disable it. See the :doc:`compression guide <../../topics/compression>` for details. origins: Acceptable values of the ``Origin`` header, for defending against Cross-Site WebSocket Hijacking attacks. Include :obj:`None` in the list if the lack of an origin is acceptable. extensions: List of supported extensions, in order in which they should be negotiated and run. subprotocols: List of supported subprotocols, in order of decreasing preference. extra_headers (Union[HeadersLike, Callable[[str, Headers], HeadersLike]]): Arbitrary HTTP headers to add to the response. This can be a :data:`~websockets.datastructures.HeadersLike` or a callable taking the request path and headers in arguments and returning a :data:`~websockets.datastructures.HeadersLike`. server_header: Value of the ``Server`` response header. It defaults to ``"Python/x.y.z websockets/X.Y"``. Setting it to :obj:`None` removes the header. process_request (Optional[Callable[[str, Headers], Awaitable[Optional[Tuple[StatusLike, HeadersLike, bytes]]]]]): Intercept HTTP request before the opening handshake. See :meth:`~WebSocketServerProtocol.process_request` for details. select_subprotocol: Select a subprotocol supported by the client. See :meth:`~WebSocketServerProtocol.select_subprotocol` for details. open_timeout: Timeout for opening connections in seconds. :obj:`None` disables the timeout. See :class:`~websockets.legacy.protocol.WebSocketCommonProtocol` for the documentation of ``ping_interval``, ``ping_timeout``, ``close_timeout``, ``max_size``, ``max_queue``, ``read_limit``, and ``write_limit``. Any other keyword arguments are passed the event loop's :meth:`~asyncio.loop.create_server` method. For example: * You can set ``ssl`` to a :class:`~ssl.SSLContext` to enable TLS. * You can set ``sock`` to a :obj:`~socket.socket` that you created outside of websockets. Returns: WebSocketServer: WebSocket server. Ndeflater5i i)create_protocolr6 compressionr7r8r9r:r;r<r=r> ping_interval ping_timeout close_timeoutmax_size max_queue read_limit write_limitr?z#Optional[Union[str, Sequence[str]]]z Optional[int]z0Optional[Callable[..., WebSocketServerProtocol]]r@rErArBrCrDrFrGrHintrrI)rJhostportrr6rr7r8r9r:r;r<r=r>rrrrrrrrLrMc!Ks|dd}|dkrd}n tdt|dkr2|}|dd}|dkrLt}n tdt|dkrd|}|dd}|dd}|dkrt}n|}td tt|d }|d dk }|d krt |}n|dk rt d || dk rt | t j |t|||||||||||||||||| | | | | |d}|ddrt|dd}|dkrZ|dks^tt j |j||f|} nt j |j|||f|} | |_||_dS)Ntimeoutr5zrename timeout to close_timeoutklasszrename klass to create_protocol legacy_recvFrgzremove loop argumentrsslrzunsupported compression: )rrsecurer>rrrrrrrrgrr7r8r9r:r;r<r=r6unixr)poprYrZr[r2rwZget_event_loopr3rr ValueErrorr" functoolspartialr\AssertionErrorZcreate_unix_server create_server_create_serverrK)!rarJrrrr6rr7r8r9r:r;r<r=r>rrrrrrrrLrrrZ_looprgrKrfactoryrrrPrPrSrXs"           zServe.__init__r3rkcs |IdHSrrPrrPrPrSrIszServe.__aenter__rrrrcs|j|jIdHdSr)rKrsrrrPrPrSrLs zServe.__aexit__z%Generator[Any, None, WebSocketServer]cCs |Sr)__await_impl__ __await__rrPrPrSr WszServe.__await__cs |IdH}|j||jSr)rrKr)rar4rPrPrSr [s zServe.__await_impl__)NN) rrrrr#rXrrr r __iter__rPrPrPrSrss8_ >| rr?rEr)rJrrLrMcKst|f|dd|S)a Start a WebSocket server listening on a Unix socket. This function is identical to :func:`serve`, except the ``host`` and ``port`` arguments are replaced by ``path``. It is only available on Unix. Unrecognized keyword arguments are passed the event loop's :meth:`~asyncio.loop.create_unix_server` method. It's useful for deploying a server behind a reverse proxy such as nginx. Args: path: File system path to the Unix socket. T)rr)r0)rJrrLrPrPrSr1hsz3Callable[[WebSocketServerProtocol], Awaitable[Any]])rJrMc sztdWn\tk rpztddWntk rNYnXdddfdd }|YSYnXtttgttfS)NrOr2r)rmrMcs(ttttgttf||jIdHSr)rrr2rrrr)rmrJrPrS _ws_handlersz)remove_path_argument.._ws_handler) inspect signaturebind TypeErrorrrr2rr)rJrrPr rSr\sr\)N)K __future__rrw email.utilsrrrrrUrrYtypesrtypingrrrrrr r r r r rrrZdatastructuresrrr exceptionsrrrrrrrr8rrZextensions.permessage_deflaterr}rr r!r"r#rr$r%r&r'r(r)Z compatibilityr+rvr,r-r.r/__all__rZHeadersLikeOrCallablebytes HTTPResponser2r3rr0r1r\rPrPrPrSsL  <$        Nks