Unicode filename

How it works

macOS often stores decomposed accents. Windows stores composed. A hash of the bytes can match while a name compare fails. ZIP tools differ on UTF-8 flags. Prefer ASCII names on partner drops if you do not control both ends.

A file named café.pdf uploads from a Mac and fails to overwrite café.pdf from Windows. Two keys exist. They rename to cafe.pdf on the partner path and keep the pretty name only in a portal label.

How it differs

The filename is not the object key unless you make it so. A generated key avoids this class of bug.

A manifest that compares names without normalization false-fails a good set.

Normalize or avoid accents on the wire.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For unicode filename, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive unicode filename files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.