Windows file transfer

How it works

Reserved names (CON, AUX), trailing dots, and backslashes break naive syncs. Tools that preserve alternate data streams lose them on a bucket. Path length limits still appear in older apps.

A folder containing aux.png fails to copy onto Windows. Renaming the file fixes the job. The Linux sender never noticed. The delivery note now forbids reserved names.

How it differs

Windows file transfer is not SMB-only. A browser upload from Windows is HTTPS.

Copy dialogs that skip errors finish green with missing files.

Use a manifest.

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 windows file transfer, 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 windows file transfer 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.