github.com/elasticperch/mux (go): Package mux implements a request router and dispatcher.  The name mux stands for "HTTP request multiplexer". Like the standard http.ServeMux, mux.Router matches incoming requests against a list of registered routes and calls a handler for the route that matches the URL or other conditions. The main features are:  Let's start registering a couple of URL paths and handlers:  Here we register three routes mapping URL paths to handlers. This is equivalent to how http.HandleFunc() works: if an incoming request URL matches one of the paths, the corresponding handler is called passing (http.ResponseWriter, *http.Request) as parameters.  Paths can have variables. They are defined using the format {name} or {name:pattern}. If a regular expression pattern is not defined, the matched variable will be anything until the next slash. For example:  Groups can be used inside patterns, as long as they are non-capturing (?:re). For example:  The names are used to create a map of route variables which can be retrieved calling mux.Vars():  Note that if any capturing groups are present, mux will panic() during parsing. To prevent this, convert any capturing groups to non-capturing, e.g. change "/{sort:(asc|desc)}" to "/{sort:(?:asc|desc)}". This is a change from prior versions which behaved unpredictably when capturing groups were present.  And this is all you need to know about the basic usage. More advanced options are explained below.  Routes can also be restricted to a domain or subdomain. Just define a host pattern to be matched. They can also have variables:  There are several other matchers that can be added. To match path prefixes:  ...or HTTP methods:  ...or URL schemes:  ...or header values:  ...or query values:  ...or to use a custom matcher function:  ...and finally, it is possible to combine several matchers in a single route:  Setting the same matching conditions again and again can be boring, so we have a way to group several routes that share the same requirements. We call it "subrouting".  For example, let's say we have several URLs that should only match when the host is "www.example.com". Create a route for that host and get a "subrouter" from it:  Then register routes in the subrouter:  The three URL paths we registered above will only be tested if the domain is "www.example.com", because the subrouter is tested first. This is not only convenient, but also optimizes request matching. You can create subrouters combining any attribute matchers accepted by a route.  Subrouters can be used to create domain or path "namespaces": you define subrouters in a central place and then parts of the app can register its paths relatively to a given subrouter.  There's one more thing about subroutes. When a subrouter has a path prefix, the inner routes use it as base for their paths:  Note that the path provided to PathPrefix() represents a "wildcard": calling PathPrefix("/static/").Handler(...) means that the handler will be passed any request that matches "/static/*". This makes it easy to serve static files with mux:  Now let's see how to build registered URLs.  Routes can be named. All routes that define a name can have their URLs built, or "reversed". We define a name calling Name() on a route. For example:  To build a URL, get the route and call the URL() method, passing a sequence of key/value pairs for the route variables. For the previous route, we would do:  ...and the result will be a url.URL with the following path:  This also works for host and query value variables:  All variables defined in the route are required, and their values must conform to the corresponding patterns. These requirements guarantee that a generated URL will always match a registered route -- the only exception is for explicitly defined "build-only" routes which never match.  Regex support also exists for matching Headers within a route. For example, we could do:  ...and the route will match both requests with a Content-Type of `application/json` as well as `application/text`  There's also a way to build only the URL host or path for a route: use the methods URLHost() or URLPath() instead. For the previous route, we would do:  And if you use subrouters, host and path defined separately can be built as well:  Mux supports the addition of middlewares to a Router, which are executed in the order they are added if a match is found, including its subrouters. Middlewares are (typically) small pieces of code which take one request, do something with it, and pass it down to another middleware or the final handler. Some common use cases for middleware are request logging, header manipulation, or ResponseWriter hijacking.  Typically, the returned handler is a closure which does something with the http.ResponseWriter and http.Request passed to it, and then calls the handler passed as parameter to the MiddlewareFunc (closures can access variables from the context where they are created).  A very basic middleware which logs the URI of the request being handled could be written as:  Middlewares can be added to a router using `Router.Use()`:  A more complex authentication middleware, which maps session token to users, could be written as:  Note: The handler chain will be stopped if your middleware doesn't call `next.ServeHTTP()` with the corresponding parameters. This can be used to abort a request if the middleware writer wants to.
Keywords: go|golang|mux|mux-router