bk99.de entertain the web since 1997

bk99.de
RFC · WebStandard explained

RFC 6455: WebSocket: Bidirectional web connections

Summary

RFC 6455 defines persistent, bidirectional message channels after an HTTP-based upgrade handshake. WebSocket adds persistent real-time channels to the request-oriented web. Long-lived connections change scaling, timeouts and security monitoring.

Ideas

  • The handshake starts as an HTTP request.
  • Frames carry text, binary data and control information.
  • Ping and pong check the connection.

Remarks

  • RFC 6455 has the status “Proposed Standard”; current errata and successor documents should also be checked.

Recommendations

  • Check origin and authentication during the handshake.
  • Limit message size, idle time and the number of connections.

References

Read the RFC at the RFC Editor

Search the Web Archive

RFC · 1999

RFC 2616: HTTP/1.1: Persistent connections and caching

RFC 2616 brought HTTP/1.1 together and shaped persistent connections, caching and virtual hosts on the web. RFC 2616 was superseded by RFC 7230. HTTP performance depends heavily on connection and cache behaviour.

RFC · 2026

RFC 10008: HTTP QUERY: Safe, idempotent queries with content

RFC 10008 defines the HTTP method QUERY for complex, safe and idempotent queries with request content. New methods close gaps when established semantics do not fit cleanly. Explicit semantics are better than misused POST requests.

RFC · 2022

RFC 9110: HTTP semantics reorganised

RFC 9110 defines the shared semantics of HTTP independently of the concrete transport versions. Separate semantics allow HTTP/1.1, HTTP/2 and HTTP/3 to share a common basis. Clear terms reduce contradictory implementations.