1.3 KiB
1.3 KiB
Pages Functions Request Design
Choose where behavior belongs before adapting an example.
| Task | Documentation |
|---|---|
| Share authentication, logging, and error handling | Middleware |
| Choose request handlers and asynchronous completion behavior | API reference |
| Keep asset requests outside Function invocation where appropriate | Routing |
| Use custom or framework-generated routing | Advanced mode |
| Integrate storage or another service | Bindings |
| Exercise the assembled application locally | Local development |
Define the response owner and middleware scope before adding authentication or response transformations. Test protected routes, rejected requests, and static fallbacks together. Choose consistency and concurrency requirements before using storage for session state or rate limiting; a generic read-modify-write example is not a complete policy.
See Pages project decisions for framework and migration work.