HTTP

How it works

RFC 9110 defines GET, PUT, and POST. Cleartext HTTP on port 80 lets a path observer read the file. Modern transfers use HTTPS. The methods do not change.

A legacy device still PUTs a 50 MB log to http://collector.example. The file arrives. Anyone on that network can read it. Moving the collector to HTTPS keeps the same PUT and closes the path.

How it differs

HTTP is not FTP. There is no separate data port. It is not HTTPS until TLS wraps it.

A redirect from HTTPS to HTTP mid-download can leak the rest of the file.

Refuse that redirect for file bodies.

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