/Wiki/sources/honojs__hono/2026/https-hono-dev-llms-full-txt-definition-of-middl-eab0a2a823bd-definition-of-middleware-s0112-c0000.md
Definition of Middleware - hono-docs
Definition of Middleware Source evidence: /Sources/raw/honojs hono/honojs hono.md Canonical citation: https://hono.dev/llms full.txt definition of middleware...
Definition of Middleware
Source evidence: /Sources/raw/honojshono/honojshono.md Canonical citation: https://hono.dev/llms-full.txt#definition-of-middleware
Summary
- Handler - should return
Responseobject. Only one handler will be called. - Middleware - shouldawait next()and return nothing to call the next Middleware, or return aResponseto early-exit. The user can register middleware...
Content
- Handler - should return
Responseobject. Only one handler will be called. - Middleware - should
await next()and return nothing to call the next Middleware, or return aResponseto early-exit.
The user can register middleware using app.use or using app.HTTP_METHOD as well as the handlers. For this feature, it's easy to specify the path and the method.
// match any method, all routes
app.use(logger())
// specify path
app.use('/posts/*', cors())
// specify method and path
app.post('/posts/*', basicAuth())If the handler returns Response, it will be used for the end-user and will stop processing.
app.post('/posts', (c) => c.text('Created!', 201))In this case, four middleware are processed before dispatching like this:
logger() -> cors() -> basicAuth() -> *handler*
Kinic Wiki