HTTP Transport

Tags: wire, transport, message-flow

© R.A.Sol

The HTTP endpoint carries one complete HPPR request packet in one HTTP POST request and returns one complete HPPR response packet.

Via: http+host[:port] (033). Default port: 80.

Advertised in HELLO or equivalent endpoint greeting metadata as:

Transport: http:<port> flow=message path=/hppr

Protocol

POST /hppr
Content-Type: protocol/hppr
Accept: protocol/hppr

<raw HPPR request packet>

Rules:

• the default endpoint path is /hppr
• the HTTP path selects only the HPPR packet endpoint; command, auth, target, and payload remain inside the HPPR request packet
• successful HTTP parsing returns 200 OK with Content-Type: protocol/hppr, including HPPR Null error packets for protocol-level errors
• malformed HTTP uses HTTP errors such as 400, 405, 411, 413, and 415
• Transfer-Encoding and chunked request bodies are not accepted
• the connection closes after each response
• stream commands are not accepted

The entity media type is protocol/hppr. Implementations must treat it as an explicit HPPR convention and must not apply text, mail, or CRLF normalization.

Repository HTTP Message Flow

Repository HTTP is a message-flow endpoint. Its concrete request envelope and command set are defined in 044.

Repository HTTP HELLO is capability/provisioning discovery and does not create a usable session binding.

HTTP listeners are explicit. all transport binding does not expose HTTP. A repository service advertises Transport: http:<port> flow=message path=/hppr only when an HTTP listener is active.