Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
/chiPublic

lightweight, idiomatic and composable router for building Go HTTP services

License

NotificationsYou must be signed in to change notification settings

go-chi/chi

Repository files navigation

chi

GoDoc Widget

chi is a lightweight, idiomatic and composable router for building Go HTTP services. It'sespecially good at helping you write large REST API services that are kept maintainable as yourproject grows and changes.chi is built on the newcontext package introduced in Go 1.7 tohandle signaling, cancelation and request-scoped values across a handler chain.

The focus of the project has been to seek out an elegant and comfortable design for writingREST API servers, written during the development of the Pressly API service that powers ourpublic API service, which in turn powers all of our client-side applications.

The key considerations of chi's design are: project structure, maintainability, standard httphandlers (stdlib-only), developer productivity, and deconstructing a large system into many smallparts. The core routergithub.com/go-chi/chi is quite small (less than 1000 LOC), but we've alsoincluded some useful/optional subpackages:middleware,renderanddocgen. We hope you enjoy it too!

Install

go get -u github.com/go-chi/chi/v5

Features

  • Lightweight - cloc'd in ~1000 LOC for the chi router
  • Fast - yes, seebenchmarks
  • 100% compatible with net/http - use any http or middleware pkg in the ecosystem that is also compatible withnet/http
  • Designed for modular/composable APIs - middlewares, inline middlewares, route groups and sub-router mounting
  • Context control - built on newcontext package, providing value chaining, cancellations and timeouts
  • Robust - in production at Pressly, Cloudflare, Heroku, 99Designs, and many others (seediscussion)
  • Doc generation -docgen auto-generates routing documentation from your source to JSON or Markdown
  • Go.mod support - as of v5, go.mod support (seeCHANGELOG)
  • No external dependencies - plain ol' Go stdlib + net/http

Examples

See_examples/ for a variety of examples.

As easy as:

package mainimport ("net/http""github.com/go-chi/chi/v5""github.com/go-chi/chi/v5/middleware")funcmain() {r:=chi.NewRouter()r.Use(middleware.Logger)r.Get("/",func(w http.ResponseWriter,r*http.Request) {w.Write([]byte("welcome"))})http.ListenAndServe(":3000",r)}

REST Preview:

Here is a little preview of what routing looks like with chi. Also take a look at the generated routing docsin JSON (routes.json) and inMarkdown (routes.md).

I highly recommend reading the source of theexamples listedabove, they will show you all the features of chi and serve as a good form of documentation.

