Connection limit

How it works

A parallel upload that opens 32 sessions can hit the cap and fail the extras. Reusing a session or capping parallelism stays under it. The error looks like a refusal, not a slow transfer.

A script opens 20 SFTP sessions for 20 files. The server allows 5. Fifteen fail. A pool of 5 finishes the set. The files were fine. The fan-out was not.

How it differs

A connection limit is not a bandwidth throttle. You can be under the rate cap and over the session cap.

NAT makes many users look like one address and they share the cap.

Identify by user where you can.

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 connection limit, 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 connection limit 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.