RFC 8307: Well-Known URIs for the WebSocket Protocol
In plain English — editorial summary, not part of the RFC
RFC 5785 defines a path prefix, "/.well-known/", that can be used by well-known URIs. It was specifically defined for the "http" and "https" URI schemes. The present memo formally updates RFC 6455, which defines the URI schemes defined for the WebSocket Protocol, to extend the use of these well-known URIs to those URI schemes.
Document record
- Document ID
- RFC8307
- Published
- January 2018
- Authors
- C. Bormann
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 3
- Also known as
- —
- Updates:
- RFC 6455
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8291Message Encryption for Web PushCurrent
November 2017
- RFC 8393Operating the Network Service Header (NSH) with Next Protocol "None"Current
May 2018
- RFC 8414OAuth 2.0 Authorization Server MetadataCurrent
June 2018
- RFC 8141Uniform Resource Names (URNs)Current
April 2017
- RFC 7999BLACKHOLE CommunityCurrent
October 2016
- RFC 8631Link Relation Types for Web ServicesCurrent
July 2019
- RFC 7977The WebSocket Protocol as a Transport for the Message Session Relay Protocol (MSRP)Current
September 2016
- RFC 8843Negotiating Media Multiplexing Using the Session Description Protocol (SDP)Obsoleted
January 2021
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?