HTTP / HTTPS / WebSocket / HTTP/3
HTTP supports device APIs, web management and media delivery. WebSocket adds persistent application messages; HTTP/3 uses QUIC over UDP. The service URI and advertised configuration determine the actual port.
Scope: HTTP / HTTPS / WebSocket / HTTP/3 — requirements depend on the selected profile.
protocol · Catalog reviewed 2026-09-27
NetworkingOpen Standard
Infrastructure Requirements
- Reachable configured URI and listener
- authentication and TLS trust where required
- WebSocket/QUIC support through any intermediary when used.
Network & Physical Requirements
| Port / allocation | Transport | Connection / signal flow | Feature and requirement | Evidence |
|---|---|---|---|---|
| 80 (default) | TCP | Client → HTTP server | Profile requirement · Core HTTP / ws service HTTP URI default | Source checked 2026-09-27 RFC 9110, Section 4.2.1: http URI Scheme |
| 443 (default) | TCP | Client → HTTPS server | Profile requirement · Core HTTPS / wss service HTTPS URI default | Source checked 2026-09-27 RFC 9110, Section 4.2.2: https URI Scheme |
| 443 (default) | UDP | Client → HTTP/3 server | Optional · HTTP/3 HTTP/3 over QUIC HTTP/3 default where advertised | Source checked 2026-09-27 RFC 9114, Sections 3.1 and 3.2: discovery and connection establishment; HTTPS default from RFC 9110 §4.2.2 |
Gotchas & IT Notes
- ⚠Hostnames, proxy behavior, authentication and certificate trust matter as much as port numbers. Custom URI ports override defaults.
- ⚠WebSocket port follows its ws/wss URI; application framing and authorization are service-specific.