Transfer timeout

How it works

Proxies, browsers, and servers each have one. A 60-second proxy idle timer kills a slow upload that is still making progress if the timer is wrong, or kills a stuck one if it is right. Resume makes the timeout a delay instead of a failure.

A proxy cuts POST at 120 seconds. A 3 GB upload on a slow link never finishes in one request. Chunks of 30 seconds each succeed. Raising the proxy timer also works and is harder politically.

How it differs

A timeout is not expiry of a link. One aborts a connection. The other refuses a URL.

Retries without resume repeat the same timeout.

Shorten the request or lengthen the timer.

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 timeout, 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 timeout 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.