bk99.de entertain the web since 1997

bk99.de
RFC · WebStandard explained

RFC 1738: URLs: Uniform addresses for internet resources

Summary

RFC 1738 standardises the syntax and schemes of URLs for various internet services. RFC 1738 was superseded by RFC 4248. Stable addresses made distributed resources reliably referenceable.

Ideas

  • A scheme determines interpretation and access method.
  • Hierarchical parts describe host, port and path.
  • Percent encoding carries reserved characters.

Insights

  • Address syntax becomes a permanent public interface.

Remarks

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

Recommendations

  • Use permanent, readable HTTPS addresses.
  • Keep implementation details and session data out of public URLs.

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.