RFC 1945

RFC 1945
Title	RFC 1945
Status	Informational
Author	{Tim Berners-Lee; Henning Schulzrinne}
Date	1996-05
Pages	22
Category	Hypertext

RFC 1945

RFC 1945 is the document that specifies the Hypertext Transfer Protocol -- HTTP/1.0, published in May 1996. It defines the protocol used by the World Wide Web for communication between web browsers and web servers, establishing message formats, status codes, methods, and header fields that underpin interactions across systems developed by organizations such as CERN, MIT, and the World Wide Web Consortium. The specification influenced subsequent standards and implementations in software projects like Netscape Navigator, Apache HTTP Server, and Microsoft Internet Explorer.

Introduction

RFC 1945 introduces HTTP/1.0 as an application-level protocol for distributed, collaborative, hypermedia information systems, originating from work at CERN and formalized through collaboration with groups including IETF and W3C. It situates HTTP among contemporaneous protocols such as FTP, SMTP, and Gopher, and frames goals aligned with interoperability pursued by projects like Mosaic and NCSA. The document addresses message syntax, request methods, response semantics, and connection management in the context of implementations like libwww and servers derived from NCSA HTTPd.

History and Development

The development of HTTP/1.0 traces to early hypertext research at CERN led by figures associated with Tim Berners-Lee, with parallel contributions from researchers affiliated with MIT, NCSA, and the IETF HTTP Working Group. RFC 1945 emerged from an evolutionary path including experimental drafts and earlier notes that influenced standards work in organizations such as the World Wide Web Consortium and the Internet Engineering Task Force. Commercial vendors including Netscape Communications Corporation and Microsoft Corporation implemented HTTP features that shaped practical interoperability issues addressed during the drafting process, while academic projects at University of Illinois and University of Geneva contributed reference implementations and test suites.

Technical Overview

RFC 1945 specifies HTTP as a stateless, request-response protocol using textual messages exchanged over Transmission Control Protocol connections defined by IETF standards. Messages comprise start-lines, header fields, and optional message bodies, employing status codes and reason phrases analogous to conventions in RFC 822 and interaction patterns familiar from SMTP and FTP. The protocol defines methods such as GET, POST, HEAD, and OPTIONS, and header fields including Host, User-Agent, Content-Type, and Content-Length, influencing web architecture discussions involving REST principles and later work by groups around Roy Fielding and W3C.

Protocol Specifications

RFC 1945 enumerates the syntax and semantics for request methods, response status codes (1xx–5xx ranges), header field definitions, entity bodies, and content negotiation mechanisms like Accept and Content-Encoding. It specifies message formatting rules drawing on standards such as ASCII and earlier specifications like RFC 822 and RFC 1123, and addresses connection management via the Connection header and rules for persistent versus non-persistent connections later revisited in subsequent RFCs. The document also defines semantics for caching-related headers (Expires, Cache-Control concepts) that influenced cache implementations in systems like Squid and browser caches in Opera Software releases.

Implementation and Impact

Implementations of RFC 1945 in servers and clients—examples include NCSA HTTPd, Apache HTTP Server, Netscape Navigator, and early Microsoft Internet Explorer—shaped the rapid expansion of the World Wide Web and the commercial internet ecosystem through the late 1990s. RFC 1945 informed interoperability testing, influenced later specifications like HTTP/1.1 and standards work at the IETF HTTP Working Group, and affected platform vendors such as Sun Microsystems and open-source projects hosted by organizations like the Apache Software Foundation. The protocol’s design choices impacted content delivery networks developed by companies like Akamai Technologies and informed academic studies at institutions such as Stanford University and Carnegie Mellon University.

Security Considerations

While RFC 1945 focuses on syntax and semantics, it acknowledges security implications related to authentication, privacy, and trust, leaving details to complementary mechanisms like TLS and authentication schemes later standardized by the IETF. Early implementations exposed risks exploited in incidents studied by researchers at CERT Coordination Center and discussed in security analyses by groups at SANS Institute and NIST. Subsequent protocol work addressed these concerns through extensions and successor specifications integrating cryptographic protections associated with Transport Layer Security and authentication frameworks used in enterprise environments such as those defined by RFC 2617.

Category:Internet standards