B h` @sdZddlZddlmZddlmZddlmZddlm Z m Z m Z ddl m Z ddlmZmZmZmZdd lmZmZmZmZmZmZmZmZmZGd d d ejZGd d d eZGdddej Z!Gdddej Z"eedeeeee#dfefeee#dfeee#effeee#dfeee#efe#ffZ$GdddeZ%Gdddee%Z&Gddde'Z(Gddde'Z)Gddde)Z*Gddde)Z+Gddde)Z,Gd d!d!e)Z-Gd"d#d#e(Z.ee#e/d$d%d&Z0eddd$d'd&Z0ee#ee/d$d(d&Z0dS))aqFlexible routing implementation. Tornado routes HTTP requests to appropriate handlers using `Router` class implementations. The `tornado.web.Application` class is a `Router` implementation and may be used directly, or the classes in this module may be used for additional flexibility. The `RuleRouter` class can match on more criteria than `.Application`, or the `Router` interface can be subclassed for maximum customization. `Router` interface extends `~.httputil.HTTPServerConnectionDelegate` to provide additional routing capabilities. This also means that any `Router` implementation can be used directly as a ``request_callback`` for `~.httpserver.HTTPServer` constructor. `Router` subclass must implement a ``find_handler`` method to provide a suitable `~.httputil.HTTPMessageDelegate` instance to handle the request: .. code-block:: python class CustomRouter(Router): def find_handler(self, request, **kwargs): # some routing logic providing a suitable HTTPMessageDelegate instance return MessageDelegate(request.connection) class MessageDelegate(HTTPMessageDelegate): def __init__(self, connection): self.connection = connection def finish(self): self.connection.write_headers( ResponseStartLine("HTTP/1.1", 200, "OK"), HTTPHeaders({"Content-Length": "2"}), b"OK") self.connection.finish() router = CustomRouter() server = HTTPServer(router) The main responsibility of `Router` implementation is to provide a mapping from a request to `~.httputil.HTTPMessageDelegate` instance that will handle this request. In the example above we can see that routing is possible even without instantiating an `~.web.Application`. For routing to `~.web.RequestHandler` implementations we need an `~.web.Application` instance. `~.web.Application.get_handler_delegate` provides a convenient way to create `~.httputil.HTTPMessageDelegate` for a given request and `~.web.RequestHandler`. Here is a simple example of how we can we route to `~.web.RequestHandler` subclasses by HTTP method: .. code-block:: python resources = {} class GetResource(RequestHandler): def get(self, path): if path not in resources: raise HTTPError(404) self.finish(resources[path]) class PostResource(RequestHandler): def post(self, path): resources[path] = self.request.body class HTTPMethodRouter(Router): def __init__(self, app): self.app = app def find_handler(self, request, **kwargs): handler = GetResource if request.method == "GET" else PostResource return self.app.get_handler_delegate(request, handler, path_args=[request.path]) router = HTTPMethodRouter(Application()) server = HTTPServer(router) `ReversibleRouter` interface adds the ability to distinguish between the routes and reverse them to the original urls using route's name and additional arguments. `~.web.Application` is itself an implementation of `ReversibleRouter` class. `RuleRouter` and `ReversibleRuleRouter` are implementations of `Router` and `ReversibleRouter` interfaces and can be used for creating rule-based routing configurations. Rules are instances of `Rule` class. They contain a `Matcher`, which provides the logic for determining whether the rule is a match for a particular request and a target, which can be one of the following. 1) An instance of `~.httputil.HTTPServerConnectionDelegate`: .. code-block:: python router = RuleRouter([ Rule(PathMatches("/handler"), ConnectionDelegate()), # ... more rules ]) class ConnectionDelegate(HTTPServerConnectionDelegate): def start_request(self, server_conn, request_conn): return MessageDelegate(request_conn) 2) A callable accepting a single argument of `~.httputil.HTTPServerRequest` type: .. code-block:: python router = RuleRouter([ Rule(PathMatches("/callable"), request_callable) ]) def request_callable(request): request.write(b"HTTP/1.1 200 OK\r\nContent-Length: 2\r\n\r\nOK") request.finish() 3) Another `Router` instance: .. code-block:: python router = RuleRouter([ Rule(PathMatches("/router.*"), CustomRouter()) ]) Of course a nested `RuleRouter` or a `~.web.Application` is allowed: .. code-block:: python router = RuleRouter([ Rule(HostMatches("example.com"), RuleRouter([ Rule(PathMatches("/app1/.*"), Application([(r"/app1/handler", Handler)]))), ])) ]) server = HTTPServer(router) In the example below `RuleRouter` is used to route between applications: .. code-block:: python app1 = Application([ (r"/app1/handler", Handler1), # other handlers ... ]) app2 = Application([ (r"/app2/handler", Handler2), # other handlers ... ]) router = RuleRouter([ Rule(PathMatches("/app1.*"), app1), Rule(PathMatches("/app2.*"), app2) ]) server = HTTPServer(router) For more information on application-level routing see docs for `~.web.Application`. .. versionadded:: 4.5 N)partial)httputil)_CallableAdapter) url_escape url_unescapeutf8)app_log)basestring_type import_object re_unescape unicode_type) AnyUnionOptional AwaitableListDictPatternTupleoverloadc@s@eZdZdZejeeejdddZ e ej ejdddZ dS) RouterzAbstract router interface.)requestkwargsreturncKs tdS)aMust be implemented to return an appropriate instance of `~.httputil.HTTPMessageDelegate` that can serve the request. Routing implementations may pass additional kwargs to extend the routing logic. :arg httputil.HTTPServerRequest request: current HTTP request. :arg kwargs: additional keyword arguments passed by routing implementation. :returns: an instance of `~.httputil.HTTPMessageDelegate` that will be used to process the request. N)NotImplementedError)selfrrrLC:\Users\sanjo\AppData\Local\Qlobot\Launcher\ext_packages\tornado\routing.py find_handlers zRouter.find_handler) server_conn request_connrcCs t|||S)N)_RoutingDelegate)rrr rrr start_requestszRouter.start_requestN) __name__ __module__ __qualname____doc__rHTTPServerRequestr rHTTPMessageDelegaterobjectHTTPConnectionr"rrrrrs  rc@s&eZdZdZeeeedddZdS)ReversibleRouterzxAbstract router interface for routers that can handle named routes and support reversing them to original urls. )nameargsrcGs tdS)aReturns url string for a given route name and arguments or ``None`` if no match is found. :arg str name: route name. :arg args: url parameters. :returns: parametrized url string for a given route name (or ``None``). N)r)rr,r-rrr reverse_urlszReversibleRouter.reverse_urlN)r#r$r%r&strr rr.rrrrr+sr+c@s~eZdZeeejddddZeej ej fej e e ddddZee e ddd d Zdd d d Zdd ddZdS)r!N)routerrr rcCs||_||_d|_||_dS)N)rr delegater0)rr0rr rrr__init__sz_RoutingDelegate.__init__) start_lineheadersrcCsjt|tjsttj|j|j||d}|j||_ |j dkr\t d|j |j t|j|_ |j ||S)N) connectionserver_connectionr3r4z$Delegate for %s %s request not found) isinstancerRequestStartLineAssertionErrorr'r rr0rr1rdebugmethodpath_DefaultMessageDelegateheaders_received)rr3r4rrrrr>s  z!_RoutingDelegate.headers_received)chunkrcCs|jdk st|j|S)N)r1r9 data_received)rr?rrrr@sz_RoutingDelegate.data_received)rcCs|jdk st|jdS)N)r1r9finish)rrrrrA sz_RoutingDelegate.finishcCs|jdk st|jdS)N)r1r9on_connection_close)rrrrrBsz$_RoutingDelegate.on_connection_close)r#r$r%rr)rr*r2rr8ResponseStartLine HTTPHeadersrrr>bytesr@rArBrrrrr!sr!c@s,eZdZejddddZddddZdS)r=N)r5rcCs ||_dS)N)r5)rr5rrrr2sz _DefaultMessageDelegate.__init__)rcCs*|jtdddt|jdS)NzHTTP/1.1iz Not Found)r5 write_headersrrCrDrA)rrrrrAs  z_DefaultMessageDelegate.finish)r#r$r%rr*r2rArrrrr=sr=RuleMatcherc@sxeZdZdZdeddddZeddddZddd d d Zej e e ej d d dZ e ej e e ej dddZdS) RuleRouterz!Rule-based router implementation.N)rulesrcCsg|_|r||dS)aIConstructs a router from an ordered list of rules:: RuleRouter([ Rule(PathMatches("/handler"), Target), # ... more rules ]) You can also omit explicit `Rule` constructor and use tuples of arguments:: RuleRouter([ (PathMatches("/handler"), Target), ]) `PathMatches` is a default matcher, so the example above can be simplified:: RuleRouter([ ("/handler", Target), ]) In the examples above, ``Target`` can be a nested `Router` instance, an instance of `~.httputil.HTTPServerConnectionDelegate` or an old-style callable, accepting a request argument. :arg rules: a list of `Rule` instances or tuples of `Rule` constructor arguments. N)rJ add_rules)rrJrrrr2/szRuleRouter.__init__cCsxxr|D]j}t|ttfr^t|dks(tt|dtrVtt|df|dd}nt|}|j | |qWdS)zAppends new rules to the router. :arg rules: a list of Rule instances (or tuples of arguments, which are passed to Rule constructor). )rN) r7tuplelistlenr9r rG PathMatchesrJappend process_rule)rrJrulerrrrKNs  zRuleRouter.add_rulesrG)rVrcCs|S)zOverride this method for additional preprocessing of each rule. :arg Rule rule: a rule to be processed. :returns: the same or modified Rule instance. r)rrVrrrrU^szRuleRouter.process_rule)rrrcKsVxP|jD]F}|j|}|dk r|jr0|j|d<|j|j|f|}|dk r|SqWdS)N target_kwargs)rJmatchermatchrWget_target_delegatetarget)rrrrV target_paramsr1rrrrfs   zRuleRouter.find_handler)r[rr\rcKspt|tr|j|f|St|tjrB|jdk s2t||j|jSt |rl|jdk sXtt t |f||jSdS)aReturns an instance of `~.httputil.HTTPMessageDelegate` for a Rule's target. This method is called by `~.find_handler` and can be extended to provide additional target types. :arg target: a Rule's target. :arg httputil.HTTPServerRequest request: current request. :arg target_params: additional parameters that can be useful for `~.httputil.HTTPMessageDelegate` creation. N) r7rrrHTTPServerConnectionDelegater5r9r"r6callablerr)rr[rr\rrrrZxs  zRuleRouter.get_target_delegate)N)r#r$r%r& _RuleListr2rKrUrr'r rr(rrZrrrrrI,s rIcsTeZdZdZd eddfdd Zdddfdd Zeee ed d d Z Z S)ReversibleRuleRouteraA rule-based router that implements ``reverse_url`` method. Each rule added to this router may have a ``name`` attribute that can be used to reconstruct an original uri. The actual reconstruction takes place in a rule's matcher (see `Matcher.reverse`). N)rJrcsi|_tt||dS)N) named_rulessuperr`r2)rrJ) __class__rrr2szReversibleRuleRouter.__init__rG)rVrcs@tt||}|jr<|j|jkr0td|j||j|j<|S)Nz4Multiple handlers named %s; replacing previous value)rbr`rUr,rarwarning)rrV)rcrrrUs   z!ReversibleRuleRouter.process_rule)r,r-rcGsZ||jkr|j|jj|Sx8|jD].}t|jtr$|jj|f|}|dk r$|Sq$WdS)N)rarXreverserJr7r[r+r.)rr,r-rV reversed_urlrrrr.s   z ReversibleRuleRouter.reverse_url)N) r#r$r%r&r_r2rUr/r rr. __classcell__rr)rcrr`s r`c@sReZdZdZd deeeefeddddZeeeddd Z ed d d Z dS)rGzA routing rule.NrH)rXr[rWr,rcCs6t|trt|}||_||_|r&|ni|_||_dS)adConstructs a Rule instance. :arg Matcher matcher: a `Matcher` instance used for determining whether the rule should be considered a match for a specific request. :arg target: a Rule's target (typically a ``RequestHandler`` or `~.httputil.HTTPServerConnectionDelegate` subclass or even a nested `Router`, depending on routing implementation). :arg dict target_kwargs: a dict of parameters that can be useful at the moment of target instantiation (for example, ``status_code`` for a ``RequestHandler`` subclass). They end up in ``target_params['target_kwargs']`` of `RuleRouter.get_target_delegate` method. :arg str name: the name of the rule that can be used to find it in `ReversibleRouter.reverse_url` implementation. N)r7r/r rXr[rWr,)rrXr[rWr,rrrr2s  z Rule.__init__)r-rcGs |jj|S)N)rXre)rr-rrrresz Rule.reverse)rcCsd|jj|j|j|j|jfS)Nz%s(%r, %s, kwargs=%r, name=%r))rcr#rXr[rWr,)rrrr__repr__s z Rule.__repr__)NN) r#r$r%r&r rr/r2rrerhrrrrrGs c@sBeZdZdZejeeee fdddZ e eedddZ dS) rHz*Represents a matcher for request features.)rrcCs tdS)a1Matches current instance against the request. :arg httputil.HTTPServerRequest request: current HTTP request :returns: a dict of parameters to be passed to the target handler (for example, ``handler_kwargs``, ``path_args``, ``path_kwargs`` can be passed for proper `~.web.RequestHandler` instantiation). An empty dict is a valid (and common) return value to indicate a match when the argument-passing features are not used. ``None`` must be returned to indicate that there is no match.N)r)rrrrrrYs z Matcher.match)r-rcGsdS)zEReconstructs full url from matcher instance and additional arguments.Nr)rr-rrrreszMatcher.reverseN) r#r$r%r&rr'rrr/r rYrerrrrrHs c@s.eZdZdZejeeee fdddZ dS) AnyMatcheszMatches any request.)rrcCsiS)Nr)rrrrrrYszAnyMatches.matchN) r#r$r%r&rr'rrr/r rYrrrrrisric@sFeZdZdZeeefddddZej e e ee fdddZ dS) HostMatchesz@Matches requests from hosts specified by ``host_pattern`` regex.N) host_patternrcCs4t|tr*|ds|d7}t||_n||_dS)N$)r7r endswithrecompilerk)rrkrrrr2s   zHostMatches.__init__)rrcCs|j|jriSdS)N)rkrY host_name)rrrrrrYszHostMatches.match)r#r$r%r&rr/rr2rr'rrr rYrrrrrjsrjc@s@eZdZdZeeddddZeje e e efdddZ dS) DefaultHostMatcheszMatches requests from host that is equal to application's default_host. Always returns no match if ``X-Real-Ip`` header is present. N) applicationrkrcCs||_||_dS)N)rrrk)rrrrkrrrr2szDefaultHostMatches.__init__)rrcCs"d|jkr|j|jjriSdS)Nz X-Real-Ip)r4rkrYrr default_host)rrrrrrY s zDefaultHostMatches.match) r#r$r%r&r rr2rr'rrr/rYrrrrrqsrqc@sxeZdZdZeeefddddZej e e ee fdddZ e e ed d d Zee ee efd d dZdS)rSz@Matches requests with paths specified by ``path_pattern`` regex.N) path_patternrcCslt|tr*|ds|d7}t||_n||_t|jjd|jjfksXt d|jj | \|_ |_ dS)NrlrzDgroups in url regexes must either be all named or all positional: %r)r7r rmrnroregexrR groupindexgroupsr9pattern _find_groups_path _group_count)rrtrrrr2+s   zPathMatches.__init__)rrcCsp|j|j}|dkrdS|jjs&iSg}i}|jjrRtdd|D}ndd|D}t||dS)Ncss"|]\}}t|t|fVqdS)N)r/_unquote_or_none).0kvrrr Jsz$PathMatches.match..cSsg|] }t|qSr)r|)r}srrr Msz%PathMatches.match..) path_args path_kwargs)rurYr<rwrvdict groupdictitems)rrrYrrrrrrY:szPathMatches.match)r-rcGs|jdkrtd|jjt||jks0tdt|s>|jSg}x8|D]0}t|tt fsbt |}| t t |ddqHW|jt|S)NzCannot reverse url regex z&required number of arguments not foundF)plus)rz ValueErrorrurxrRr{r9r7r rEr/rTrrrP)rr-converted_argsarrrreQs  zPathMatches.reverse)rc Cs|jj}|dr|dd}|dr4|dd}|jj|dkrJdSg}xt|dD]f}d|kr|d}|d kr|d ||ddqZy t |}Wnt k rdSX||qZWd ||jjfS) zReturns a tuple (reverse string, group count) for a url. For example: Given the url pattern /([0-9]{4})/([a-z-]+)/, this method would return ('/%s/%s/', 2). ^rONrl()NN)rz%s) rurx startswithrmrwcountsplitindexrTr rjoin)rrxpiecesfragmentZ paren_locZunescaped_fragmentrrrry`s&      zPathMatches._find_groups)r#r$r%r&rr/rr2rr'rrr rYrerintryrrrrrS(s rScsNeZdZdZd eeefeeeefeddfdd Z edddZ Z S) URLSpeczSpecifies mappings between URLs and handlers. .. versionchanged: 4.5 `URLSpec` is now a subclass of a `Rule` with `PathMatches` matcher and is preserved for backwards compatibility. N)rxhandlerrr,rcs8t|}tt||||||j|_|j|_||_dS)aParameters: * ``pattern``: Regular expression to be matched. Any capturing groups in the regex will be passed in to the handler's get/post/etc methods as arguments (by keyword if named, by position if unnamed. Named and unnamed capturing groups may not be mixed in the same rule). * ``handler``: `~.web.RequestHandler` subclass to be invoked. * ``kwargs`` (optional): A dictionary of additional arguments to be passed to the handler's constructor. * ``name`` (optional): A name for this handler. Used by `~.web.Application.reverse_url`. N)rSrbrr2rur[ handler_classr)rrxrrr,rX)rcrrr2s zURLSpec.__init__)rcCs d|jj|jj|j|j|jfS)Nz%s(%r, %s, kwargs=%r, name=%r))rcr#rurxrrr,)rrrrrhs zURLSpec.__repr__)NN) r#r$r%r&rr/rr rr2rhrgrr)rcrrs r)rrcCsdS)Nr)rrrrr|sr|cCsdS)Nr)rrrrr|scCs|dkr |St|dddS)zNone-safe wrapper around url_unescape to handle unmatched optional groups correctly. Note that args are passed as bytes so the handler can decide what encoding to use. NF)encodingr)r)rrrrr|s)1r&rn functoolsrtornadortornado.httpserverrtornado.escaperrr tornado.logr tornado.utilr r r r typingr rrrrrrrrr]rr+r(r!r=r/r_rIr`r)rGrHrirjrqrSrrEr|rrrrsB    ,.&h%1[1