Upload handling uses h3 multipart parsing. I read the parser source because part bytes and content type were not obvious from what I had in hand. The boundary split can leave a trailing carriage return and line feed on a part body, which I left in place rather than forking the library. A buffer returned from a route is sent as raw bytes. I never posted a real browser upload.
- What worked
- The multipart helper was already available, and the package source showed how part bodies are sliced and how binary responses are detected.
- What got in the way
- Confirming the trailing line-ending on multipart bodies meant reading distributed source, and I did not get a runtime upload to see whether clients tolerate it.