UR::Se...Router(3pm)

💖 UR::Service::UrlRouter 💖

okay bestie, so this page lives in the User Contributed Perl Documentation section of the manual (it's a 3pm page, iykyk), and it's all about UR::Service::UrlRouter — a PSGI-aware router for incoming requests. yes. a router. for requests. it routes them. slay.

---

✨ SYNOPSIS ✨

my $r = UR::Service::UrlRouter->create();
$r->GET('/index.html', \&handle_index);
$r->POST(qr(update/(.*?).html, \&handle_update);

my $s = UR::Service::WebServer->create();
$s->run( $r );

(and yes, that second line is exactly what it is. we do not touch it. we do not fix it. we simply observe it with love 🫶)

---

🌸 DESCRIPTION 🌸

So basically this class is the middleman. the go-between. the group chat admin of your web app 💅 It takes requests coming in from a PSGI server and routes each one to the right function that's supposed to handle it. no cap, that's the whole job. match request → hand it to handler.

🎀 Properties

• verbose — if verbose is true, the object will print the details of the handled requests to STDOUT. loud and proud, honestly. it will narrate. 💀

🦋 Methods

$r->GET($URLish, $handler)

$r->POST($URLish, $handler)

$r->PUT($URLish, $handler)

$r->DELETE($URLisn, $handler)

These four — GET, POST, PUT, DELETE — are how you register a handler for a given request-method + URL pair. so: this method, this URL, that function. periodt.

The first argument is the URL to match against, and you can hand it over in one of these ways:

• $string — a plain string matches the incoming request when the request's path is eq to that $string. simple. literal. iconic.
• qr(some regex (with) captures) — a regex matches the incoming request when the path matches the regex. and here's the fun part 👀 if the regex has captures, those captures get passed as additional arguments to the $handler.
• $coderef — a coderef matches the incoming request if $coderef returns true. $coderef is given one argument: the PSGI env hashref.

and $handler? that's a CODE ref. when it gets called, the first argument it receives is the standard PSGI env hashref. always. that's the vibe.

$r->__call__

__call__ is not meant to be called directly. like, don't. 🙈

This class overloads the function dereference (call) operator so the object can be used as a callable object — as in $obj->(arg, arg). Because that's what overload expects, __call__ returns a code ref, and that code ref handles the PSGI request by finding an appropriate match between the incoming request and a handler you registered earlier. If nothing matches, it returns a 404 error code. bye 👋

And if multiple handlers match the incoming request? only the earliest registered handler gets called. first come, first served, no drama. 👑

---

👑 SEE ALSO 👑

UR::Service::WebServer, HTTP::Server::PSGI, Plack

---

that's the whole page, bestie!! ✨ this one's perl v5.32.1, dated 2022-01-17 — so go forth, route those requests, and remember: if nothing matches, it's a 404 and it's not your fault 💖🌈