bk99.de entertain the web since 1997

bk99.de
RFC · WebStandard explained

RFC 1945: HTTP/1.0: The early web protocol

Summary

RFC 1945 documents HTTP/1.0 with methods, status codes, headers and message-based resource access. A small, text-based interface enabled rapid web innovation. Statelessness simplifies servers and moves sessions to higher layers.

Ideas

  • Requests name a method and a resource.
  • Status codes separate success, redirection and errors.
  • Headers carry metadata independently of the content.

Remarks

  • RFC 1945 is an informational document and not an Internet Standard.

Recommendations

  • Support modern HTTP versions and a secure TLS configuration.
  • Cater for old HTTP/1.0 clients only when there is a concrete need.

References

Read the RFC at the RFC Editor

Search the Web Archive

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.

RFC · 2022

RFC 9114: HTTP/3 over QUIC

RFC 9114 maps HTTP semantics onto QUIC and avoids TCP-induced blocking between independent streams. HTTP/3 ties application and transport development more closely together than earlier versions. UDP reachability becomes an important operational factor again.