tests: cover non-ASCII filename encoding in Content-Disposition - #331
Conversation
* added a café résumé.pdf case to TestServeSetHeadersContentDisposition, exercising url.PathEscape for filename* (spaces + multi-byte UTF-8). * documents current behavior: legacy filename keeps raw UTF-8 bytes.
|
/review AI review started. |
Advanced AI Review
Click to expand reviewReview:
|
|
@taoeffect approved! ✅ |
Closes #303
AI Disclosure
Co-authored with: Opus 5