gddlmZddlZddlZddlZddlmZm Z m Z m Z ddl m Z ddlmZmZddlmZmZdd lmZmZmZgd ZGd d Zdddd ddZ dd dZdS)!) annotationsN)Any AwaitableCallableLiteral)NotFound)MapRequestRedirect)RequestResponse)ServerServerConnectionserve)route unix_routeRoutercHeZdZdZ ddd ZddZddZddZddZddZ dS) rz*WebSocket router supporting :func:`route`.Nwsurl_mapr server_name str | None url_schemestrreturnNonecv||_||_||_|jD] }d|_ dS)NT)rrr iter_rules websocket)selfrrrrules e/var/www/html/nodeJS/PythonScripts/venv3.11/lib/python3.11/site-packages/websockets/asyncio/router.py__init__zRouter.__init__sJ  &$L++-- " "D!DNN " " connectionrrequestr c8|j |jdS|jS)NHost)rheaders)r!r&r's r#get_server_namezRouter.get_server_name!s!   #?6* *# #r%urlr cj|tjjd|}||jd<|S)Nz Found at Location)respondhttp HTTPStatusFOUNDr*)r!r&r,responses r#redirectzRouter.redirect's7%%do&;=N=N=NOO'*$r%cL|tjjdS)Nz Not Found)r/r0r1 NOT_FOUNDr!r&s r# not_foundzRouter.not_found,s!!$/";[IIIr%Response | Nonec|j||||j} tj|j}||j|j \}}nR#t$r%}| ||j cYd}~Sd}~wt$r||cYSwxYw||c|_|_dS)zRoute incoming request.)rr) path_info query_argsN)rbindr+rurllibparseurlparsepathmatchqueryr r4new_urlrr8handlerhandler_kwargs)r!r&r'url_map_adapterparsedrEkwargsr4s r# route_requestzRouter.route_request/s,++,,ZAA,   .\**7<88F-33 +!<4OGVV ? ? ?==X-=>> > > > > > > . . .>>*-- - - - .8?5 J5ts$AB C B*$C*"CCc8K|j|fi|jd{VS)zHandle a connection.N)rErFr7s r#rEzRouter.handlerDs6'Z' PPj6OPPPPPPPPPr%)Nr)rr rrrrrr)r&rr'r rr)r&rr,rrr )r&rrr r&rr'r rr9)r&rrr) __name__ __module__ __qualname____doc__r$r+r4r8rJrEr%r#rrs44 #' " " " " "$$$$  JJJJ*QQQQQQr%r)rssl create_routerrr argsrrrrR,ssl_module.SSLContext | Literal[True] | NonerStype[Router] | NonerIrAwaitable[Server]c |dnd}|dur|||d<|t}|||| |dd j}nd fd }t jg|Rd|i|S)a- Create a WebSocket server dispatching connections to different handlers. This feature requires the third-party library `werkzeug`_: .. code-block:: console $ pip install werkzeug .. _werkzeug: https://werkzeug.palletsprojects.com/ :func:`route` accepts the same arguments as :func:`~websockets.sync.server.serve`, except as described below. The first argument is a :class:`werkzeug.routing.Map` that maps URL patterns to connection handlers. In addition to the connection, handlers receive parameters captured in the URL as keyword arguments. Here's an example:: from websockets.asyncio.router import route from werkzeug.routing import Map, Rule async def channel_handler(websocket, channel_id): ... url_map = Map([ Rule("/channel/", endpoint=channel_handler), ... ]) # set this future to exit the server stop = asyncio.get_running_loop().create_future() async with route(url_map, ...) as server: await stop Refer to the documentation of :mod:`werkzeug.routing` for details. If you define redirects with ``Rule(..., redirect_to=...)`` in the URL map, when the server runs behind a reverse proxy that modifies the ``Host`` header or terminates TLS, you need additional configuration: * Set ``server_name`` to the name of the server as seen by clients. When not provided, websockets uses the value of the ``Host`` header. * Set ``ssl=True`` to generate ``wss://`` URIs without actually enabling TLS. Under the hood, this bind the URL map with a ``url_scheme`` of ``wss://`` instead of ``ws://``. There is no need to specify ``websocket=True`` in each rule. It is added automatically. Args: url_map: Mapping of URL patterns to connection handlers. server_name: Name of the server as seen by clients. If :obj:`None`, websockets uses the value of the ``Host`` header. ssl: Configuration for enabling TLS on the connection. Set it to :obj:`True` if a reverse proxy terminates TLS connections. create_router: Factory for the :class:`Router` dispatching requests to handlers. Set it to a wrapper or a subclass to customize routing. NrwssTrRprocess_requestr&rr'r rr9cK||}t|tr|d{V}||S||SN) isinstancerrJ)r&r'r3_process_requestrouters r#rZzroute..process_requests_(' G<>>>>>#'' G<< typingrrrrwerkzeug.exceptionsrwerkzeug.routingr r http11r r serverrrr__all__rrrrQr%r#rlsX"""""" 444444444444((((((11111111&&&&&&&&3333333333 , + +4Q4Q4Q4Q4Q4Q4Q4Qt#8<)- jSjSjSjSjSjS^:::::::r%