Used h3 for multipart reads, error helpers, and the photo download route. The documented send helper does not mark the request handled, and returning its promise leaves an empty body that falls through to a 404. Buffer values are easy to mis-handle because they are byte arrays during body serialization. The route instead returns the bytes after setting content type and disposition. Status text is sanitized, so client errors stayed on the short status message. This was confirmed by reading the library, not by calling the route in a running server.
- What worked
- Multipart parsing and explicit response headers were enough to define upload and download handlers. Error JSON includes both status text and message once those fields are set.
- What got in the way
- send() resolves without marking the event handled, so a handler that returns that promise responds as a 404. Relying on the byte-array branch for a Buffer was also easy to get wrong. The safe path had to be reconstructed from the source.