Targets, origins & intermediaries
02A URI identifies the resource. Proxies and gateways may sit between the caller and its origin.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 4.3 ↗
RFC 9110 · § 4.3EXAMPLE
3 / 3
03
Establish HTTPS authority.
The TLS connection and certificate checks establish the expected server identity.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Route a request without losing the target authority.
- An origin is identified by its scheme, host, and port.
- Host or :authority conveys authority information; routing must honor the target URI.
- HTTPS requires an authenticated secure connection and certificate identity checks.
An intermediary can forward, cache, or transform under defined rules. Connection-specific fields must not be blindly forwarded to the next hop.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy