RFC 2818: HTTP Over TLS

This memo describes how to use Transport Layer Security (TLS) to secure Hypertext Transfer Protocol (HTTP) connections over the Internet. This memo provides…

Read RFC 2818 on the RFC Editor

Incoming relationships (102 related RFCs)

Showing 50 of 102 related RFCs.

Updated by — RFC 7230: Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
Updated by — RFC 5785: Defining Well-Known Uniform Resource Identifiers (URIs)
Obsoleted by — RFC 9110: HTTP Semantics
Normatively referenced by — RFC 6749: The OAuth 2.0 Authorization Framework
Normatively referenced by — RFC 7517: JSON Web Key (JWK)
Normatively referenced by — RFC 6750: The OAuth 2.0 Authorization Framework: Bearer Token Usage
Normatively referenced by — RFC 7540: Hypertext Transfer Protocol Version 2 (HTTP/2)
Normatively referenced by — RFC 4791: Calendaring Extensions to WebDAV (CalDAV)
Normatively referenced by — RFC 7481: Security Services for the Registration Data Access Protocol (RDAP)
Normatively referenced by — RFC 5216: The EAP-TLS Authentication Protocol
Normatively referenced by — RFC 4825: The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)
Normatively referenced by — RFC 5985: HTTP-Enabled Location Delivery (HELD)
Normatively referenced by — RFC 6797: HTTP Strict Transport Security (HSTS)
Normatively referenced by — RFC 7838: HTTP Alternative Services
Normatively referenced by — RFC 8827: WebRTC Security Architecture
Normatively referenced by — RFC 6920: Naming Things with Hashes
Normatively referenced by — RFC 5023: The Atom Publishing Protocol
Normatively referenced by — RFC 5986: Discovering the Local Location Information Server (LIS)
Normatively referenced by — RFC 6546: Transport of Real-time Inter-network Defense (RID) Messages over HTTP/TLS
Normatively referenced by — RFC 6940: REsource LOcation And Discovery (RELOAD) Base Protocol
Normatively referenced by — RFC 5849: The OAuth 1.0 Protocol
Normatively referenced by — RFC 7975: Request Routing Redirection Interface for Content Delivery Network (CDN) Interconnection
Normatively referenced by — RFC 6352: CardDAV: vCard Extensions to Web Distributed Authoring and Versioning (WebDAV)
Normatively referenced by — RFC 6503: Centralized Conferencing Manipulation Protocol
Normatively referenced by — RFC 8801: Discovering Provisioning Domain Names and Data
Normatively referenced by — RFC 4827: An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Manipulating Presence Document Contents
Normatively referenced by — RFC 5408: Identity-Based Encryption Architecture and Supporting Data Structures
Normatively referenced by — RFC 6231: An Interactive Voice Response (IVR) Control Package for the Media Control Channel Framework
Normatively referenced by — RFC 7711: PKIX over Secure HTTP (POSH)
Normatively referenced by — RFC 7808: Time Zone Data Distribution Service
Normatively referenced by — RFC 8164: Opportunistic Security for HTTP/2
Normatively referenced by — RFC 8823: Extensions to Automatic Certificate Management Environment for End-User S/MIME Certificates
Normatively referenced by — RFC 4002: IANA Registration for Enumservice 'web' and 'ft'
Normatively referenced by — RFC 5278: IANA Registration of Enumservices for Voice and Video Messaging
Normatively referenced by — RFC 6046: Transport of Real-time Inter-network Defense (RID) Messages
Normatively referenced by — RFC 6638: Scheduling Extensions to CalDAV
Normatively referenced by — RFC 6739: Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol
Normatively referenced by — RFC 6764: Locating Services for Calendaring Extensions to WebDAV (CalDAV) and vCard Extensions to WebDAV (CardDAV)
Normatively referenced by — RFC 7035: Relative Location Representation
Normatively referenced by — RFC 8336: The ORIGIN HTTP/2 Frame
Normatively referenced by — RFC 8876: Non-interactive Emergency Calls
Normatively referenced by — RFC 8908: Captive Portal API
Normatively referenced by — RFC 8935: Push-Based Security Event Token (SET) Delivery Using HTTP
Normatively referenced by — RFC 8936: Poll-Based Security Event Token (SET) Delivery Using HTTP
Normatively referenced by — RFC 8952: Captive Portal Architecture
Normatively referenced by — RFC 9092: Finding and Using Geofeed Data
Normatively referenced by — RFC 5854: The Metalink Download Description Format
Normatively referenced by — RFC 6011: Session Initiation Protocol (SIP) User Agent Configuration
Normatively referenced by — RFC 6109: La Posta Elettronica Certificata - Italian Certified Electronic Mail
Normatively referenced by — RFC 6338: Definition of a Uniform Resource Name (URN) Namespace for the Schema for Academia (SCHAC)