Jan 11, 2008, 7:39:06 PM (12 years ago)

editorial: write preliminary introduction to p2 noting future reorg

1 edited


  • draft-ietf-httpbis/latest/p2-semantics.xml

    r153 r162  
    2222  <!ENTITY auth                       "<xref target='Part7' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2323  <!ENTITY content-negotiation        "<xref target='Part3' x:rel='#content.negotiation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    24   <!ENTITY diff2045entity             "<xref target='Part3' x:rel='#differences.between.http.entities.and.rfc.2045.entities' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2524  <!ENTITY uri                        "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2625  <!ENTITY http-url                   "<xref target='Part1' x:rel='#http-url' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    245244<section title="Introduction" anchor="introduction">
    247    This document will define aspects of HTTP related to request and response
    248    semantics. Right now it only includes the extracted relevant sections of
    249    RFC 2616 with only minor edits.
    250 </t>
    251 <t>
    252    The HTTP protocol is a request/response protocol. A client sends a
    253    request to the server in the form of a request method, URI, and
    254    protocol version, followed by a MIME-like message containing request
    255    modifiers, client information, and possible body content over a
    256    connection with a server. The server responds with a status line,
    257    including the message's protocol version and a success or error code,
    258    followed by a MIME-like message containing server information, entity
    259    metainformation, and possible entity-body content. The relationship
    260    between HTTP and MIME is described in &diff2045entity;.
     246   This document defines HTTP/1.1 request and response semantics.  Each HTTP
     247   message, as defined in &messaging;, is in the form of either a request or
     248   a response.  An HTTP server listens on a connection for HTTP requests and
     249   responds to each request, in the order received on that connection, with
     250   one or more HTTP response messages.  This document defines the commonly
     251   agreed upon semantics of the HTTP uniform interface, the intentions defined
     252   by each request method, and the various response messages that might be
     253   expected as a result of applying that method for the requested resource.
     256   This document is currently disorganized in order to minimize the changes
     257   between drafts and enable reviewers to see the smaller errata changes.
     258   The next draft will reorganize the sections to better reflect the content.
     259   In particular, the sections will be ordered according to the typical
     260   processing of an HTTP request message (after message parsing): resource
     261   mapping, general header fields, methods, request modifiers, response
     262   status, and resource metadata.  The current mess reflects how widely
     263   dispersed these topics and associated requirements had become in
     264   <xref target="RFC2616"/>.
Note: See TracChangeset for help on using the changeset viewer.