IPP Mail Archive: IPP> FW: RFC 2616 on HTTP/1.1

IPP Mail Archive: IPP> FW: RFC 2616 on HTTP/1.1

IPP> FW: RFC 2616 on HTTP/1.1

Manros, Carl-Uno B (cmanros@cp10.es.xerox.com)
Mon, 14 Jun 1999 13:34:21 -0700

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

Content-Type: text/plain;



-----Original Message-----
From: RFC Editor [mailto:rfc-ed@ISI.EDU]
Sent: Monday, June 14, 1999 11:01 AM
Cc: rfc-ed@ISI.EDU
Subject: RFC 2616 on HTTP/1.1

A new Request for Comments is now available in online RFC libraries.

RFC 2616:

Title: Hypertext Transfer Protocol -- HTTP/1.1
Author(s): R. Fielding, J. Gettys, J. Mogul, H. Frystyk,
L. Masinter, P. Leach, T. Berners-Lee
Status: Draft Standard
Date: June 1999
Mailbox: fielding@ics.uci.edu, jg@w3.org,
mogul@wrl.dec.com, frystyk@w3.org,
masinter@parc.xerox.com, paulle@microsoft.com,
Pages: 176
Characters: 422317
Obsoletes: 2068
I-D Tag: draft-ietf-http-v11-spec-rev-06.txt

URL: ftp://ftp.isi.edu/in-notes/rfc2616.txt

The Hypertext Transfer Protocol (HTTP) is an application-level
protocol for distributed, collaborative, hypermedia information
systems. It is a generic, stateless, protocol which can be used for
many tasks beyond its use for hypertext, such as name servers and
distributed object management systems, through extension of its
request methods, error codes and headers. A feature of HTTP is the
typing and negotiation of data representation, allowing systems to be
built independently of the data being transferred.

This document is a product of the HyperText Transfer Protocol Working
Group of the IETF.

This is now a Draft Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol. Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:

To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs

help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.

Content-Type: message/rfc822
Content-Location: ATT-0-88B6FDAD9522D311A2DA00805F15CE85

Date: Mon, 14 Jun 1999 13:29:24 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: multipart/mixed;

Content-Type: text/plain

Content-Type: application/octet-stream;
Content-Disposition: attachment;
Content-Location: ATT-0-86B6FDAD9522D311A2DA00805F15CE85-A

Content-type: message/external-body;

Content-Type: text/plain
Content-ID: <990614105544.RFC@RFC-EDITOR.ORG>

DOC-ID: rfc2616

Content-Type: message/external-body;
Content-Location: ATT-1-87B6FDAD9522D311A2DA00805F15CE85-r