Nitro
Mount the Files gateway in a Nitro (or Nuxt server) route, on Nitro 2 (h3 1) or Nitro 3 (h3 2). Hands the gateway a Web Request and returns the Response for Nitro to flush.
files-sdk/nitro mounts a createFilesRouter in a Nitro route (and therefore Nuxt server routes). It works with both h3 majors: on Nitro 3 (h3 2) the event already carries a Web Request, which goes to the gateway as-is; on Nitro 2 (h3 1) the binding marshals the Node request on event.node.req into one. Either way it returns the Web Response for Nitro to flush, and a client disconnect aborts the upstream read on a proxied download.
import { createFiles } from "files-sdk";
import { r2 } from "files-sdk/r2";
import { createFilesRouter } from "files-sdk/api";
import { createRouteHandler } from "files-sdk/nitro";
const router = createFilesRouter({
files: createFiles({ adapter: r2({ bucket: "uploads" }) }),
allowedOrigins: ["https://app.example.com"],
authorize: async ({ req }) => {
/* throw to deny, or return a per-user constraint — see /ui/server/authorization */
},
});
// Nitro 2 and Nuxt 4 (put this at server/routes/api/files.ts in Nuxt).
export default defineEventHandler(createRouteHandler(router));
Nitro 3 drops auto-imports, so import defineHandler from nitro:
import { defineHandler } from "nitro";
export default defineHandler(createRouteHandler(router));
Behind a proxy that terminates TLS, Nitro 3’s Node server builds event.req.url from the connection rather than x-forwarded-proto, so the request looks like plain http. If you rely on the gateway’s default same-origin check instead of allowedOrigins, a browser POST from your https origin is then rejected; list the origin in allowedOrigins as above.
See the gateway options for the full configuration and the authorize model for locking it down.