rfc-8307

Well-Known URIs for the WebSocket Protocol

C. Bormann

date2018-01 streamIETF wgnon working group statusPROPOSED STANDARD pages3 canonicalhttps://www.rfc-editor.org/rfc/rfc8307 doi10.17487/RFC8307

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.

updates

rfc-6455 — The WebSocket Protocol

Extracted elements (5)

design-rationale §3

It was already possible to form 'ws' and 'wss' URIs that map to well-known HTTP(S) URIs via the procedure in Section 4 of RFC 6455; this memo formalizes that relationship rather than introducing new mechanism.

websocket, http

interoperability-note §1

Well-known URIs for 'ws' and 'wss' share the existing registry for URI suffixes established by RFC 5785; no change to the registry or its IANA considerations is required by this memo.

websocket, registry

normative-requirement §1 REQUIRED

RFC 6455 is formally updated to extend the use of RFC 5785 well-known URIs (path prefix '/.well-known/') to the 'ws' and 'wss' URI schemes defined for the WebSocket Protocol.

websocket

registry §2

This document requires no IANA actions; 'ws' and 'wss' well-known URIs reuse the existing RFC 5785 URI suffixes registry without modification.

registry, websocket

security-consideration §3

The Security Considerations of RFC 5785 apply to all well-known URIs under 'ws' and 'wss'. Applications defining well-known URI suffixes for WebSocket use must consider whether equivalent HTTP(S) resources (formed via RFC 6455 Section 4) pose information disclosure or other security risks.

websocket, security