Skip to Content
Senri
Requests and responses

Context

What you can do with c, which handlers and middleware receive

A handler's second argument and a middleware's first argument are the Context (c) of the request.

import {  } from "@senrijs/senri";

const  = <{ : string }>();

.(async (, ) => {
    .("user", "alice");          // pass a value to the handler
    await ();
});

.("/users/:id", ({  }, ) => {
    .("cache-control", "no-store");
    return { , : .("user"), : .("page") };
});

Read the request

WriteWhat it is
c.reqThe real Request
c.pathThe normalized, decoded path
c.routeThe pattern of the matched route ("/users/:id"), or undefined
c.paramsThe path parameters (the same as the handler's first argument)
c.query(name) / c.query()One query value / all of them
c.queries(name)All values of a query name (an array)
c.body()Reads the body by its Content-Type (Request bodies and limits)
c.bodyJson() / c.bodyBytes()Reads the body as JSON / an ArrayBuffer, whatever its Content-Type
c.valid(target)The values checked by a schema (Validation)

c.route and c.params can be read in middleware before next(), because the route is decided before middleware runs.

Decide the response

WriteWhat it does
c.status(code)Sets the status of the value you return
c.header(name, value)Adds a header to the response
c.json(), c.text(), c.html(), c.redirect()Make a Response (Response helpers)
c.notFound()Hands over to the 404 handler (Not found)

Headers added with c.header() are added to the response once, at the end. They are added even when you return a Response directly, and on errors. Content-Type and Location in the response itself win, though.

Pass values (c.set / c.get)

To pass values from middleware to the handler, use c.set() and c.get(). Set their types as in createApp<{ user: string }>(), or from the middleware's type (Writing middleware).

env and ctx on Cloudflare Workers

c.env and c.executionCtx give the Workers bindings and waitUntil() (Cloudflare Workers).

On this page