a њh @sddlmZddlZddlZddlZddlmZm Z m Z ddl m Z ddl mZmZddlmZmZdd lmZmZmZgd ZGd d d Zdddd ddddddddddZddddddddZdS)) annotationsN)AnyCallableLiteral)NotFound)MapRequestRedirect)RequestResponse)ServerServerConnectionserve)route unix_routeRouterc@s|eZdZdZddddddd d Zd d dd ddZd dddddZd ddddZd d dd ddZd ddddZ dS)rz*WebSocket router supporting :func:`route`.Nwsr str | NonestrNone)url_map server_name url_schemereturncCs,||_||_||_|jD] }d|_qdS)NT)rrrZ iter_rulesZ websocket)selfrrrrulerQ/wd/webapps/venvs/v2025_4um/lib/python3.9/site-packages/websockets/sync/router.py__init__s zRouter.__init__rr  connectionrequestrcCs|jdur|jdS|jSdS)NHost)rheaders)rr!r"rrrget_server_name!s  zRouter.get_server_namer )r!urlrcCs$|tjjd|}||jd<|S)Nz Found at ZLocation)respondhttp HTTPStatusFOUNDr$)rr!r&responserrrredirect's zRouter.redirect)r!rcCs|tjjdS)Nz Not Found)r'r(r) NOT_FOUNDrr!rrr not_found,szRouter.not_foundResponse | Nonec Cs|jj||||jd}z(tj|j}|j|j|j d\}}WnLt yt}z| ||j WYd}~Sd}~0t y||YS0|||_|_dS)zRoute incoming request.)rr)Z path_infoZ query_argsN)rbindr%rurllibparseurlparsepathmatchqueryrr,new_urlrr/handlerhandler_kwargs)rr!r"Zurl_map_adapterparsedr9kwargsr,rrr route_request/s  " zRouter.route_requestcCs|j|fi|jS)zHandle a connection.)r9r:r.rrrr9DszRouter.handler)Nr) __name__ __module__ __qualname____doc__rr%r,r/r=r9rrrrrs r)rssl create_routerrrrz,ssl_module.SSLContext | Literal[True] | Noneztype[Router] | Noner )rargsrrBrCr<rcs|dur dnd}|dur(|dur(||d<|dur4t}|||||dddur\j}nddd d fd d }tjg|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.sync.router import route from werkzeug.routing import Map, Rule def channel_handler(websocket, channel_id): ... url_map = Map([ Rule("/channel/", endpoint=channel_handler), ... ]) with route(url_map, ...) as server: server.serve_forever() 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. NrwssTrBprocess_requestrr r0r cs"||}|dur|S||S)N)r=)r!r"r+Z_process_requestZrouterrrrFs zroute..process_request)rpopr=rr9)rrrBrCrDr<rrFrrGrrIsE  r)rr5r<rcKst|fd|d|S)aK Create a WebSocket Unix server dispatching connections to different handlers. :func:`unix_route` combines the behaviors of :func:`route` and :func:`~websockets.sync.server.unix_serve`. Args: url_map: Mapping of URL patterns to connection handlers. path: File system path to the Unix socket. T)unixr5)r)rr5r<rrrrsr)N) __future__rr(rBZ ssl_module urllib.parser2typingrrrZwerkzeug.exceptionsrZwerkzeug.routingrrZhttp11r r serverr rr__all__rrrrrrrs  :i