bk99.de entertain the web since 1997

bk99.de
RFC · WebStandard explained

RFC 2616: HTTP/1.1: Persistent connections and caching

Summary

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.

Ideas

  • The Host header allows several websites per address.
  • Persistent connections save repeated handshakes.
  • Cache rules control reuse and validation.

Insights

  • A monolithic standard was later split up to make maintenance easier.

Remarks

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

Recommendations

  • Use the RFC 9110 family as the current reference.
  • Test cache headers with browsers and intermediate proxies.

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.