bk99.de entertain the web since 1997

bk99.de
RFC · WebStandard explained

RFC 6585: Additional HTTP status codes

Summary

RFC 6585 adds 428, 429, 431 and 511, among others, to HTTP for more precise error states. Precise error codes make automated reactions more reliable. Rate limits need clear feedback in addition to rejection.

Ideas

  • 428 requires conditional changes to prevent lost updates.
  • 429 signals too many requests.
  • 431 rejects oversized headers.

Remarks

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

Recommendations

  • Send Retry-After with 429 where possible.
  • Limit header sizes consistently across proxy and application layers.

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.