Excel Filename Edge Cases
Before an application even parses the XML, it must successfully write the file to disk or an S3 bucket. Filename ingestion is a frequent source of bugs, particularly involving URL-encoding, shell injection via spaces, and Unicode normalization across different OS filesystems (e.g., macOS NFD vs Linux NFC).
These files isolate the upload and storage layers. They feature hostile filenames designed to break poor regex sanitization, trigger Cross-Site Scripting (XSS) filters, or exceed historical 260-character MAX_PATH constraints.
中文
Pure Chinese script.
Special !@#$%^&() chars
Hostile filename to test XSS filters and regex validators.
file [test]
Square brackets which break poor glob matchers.
Unicode テスト Файл
Mixed script to ensure complete Unicode support.
العربية
Pure Arabic script.
file & data
Ampersand to test strict XML/HTML escaping.
file #1
Hash symbol which breaks unencoded URL routing.
My Excel Test File
Standard spaces.
file (1)
Classic browser duplicate download pattern.
日本語
Pure Japanese script.
normal
Baseline alphanumeric file.
हिंदी
Pure Hindi script.
Spaces in filename
Tests shell escaping and `%20` URL encoding.
한국어
Pure Korean script.
Very Long Filename AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
Extremely long name to test `VARCHAR(255)` database limits and `MAX_PATH`.
தமிழ்
Pure Tamil script.
Frequently Asked Questions
Use Cases
- Testing S3/Blob upload routines to ensure spaces and brackets are correctly URL-encoded.
- Validating filename sanitization scripts to ensure they don't destroy valid foreign language characters.
- Testing `MAX_PATH` limitations on legacy Windows ingestion servers.