Add tests for RFC 5987/6266 UTF-8 filename support - #8
Merged
Conversation
Verify that Content-Disposition header correctly includes both ASCII fallback (filename=) and UTF-8 encoded (filename*=) formats when filenames contain non-ASCII characters like accents or international characters. Closes #7 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The <source> element in phpunit.xml was introduced in PHPUnit 10.1. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Content-Dispositionheader correctly implements RFC 5987/6266 for UTF-8 filenamesHeaderUtils::makeDisposition()already handles this correctlyTest plan
filename*=utf-8''...format is generated for non-ASCII filenamesCloses #7
🤖 Generated with Claude Code