import (//..."context""github.com/go-chi/chi/v5""github.com/go-chi/chi/v5/middleware")funcmain() {r:=chi.NewRouter()// A good base middleware stackr.Use(middleware.RequestID)r.Use(middleware.RealIP)r.Use(middleware.Logger)r.Use(middleware.Recoverer)// Set a timeout value on the request context (ctx), that will signal// through ctx.Done() that the request has timed out and further// processing should be stopped.r.Use(middleware.Timeout(60*time.Second))r.Get("/",func(w http.ResponseWriter,r*http.Request) {w.Write([]byte("hi"))  })// RESTy routes for "articles" resourcer.Route("/articles",func(r chi.Router) {r.With(paginate).Get("/",listArticles)// GET /articlesr.With(paginate).Get("/{month}-{day}-{year}",listArticlesByDate)// GET /articles/01-16-2017r.Post("/",createArticle)// POST /articlesr.Get("/search",searchArticles)// GET /articles/search// Regexp url parameters:r.Get("/{articleSlug:[a-z-]+}",getArticleBySlug)// GET /articles/home-is-toronto// Subrouters:r.Route("/{articleID}",func(r chi.Router) {r.Use(ArticleCtx)r.Get("/",getArticle)// GET /articles/123r.Put("/",updateArticle)// PUT /articles/123r.Delete("/",deleteArticle)// DELETE /articles/123    })  })// Mount the admin sub-routerr.Mount("/admin",adminRouter())http.ListenAndServe(":3333",r)}funcArticleCtx(next http.Handler) http.Handler {returnhttp.HandlerFunc(func(w http.ResponseWriter,r*http.Request) {articleID:=chi.URLParam(r,"articleID")article,err:=dbGetArticle(articleID)iferr!=nil {http.Error(w,http.StatusText(404),404)return    }ctx:=context.WithValue(r.Context(),"article",article)next.ServeHTTP(w,r.WithContext(ctx))  })}funcgetArticle(w http.ResponseWriter,r*http.Request) {ctx:=r.Context()article,ok:=ctx.Value("article").(*Article)if!ok {http.Error(w,http.StatusText(422),422)return  }w.Write([]byte(fmt.Sprintf("title:%s",article.Title)))}// A completely separate router for administrator routesfuncadminRouter() http.Handler {r:=chi.NewRouter()r.Use(AdminOnly)r.Get("/",adminIndex)r.Get("/accounts",adminListAccounts)returnr}funcAdminOnly(next http.Handler) http.Handler {returnhttp.HandlerFunc(func(w http.ResponseWriter,r*http.Request) {ctx:=r.Context()perm,ok:=ctx.Value("acl.permission").(YourPermissionType)if!ok||!perm.IsAdmin() {http.Error(w,http.StatusText(403),403)return    }next.ServeHTTP(w,r)  })}

Router interface

chi's router is based on a kind ofPatricia Radix trie.The router is fully compatible withnet/http.

Built on top of the tree is theRouter interface:

// Router consisting of the core routing methods used by chi's Mux,// using only the standard net/http.typeRouterinterface {http.HandlerRoutes// Use appends one or more middlewares onto the Router stack.Use(middlewares...func(http.Handler) http.Handler)// With adds inline middlewares for an endpoint handler.With(middlewares...func(http.Handler) http.Handler)Router// Group adds a new inline-Router along the current routing// path, with a fresh middleware stack for the inline-Router.Group(fnfunc(rRouter))Router// Route mounts a sub-Router along a `pattern` string.Route(patternstring,fnfunc(rRouter))Router// Mount attaches another http.Handler along ./pattern/*Mount(patternstring,h http.Handler)// Handle and HandleFunc adds routes for `pattern` that matches// all HTTP methods.Handle(patternstring,h http.Handler)HandleFunc(patternstring,h http.HandlerFunc)// Method and MethodFunc adds routes for `pattern` that matches// the `method` HTTP method.Method(method,patternstring,h http.Handler)MethodFunc(method,patternstring,h http.HandlerFunc)// HTTP-method routing along `pattern`Connect(patternstring,h http.HandlerFunc)Delete(patternstring,h http.HandlerFunc)Get(patternstring,h http.HandlerFunc)Head(patternstring,h http.HandlerFunc)Options(patternstring,h http.HandlerFunc)Patch(patternstring,h http.HandlerFunc)Post(patternstring,h http.HandlerFunc)Put(patternstring,h http.HandlerFunc)Trace(patternstring,h http.HandlerFunc)// NotFound defines a handler to respond whenever a route could// not be found.NotFound(h http.HandlerFunc)// MethodNotAllowed defines a handler to respond whenever a method is// not allowed.MethodNotAllowed(h http.HandlerFunc)}// Routes interface adds two methods for router traversal, which is also// used by the github.com/go-chi/docgen package to generate documentation for Routers.typeRoutesinterface {// Routes returns the routing tree in an easily traversable structure.Routes() []Route// Middlewares returns the list of middlewares in use by the router.Middlewares()Middlewares// Match searches the routing tree for a handler that matches// the method/path - similar to routing a http request, but without// executing the handler thereafter.Match(rctx*Context,method,pathstring)bool}

Each routing method accepts a URLpattern and chain ofhandlers. The URL patternsupports named params (ie./users/{userID}) and wildcards (ie./admin/*). URL parameterscan be fetched at runtime by callingchi.URLParam(r, "userID") for named parametersandchi.URLParam(r, "*") for a wildcard parameter.

Middleware handlers

chi's middlewares are just stdlib net/http middleware handlers. There is nothing specialabout them, which means the router and all the tooling is designed to be compatible andfriendly with any middleware in the community. This offers much better extensibility and reuseof packages and is at the heart of chi's purpose.

Here is an example of a standard net/http middleware where we assign a context key"user"the value of"123". This middleware sets a hypothetical user identifier on the requestcontext and calls the next handler in the chain.

// HTTP middleware setting a value on the request contextfuncMyMiddleware(next http.Handler) http.Handler {returnhttp.HandlerFunc(func(w http.ResponseWriter,r*http.Request) {// create new context from `r` request context, and assign key `"user"`// to value of `"123"`ctx:=context.WithValue(r.Context(),"user","123")// call the next handler in the chain, passing the response writer and// the updated request object with the new context value.//// note: context.Context values are nested, so any previously set// values will be accessible as well, and the new `"user"` key// will be accessible from this point forward.next.ServeHTTP(w,r.WithContext(ctx))  })}

Request handlers

chi uses standard net/http request handlers. This little snippet is an example of a http.Handlerfunc that reads a user identifier from the request context - hypothetically, identifyingthe user sending an authenticated request, validated+set by a previous middleware handler.

// HTTP handler accessing data from the request context.funcMyRequestHandler(w http.ResponseWriter,r*http.Request) {// here we read from the request context and fetch out `"user"` key set in// the MyMiddleware example above.user:=r.Context().Value("user").(string)// respond to the clientw.Write([]byte(fmt.Sprintf("hi %s",user)))}

URL parameters

chi's router parses and stores URL parameters right onto the request context. Here isan example of how to access URL params in your net/http handlers. And of course, middlewaresare able to access the same information.

// HTTP handler accessing the url routing parameters.funcMyRequestHandler(w http.ResponseWriter,r*http.Request) {// fetch the url parameter `"userID"` from the request of a matching// routing pattern. An example routing pattern could be: /users/{userID}userID:=chi.URLParam(r,"userID")// fetch `"key"` from the request contextctx:=r.Context()key:=ctx.Value("key").(string)// respond to the clientw.Write([]byte(fmt.Sprintf("hi %v, %v",userID,key)))}

Middlewares

chi comes equipped with an optionalmiddleware package, providing a suite of standardnet/http middlewares. Please note, any middleware in the ecosystem that is also compatiblewithnet/http can be used with chi's mux.

Core middlewares


chi/middleware Handlerdescription
AllowContentEncodingEnforces a whitelist of request Content-Encoding headers
AllowContentTypeExplicit whitelist of accepted request Content-Types
BasicAuthBasic HTTP authentication
CompressGzip compression for clients that accept compressed responses
ContentCharsetEnsure charset for Content-Type request headers
CleanPathClean double slashes from request path
GetHeadAutomatically route undefined HEAD requests to GET handlers
HeartbeatMonitoring endpoint to check the servers pulse
LoggerLogs the start and end of each request with the elapsed processing time
NoCacheSets response headers to prevent clients from caching
ProfilerEasily attach net/http/pprof to your routers
RealIPSets a http.Request's RemoteAddr to either X-Real-IP or X-Forwarded-For
RecovererGracefully absorb panics and prints the stack trace
RequestIDInjects a request ID into the context of each request
RedirectSlashesRedirect slashes on routing paths
RouteHeadersRoute handling for request headers
SetHeaderShort-hand middleware to set a response header key/value
StripSlashesStrip slashes on routing paths
SunsetSunset set Deprecation/Sunset header to response
ThrottlePuts a ceiling on the number of concurrent requests
TimeoutSignals to the request context when the timeout deadline is reached
URLFormatParse extension from url and put it on request context
WithValueShort-hand middleware to set a key/value on the request context

Extra middlewares & packages

Please seehttps://github.com/go-chi for additional packages.


packagedescription
corsCross-origin resource sharing (CORS)
docgenPrint chi.Router routes at runtime
jwtauthJWT authentication
hostrouterDomain/host based request routing
httplogSmall but powerful structured HTTP request logging
httprateHTTP request rate limiter
httptracerHTTP request performance tracing library
httpvcrWrite deterministic tests for external sources
stampedeHTTP request coalescer

context?

context is a tiny pkg that provides simple interface to signal context across call stacksand goroutines. It was originally written bySameer Ajmaniand is available in stdlib since go1.7.

Learn more athttps://blog.golang.org/context

and..

Benchmarks

The benchmark suite:https://github.com/pkieltyka/go-http-routing-benchmark

Results as of Nov 29, 2020 with Go 1.15.5 on Linux AMD 3950x

BenchmarkChi_Param          3075895        384 ns/op      400 B/op      2 allocs/opBenchmarkChi_Param5         2116603        566 ns/op      400 B/op      2 allocs/opBenchmarkChi_Param20         964117       1227 ns/op      400 B/op      2 allocs/opBenchmarkChi_ParamWrite     2863413        420 ns/op      400 B/op      2 allocs/opBenchmarkChi_GithubStatic   3045488        395 ns/op      400 B/op      2 allocs/opBenchmarkChi_GithubParam    2204115        540 ns/op      400 B/op      2 allocs/opBenchmarkChi_GithubAll        10000     113811 ns/op    81203 B/op    406 allocs/opBenchmarkChi_GPlusStatic    3337485        359 ns/op      400 B/op      2 allocs/opBenchmarkChi_GPlusParam     2825853        423 ns/op      400 B/op      2 allocs/opBenchmarkChi_GPlus2Params   2471697        483 ns/op      400 B/op      2 allocs/opBenchmarkChi_GPlusAll        194220       5950 ns/op     5200 B/op     26 allocs/opBenchmarkChi_ParseStatic    3365324        356 ns/op      400 B/op      2 allocs/opBenchmarkChi_ParseParam     2976614        404 ns/op      400 B/op      2 allocs/opBenchmarkChi_Parse2Params   2638084        439 ns/op      400 B/op      2 allocs/opBenchmarkChi_ParseAll        109567      11295 ns/op    10400 B/op     52 allocs/opBenchmarkChi_StaticAll        16846      71308 ns/op    62802 B/op    314 allocs/op

Comparison with other routers:https://gist.github.com/pkieltyka/123032f12052520aaccab752bd3e78cc

NOTE: the allocs in the benchmark above are from the calls to http.Request'sWithContext(context.Context) method that clones the http.Request, sets theContext()on the duplicated (alloc'd) request and returns it the new request object. This is justhow setting context on a request in Go works.

Credits

We'll be more than happy to seeyour contributions!

Beyond REST

chi is just a http router that lets you decompose request handling into many smaller layers.Many companies use chi to write REST services for their public APIs. But, REST is just a conventionfor managing state via HTTP, and there's a lot of other pieces required to write a complete client-serversystem or network of microservices.

Looking beyond REST, I also recommend some newer works in the field:

  • webrpc - Web-focused RPC client+server framework with code-gen
  • gRPC - Google's RPC framework via protobufs
  • graphql - Declarative query language
  • NATS - lightweight pub-sub

License

Copyright (c) 2015-presentPeter Kieltyka

Licensed underMIT License


[8]ページ先頭

©2009-2025 Movatter.jp