RFC 2109 on HTTP State Management Mechanism

To: IETF-Announce: ;
Subject: RFC 2109 on HTTP State Management Mechanism
Cc: rfc-ed@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Tue, 18 Feb 97 12:48:41 PST
Sender:ietf-announce-request@ietf.org
From: RFC Editor <rfc-ed@isi.edu>


--NextPart


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


        RFC 2109:

        Title:      HTTP State Management Mechanism
        Author:     D. Kristol, L. Montulli
        Date:       February 1997
        Mailbox:    dmk@bell-labs.com, montulli@netscape.com
        Pages:      21
        Characters: 43649
        Updates/Obsoletes: None

        URL:        ftp://ds.internic.net/rfc/rfc2109.txt


This document specifies a way to create a stateful session with HTTP
requests and responses.  It describes two new headers, Cookie and
Set-Cookie, which carry state information between participating origin
servers and user agents. This document is a product of the HyperText
Transfer Protocol Working Group of the IETF.

This is now a Proposed 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@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

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

        To: rfc-info@ISI.EDU
        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 admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Mary Kennedy
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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="mailserv@ds.internic.net"

Content-Type: text/plain
Content-ID: <970212095025.RFC@ISI.EDU>

SEND /rfc/rfc2109.txt

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc2109.txt";
        site="ds.internic.net";
        access-type="anon-ftp";
        directory="rfc"

Content-Type: text/plain
Content-ID: <970212095025.RFC@ISI.EDU>

--OtherAccess--
--NextPart--

Received on Wednesday, 19 February 1997 09:36:20 UTC