Ignore:
Timestamp:
Dec 23, 2007, 5:22:38 AM (12 years ago)
Author:
julian.reschke@…
Message:

Cleanup references after switch to symbolic references (removing duplicated RFC numbers), clean up some of the references XML code.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r96 r97  
    243243   information initiative since 1990. The first version of HTTP,
    244244   referred to as HTTP/0.9, was a simple protocol for raw data transfer
    245    across the Internet. HTTP/1.0, as defined by RFC 1945 <xref target="RFC1945"/>, improved
     245   across the Internet. HTTP/1.0, as defined by <xref target="RFC1945"/>, improved
    246246   the protocol by allowing messages to be in the format of MIME-like
    247247   messages, containing metainformation about the data transferred and
     
    661661   All of the mechanisms specified in this document are described in
    662662   both prose and an augmented Backus-Naur Form (BNF) similar to that
    663    used by RFC 822 <xref target="RFC822"/>. Implementors will need to be familiar with the
     663   used by <xref target="RFC822"/>. Implementors will need to be familiar with the
    664664   notation in order to understand this specification. The augmented BNF
    665665   includes the following constructs:
     
    865865   that are not intended to be interpreted by the message parser. Words
    866866   of *TEXT &MAY; contain characters from character sets other than ISO-8859-1
    867    <xref target="ISO-8859"/> only when encoded according to the rules of RFC 2047
     867   <xref target="ISO-8859"/> only when encoded according to the rules of
    868868   <xref target="RFC2047"/>.
    869869</t>
     
    942942   additional capabilities of the sender. The &lt;major&gt; number is
    943943   incremented when the format of a message within the protocol is
    944    changed. See RFC 2145 <xref target="RFC2145"/> for a fuller explanation.
     944   changed. See <xref target="RFC2145"/> for a fuller explanation.
    945945</t>
    946946<t>
     
    965965   "HTTP/1.1" in their messages, and &MUST; do so for any message that is
    966966   not compatible with HTTP/1.0. For more details on when to send
    967    specific HTTP-Version values, see RFC 2145 <xref target="RFC2145"/>.
     967   specific HTTP-Version values, see <xref target="RFC2145"/>.
    968968</t>
    969969<t>
     
    983983<t>
    984984   Due to interoperability problems with HTTP/1.0 proxies discovered
    985    since the publication of RFC 2068 <xref target="RFC2068"/>, caching proxies &MUST;, gateways
     985   since the publication of <xref target="RFC2068"/>, caching proxies &MUST;, gateways
    986986   &MAY;, and tunnels &MUST-NOT; upgrade the request to the highest version
    987987   they support. The proxy/gateway's response to that request &MUST; be in
     
    10151015   with a scheme name followed by a colon. For definitive information on
    10161016   URL syntax and semantics, see "Uniform Resource Identifiers (URI):
    1017    Generic Syntax and Semantics," RFC 2396 <xref target="RFC2396"/> (which replaces RFCs
    1018    1738 <xref target="RFC1738"/> and RFC 1808 <xref target="RFC1808"/>). This specification adopts the
     1017   Generic Syntax and Semantics," <xref target="RFC2396"/> (which replaces <xref target="RFC1738"/>
     1018   and <xref target="RFC1808"/>). This specification adopts the
    10191019   definitions of "URI-reference", "absoluteURI", "relativeURI", "port",
    10201020   "host","abs_path", "rel_path", and "authority" from that
     
    10541054   for TCP connections on that port of that host, and the Request-URI
    10551055   for the resource is abs_path (<xref target="request-uri"/>). The use of IP addresses
    1056    in URLs &SHOULD; be avoided whenever possible (see RFC 1900 <xref target="RFC1900"/>). If
     1056   in URLs &SHOULD; be avoided whenever possible (see <xref target="RFC1900"/>). If
    10571057   the abs_path is not present in the URL, it &MUST; be given as "/" when
    10581058   used as a Request-URI for a resource (<xref target="request-uri"/>). If a proxy
     
    10801080<t>
    10811081   Characters other than those in the "reserved" set (see
    1082    RFC 2396 <xref target="RFC2396"/>) are equivalent to their ""%" HEX HEX" encoding.
     1082   <xref target="RFC2396"/>) are equivalent to their ""%" HEX HEX" encoding.
    10831083</t>
    10841084<t>
     
    11061106<t>
    11071107   The first format is preferred as an Internet standard and represents
    1108    a fixed-length subset of that defined by RFC 1123 <xref target="RFC1123"/> (an update to
    1109    RFC 822 <xref target="RFC822"/>). The other formats are described here only for
     1108   a fixed-length subset of that defined by <xref target="RFC1123"/> (an update to
     1109   <xref target="RFC822"/>). The other formats are described here only for
    11101110   compatibility with obsolete implementations.
    11111111   HTTP/1.1 clients and servers that parse the date value &MUST; accept
     
    13241324<t>
    13251325   Request (<xref target="request"/>) and Response (<xref target="response"/>) messages use the generic
    1326    message format of RFC 822 <xref target="RFC822"/> for transferring entities (the payload
     1326   message format of <xref target="RFC822"/> for transferring entities (the payload
    13271327   of the message). Both types of message consist of a start-line, zero
    13281328   or more header fields (also known as "headers"), an empty line (i.e.,
     
    13561356   request-header (&request-header-fields;), response-header (&response-header-fields;), and
    13571357   entity-header (&entity-header-fields;) fields, follow the same generic format as
    1358    that given in <xref target="RFC822" x:fmt="sec" x:sec="3.1"/> of RFC 822 <xref target="RFC822"/>. Each header field consists
     1358   that given in <xref target="RFC822" x:fmt="of" x:sec="3.1"/>. Each header field consists
    13591359   of a name followed by a colon (":") and the field value. Field names
    13601360   are case-insensitive. The field value &MAY; be preceded by any amount
     
    18051805   these performance problems and results from a prototype
    18061806   implementation are available <xref target="Pad1995"/> <xref target="Spe"/>. Implementation experience and
    1807    measurements of actual HTTP/1.1 (RFC 2068) implementations show good
     1807   measurements of actual HTTP/1.1 (<xref target="RFC2068" x:fmt="none">RFC 2068</xref>) implementations show good
    18081808   results <xref target="Nie1997"/>. Alternatives have also been explored, for example,
    18091809   T/TCP <xref target="Tou1998"/>.
     
    19381938<t>
    19391939   A proxy server &MUST-NOT; establish a HTTP/1.1 persistent connection
    1940    with an HTTP/1.0 client (but see RFC 2068 <xref target="RFC2068"/> for information and
     1940   with an HTTP/1.0 client (but see <xref target="RFC2068"/> for information and
    19411941   discussion of the problems with the Keep-Alive header implemented by
    19421942   many HTTP/1.0 clients).
     
    20752075        100 (Continue) response if such a request comes from an HTTP/1.0
    20762076        (or earlier) client. There is an exception to this rule: for
    2077         compatibility with RFC 2068, a server &MAY; send a 100 (Continue)
     2077        compatibility with <xref target="RFC2068"/>, a server &MAY; send a 100 (Continue)
    20782078        status in response to an HTTP/1.1 PUT or POST request that does
    20792079        not include an Expect request-header field with the "100-continue"
     
    23022302   The Date general-header field represents the date and time at which
    23032303   the message was originated, having the same semantics as orig-date in
    2304    RFC 822. The field value is an HTTP-date, as described in <xref target="full.date"/>;
     2304   <xref target="RFC822"/>. The field value is an HTTP-date, as described in <xref target="full.date"/>;
    23052305   it &MUST; be sent in rfc1123-date format.
    23062306</t>
     
    24102410</t>
    24112411<t>
    2412    See sections <xref target="the.resource.identified.by.a.request" format="counter"/>
     2412   See Sections <xref target="the.resource.identified.by.a.request" format="counter"/>
    24132413   and <xref target="changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses" format="counter"/>
    24142414   for other requirements relating to Host.
     
    26252625   agent and the server on requests, and between the origin server and
    26262626   the client on responses. It is analogous to the "Received" field of
    2627    RFC 822 <xref target="RFC822"/> and is intended to be used for tracking message forwards,
     2627   <xref target="RFC822"/> and is intended to be used for tracking message forwards,
    26282628   avoiding request loops, and identifying the protocol capabilities of
    26292629   all senders along the request/response chain.
     
    28592859<t>
    28602860   This specification makes heavy use of the augmented BNF and generic
    2861    constructs defined by David H. Crocker for RFC 822 <xref target="RFC822"/>. Similarly, it
     2861   constructs defined by David H. Crocker for <xref target="RFC822"/>. Similarly, it
    28622862   reuses many of the definitions provided by Nathaniel Borenstein and
    28632863   Ned Freed for MIME <xref target="RFC2045"/>. We hope that their inclusion in this
     
    32043204
    32053205<reference anchor="RFC1738">
    3206 <front>
    3207 <title>Uniform Resource Locators (URL)</title>
    3208 <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
    3209 <organization>CERN, World-Wide Web project</organization>
    3210 <address>
    3211 <postal>
    3212 <street>1211 Geneva 23</street>
    3213 <city/>
    3214 <region/>
    3215 <code/>
    3216 <country>CH</country></postal>
    3217 <phone>+41 22 7673755</phone>
    3218 <facsimile>+41 22 7677155</facsimile>
    3219 <email>timbl@info.cern.ch</email></address></author>
    3220 <author initials="L." surname="Masinter" fullname="Larry Masinter">
    3221 <organization>Xerox PARC</organization>
    3222 <address>
    3223 <postal>
    3224 <street>3333 Coyote Hill Road</street>
    3225 <city>Palo Alto</city>
    3226 <region>CA</region>
    3227 <code>94034</code>
    3228 <country>US</country></postal>
    3229 <phone>+1 415 812 4365</phone>
    3230 <facsimile>+1 415 812 4333</facsimile>
    3231 <email>masinter@parc.xerox.com</email></address></author>
    3232 <author initials="M." surname="McCahill" fullname="Mark McCahill">
    3233 <organization>University of Minnesota, Computer and Information Services</organization>
    3234 <address>
    3235 <postal>
    3236 <street>100 Union Street SE, Shepherd Labs</street>
    3237 <street>Room 152</street>
    3238 <city>Minneapolis</city>
    3239 <region>MN</region>
    3240 <code>55455</code>
    3241 <country>US</country></postal>
    3242 <phone>+1 612 625 1300</phone>
    3243 <email>mpm@boombox.micro.umn.edu</email></address></author>
    3244 <date month="December" year="1994"/>
    3245 </front>
    3246 <seriesInfo name="RFC" value="1738"/>
     3206  <front>
     3207    <title>Uniform Resource Locators (URL)</title>
     3208    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
     3209      <organization>CERN, World-Wide Web project</organization>
     3210      <address><email>timbl@info.cern.ch</email></address>
     3211    </author>
     3212    <author initials="L." surname="Masinter" fullname="Larry Masinter">
     3213      <organization>Xerox PARC</organization>
     3214      <address><email>masinter@parc.xerox.com</email></address>
     3215    </author>
     3216    <author initials="M." surname="McCahill" fullname="Mark McCahill">
     3217      <organization>University of Minnesota, Computer and Information Services</organization>
     3218      <address><email>mpm@boombox.micro.umn.edu</email></address>
     3219    </author>
     3220    <date month="December" year="1994"/>
     3221  </front>
     3222  <seriesInfo name="RFC" value="1738"/>
    32473223</reference>
    32483224
    32493225<reference anchor="RFC1945">
    3250 <front>
    3251 <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
    3252 <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
    3253 <organization>MIT, Laboratory for Computer Science</organization>
    3254 <address>
    3255 <postal>
    3256 <street>545 Technology Square</street>
    3257 <city>Cambridge</city>
    3258 <region>MA</region>
    3259 <code>02139</code>
    3260 <country>US</country></postal>
    3261 <phone/>
    3262 <facsimile>+1 617 258 8682</facsimile>
    3263 <email>timbl@w3.org</email></address></author>
    3264 <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
    3265 <organization>University of California, Irvine, Department of Information and Computer Science</organization>
    3266 <address>
    3267 <postal>
    3268 <street/>
    3269 <city>Irvine</city>
    3270 <region>CA</region>
    3271 <code>92717-3425</code>
    3272 <country>US</country></postal>
    3273 <phone/>
    3274 <facsimile>+1 714 824 4056</facsimile>
    3275 <email>fielding@ics.uci.edu</email></address></author>
    3276 <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
    3277 <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
    3278 <address>
    3279 <postal>
    3280 <street>545 Technology Square</street>
    3281 <city>Cambridge</city>
    3282 <region>MA</region>
    3283 <code>02139</code>
    3284 <country>US</country></postal>
    3285 <phone/>
    3286 <facsimile>+1 617 258 8682</facsimile>
    3287 <email>frystyk@w3.org</email></address></author>
    3288 <date month="May" year="1996"/>
    3289 </front>
    3290 <seriesInfo name="RFC" value="1945"/>
     3226  <front>
     3227    <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
     3228    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
     3229      <organization>MIT, Laboratory for Computer Science</organization>
     3230      <address><email>timbl@w3.org</email></address>
     3231    </author>
     3232    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
     3233      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
     3234      <address><email>fielding@ics.uci.edu</email></address>
     3235    </author>
     3236    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
     3237      <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
     3238      <address><email>frystyk@w3.org</email></address>
     3239    </author>
     3240    <date month="May" year="1996"/>
     3241  </front>
     3242  <seriesInfo name="RFC" value="1945"/>
    32913243</reference>
    32923244
    32933245<reference anchor="RFC2045">
    3294 <front>
    3295 <title abbrev="Internet Message Bodies">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title>
    3296 <author initials="N." surname="Freed" fullname="Ned Freed">
    3297 <organization>Innosoft International, Inc.</organization>
    3298 <address>
    3299 <postal>
    3300 <street>1050 East Garvey Avenue South</street>
    3301 <city>West Covina</city>
    3302 <region>CA</region>
    3303 <code>91790</code>
    3304 <country>US</country></postal>
    3305 <phone>+1 818 919 3600</phone>
    3306 <facsimile>+1 818 919 3614</facsimile>
    3307 <email>ned@innosoft.com</email></address></author>
    3308 <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">
    3309 <organization>First Virtual Holdings</organization>
    3310 <address>
    3311 <postal>
    3312 <street>25 Washington Avenue</street>
    3313 <city>Morristown</city>
    3314 <region>NJ</region>
    3315 <code>07960</code>
    3316 <country>US</country></postal>
    3317 <phone>+1 201 540 8967</phone>
    3318 <facsimile>+1 201 993 3032</facsimile>
    3319 <email>nsb@nsb.fv.com</email></address></author>
    3320 <date month="November" year="1996"/>
    3321 </front>
    3322 <seriesInfo name="RFC" value="2045"/>
     3246  <front>
     3247    <title abbrev="Internet Message Bodies">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title>
     3248    <author initials="N." surname="Freed" fullname="Ned Freed">
     3249      <organization>Innosoft International, Inc.</organization>
     3250      <address><email>ned@innosoft.com</email></address>
     3251    </author>
     3252    <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">
     3253      <organization>First Virtual Holdings</organization>
     3254      <address><email>nsb@nsb.fv.com</email></address>
     3255    </author>
     3256    <date month="November" year="1996"/>
     3257  </front>
     3258  <seriesInfo name="RFC" value="2045"/>
    33233259</reference>
    33243260
    33253261<reference anchor="RFC1123">
    3326 <front>
    3327 <title>Requirements for Internet Hosts - Application and Support</title>
    3328 <author initials="R." surname="Braden" fullname="Robert Braden">
    3329 <organization>University of Southern California (USC), Information Sciences Institute</organization>
    3330 <address>
    3331 <postal>
    3332 <street>4676 Admiralty Way</street>
    3333 <city>Marina del Rey</city>
    3334 <region>CA</region>
    3335 <code>90292-6695</code>
    3336 <country>US</country></postal>
    3337 <phone>+1 213 822 1511</phone>
    3338 <email>Braden@ISI.EDU</email></address></author>
    3339 <date month="October" year="1989"/></front>
    3340 <seriesInfo name="STD" value="3"/>
    3341 <seriesInfo name="RFC" value="1123"/>
     3262  <front>
     3263    <title>Requirements for Internet Hosts - Application and Support</title>
     3264    <author initials="R." surname="Braden" fullname="Robert Braden">
     3265      <organization>University of Southern California (USC), Information Sciences Institute</organization>
     3266      <address><email>Braden@ISI.EDU</email></address>
     3267    </author>
     3268    <date month="October" year="1989"/>
     3269  </front>
     3270  <seriesInfo name="STD" value="3"/>
     3271  <seriesInfo name="RFC" value="1123"/>
    33423272</reference>
    33433273
    33443274<reference anchor="RFC822">
    3345 <front>
    3346 <title abbrev="Standard for ARPA Internet Text Messages">Standard for the format of ARPA Internet text messages</title>
    3347 <author initials="D.H." surname="Crocker" fullname="David H. Crocker">
    3348 <organization>University of Delaware, Dept. of Electrical Engineering</organization>
    3349 <address>
    3350 <postal>
    3351 <street/>
    3352 <city>Newark</city>
    3353 <region>DE</region>
    3354 <code>19711</code>
    3355 <country>US</country></postal>
    3356 <email>DCrocker@UDel-Relay</email></address></author>
    3357 <date month="August" day="13" year="1982"/></front>
    3358 <seriesInfo name="STD" value="11"/>
    3359 <seriesInfo name="RFC" value="822"/>
     3275  <front>
     3276    <title abbrev="Standard for ARPA Internet Text Messages">Standard for the format of ARPA Internet text messages</title>
     3277    <author initials="D.H." surname="Crocker" fullname="David H. Crocker">
     3278      <organization>University of Delaware, Dept. of Electrical Engineering</organization>
     3279      <address><email>DCrocker@UDel-Relay</email></address>
     3280    </author>
     3281    <date month="August" day="13" year="1982"/>
     3282  </front>
     3283  <seriesInfo name="STD" value="11"/>
     3284  <seriesInfo name="RFC" value="822"/>
    33603285</reference>
    33613286
     
    33923317
    33933318<reference anchor="RFC1808">
    3394 <front>
    3395 <title>Relative Uniform Resource Locators</title>
    3396 <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
    3397 <organization>University of California Irvine, Department of Information and Computer Science</organization>
    3398 <address>
    3399 <postal>
    3400 <street/>
    3401 <city>Irvine</city>
    3402 <region>CA</region>
    3403 <code>92717-3425</code>
    3404 <country>US</country></postal>
    3405 <phone>+1 714 824 4049</phone>
    3406 <facsimile>+1 714 824 4056</facsimile>
    3407 <email>fielding@ics.uci.edu</email></address></author>
    3408 <date month="June" year="1995"/>
    3409 </front>
    3410 <seriesInfo name="RFC" value="1808"/>
     3319  <front>
     3320    <title>Relative Uniform Resource Locators</title>
     3321    <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
     3322      <organization>University of California Irvine, Department of Information and Computer Science</organization>
     3323      <address><email>fielding@ics.uci.edu</email></address>
     3324    </author>
     3325    <date month="June" year="1995"/>
     3326  </front>
     3327  <seriesInfo name="RFC" value="1808"/>
    34113328</reference>
    34123329
     
    34253342
    34263343<reference anchor="RFC2047">
    3427 <front>
    3428 <title abbrev="Message Header Extensions">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</title>
    3429 <author initials="K." surname="Moore" fullname="Keith Moore">
    3430 <organization>University of Tennessee</organization>
    3431 <address>
    3432 <postal>
    3433 <street>107 Ayres Hall</street>
    3434 <street>Knoxville TN 37996-1301</street></postal>
    3435 <email>moore@cs.utk.edu</email></address></author>
    3436 <date month="November" year="1996"/>
    3437 <area>Applications</area>
    3438 <keyword>Amercian Standard Code for Information Interchange</keyword>
    3439 <keyword>mail</keyword>
    3440 <keyword>multipurpose internet mail extensions</keyword>
    3441 </front>
    3442 <seriesInfo name="RFC" value="2047"/>
     3344  <front>
     3345    <title abbrev="Message Header Extensions">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</title>
     3346    <author initials="K." surname="Moore" fullname="Keith Moore">
     3347      <organization>University of Tennessee</organization>
     3348      <address><email>moore@cs.utk.edu</email></address>
     3349    </author>
     3350    <date month="November" year="1996"/>
     3351  </front>
     3352  <seriesInfo name="RFC" value="2047"/>
    34433353</reference>
    34443354
     
    35573467
    35583468<reference anchor="RFC1900">
    3559 <front>
    3560 <title>Renumbering Needs Work</title>
    3561 <author initials="B." surname="Carpenter" fullname="Brian E. Carpenter">
    3562 <organization>CERN, Computing and Networks Division</organization>
    3563 <address>
    3564 <postal>
    3565 <street>1211 Geneva 23</street>
    3566 <country>CH</country></postal>
    3567 <phone>+41 22 7674967</phone>
    3568 <facsimile>+41 22 7677155</facsimile>
    3569 <email>brian@dxcoms.cern.ch</email></address></author>
    3570 <author initials="Y." surname="Rekhter" fullname="Yakov Rekhter">
    3571 <organization>cisco Systems</organization>
    3572 <address>
    3573 <postal>
    3574 <street>170 West Tasman Drive</street>
    3575 <city>San Jose</city>
    3576 <region>CA</region>
    3577 <code>95134</code>
    3578 <country>US</country></postal>
    3579 <phone>+1 914 528 0090</phone>
    3580 <email>yakov@cisco.com</email></address></author>
    3581 <date month="February" year="1996"/>
    3582 </front>
    3583 <seriesInfo name="RFC" value="1900"/>
     3469  <front>
     3470    <title>Renumbering Needs Work</title>
     3471    <author initials="B." surname="Carpenter" fullname="Brian E. Carpenter">
     3472      <organization>CERN, Computing and Networks Division</organization>
     3473      <address><email>brian@dxcoms.cern.ch</email></address>
     3474    </author>
     3475    <author initials="Y." surname="Rekhter" fullname="Yakov Rekhter">
     3476      <organization>cisco Systems</organization>
     3477      <address><email>yakov@cisco.com</email></address>
     3478    </author>
     3479    <date month="February" year="1996"/>
     3480  </front>
     3481  <seriesInfo name="RFC" value="1900"/>
    35843482</reference>
    35853483
     
    36493547
    36503548<reference anchor="RFC2068">
    3651 <front>
    3652 <title abbrev="HTTP/1.1">Hypertext Transfer Protocol -- HTTP/1.1</title>
    3653 <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
    3654 <organization>University of California, Irvine, Department of Information and Computer Science</organization>
    3655 <address>
    3656 <postal>
    3657 <street/>
    3658 <city>Irvine</city>
    3659 <region>CA</region>
    3660 <code>92717-3425</code>
    3661 <country>US</country></postal>
    3662 <facsimile>+1 714 824 4056</facsimile>
    3663 <email>fielding@ics.uci.edu</email></address></author>
    3664 <author initials="J." surname="Gettys" fullname="Jim Gettys">
    3665 <organization>MIT Laboratory for Computer Science</organization>
    3666 <address>
    3667 <postal>
    3668 <street>545 Technology Square</street>
    3669 <city>Cambridge</city>
    3670 <region>MA</region>
    3671 <code>02139</code>
    3672 <country>US</country></postal>
    3673 <facsimile>+1 617 258 8682</facsimile>
    3674 <email>jg@w3.org</email></address></author>
    3675 <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
    3676 <organization>Digital Equipment Corporation, Western Research Laboratory</organization>
    3677 <address>
    3678 <postal>
    3679 <street>250 University Avenue</street>
    3680 <city>Palo Alto</city>
    3681 <region>CA</region>
    3682 <code>94301</code>
    3683 <country>US</country></postal>
    3684 <email>mogul@wrl.dec.com</email></address></author>
    3685 <author initials="H." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
    3686 <organization>MIT Laboratory for Computer Science</organization>
    3687 <address>
    3688 <postal>
    3689 <street>545 Technology Square</street>
    3690 <city>Cambridge</city>
    3691 <region>MA</region>
    3692 <code>02139</code>
    3693 <country>US</country></postal>
    3694 <facsimile>+1 617 258 8682</facsimile>
    3695 <email>frystyk@w3.org</email></address></author>
    3696 <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
    3697 <organization>MIT Laboratory for Computer Science</organization>
    3698 <address>
    3699 <postal>
    3700 <street>545 Technology Square</street>
    3701 <city>Cambridge</city>
    3702 <region>MA</region>
    3703 <code>02139</code>
    3704 <country>US</country></postal>
    3705 <facsimile>+1 617 258 8682</facsimile>
    3706 <email>timbl@w3.org</email></address></author>
    3707 <date month="January" year="1997"/>
    3708 <abstract>
    3709 <t>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. It is a generic, stateless, object-oriented protocol which can be used for many tasks, such as name servers and distributed object management systems, through extension of its request methods. A feature of HTTP is the typing and negotiation of data representation, allowing systems to be built independently of the data being transferred.</t>
    3710 <t>HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification defines the protocol referred to as "HTTP/1.1".</t></abstract></front>
    3711 <seriesInfo name="RFC" value="2068"/>
     3549  <front>
     3550    <title abbrev="HTTP/1.1">Hypertext Transfer Protocol -- HTTP/1.1</title>
     3551    <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
     3552      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
     3553      <address><email>fielding@ics.uci.edu</email></address>
     3554    </author>
     3555    <author initials="J." surname="Gettys" fullname="Jim Gettys">
     3556      <organization>MIT Laboratory for Computer Science</organization>
     3557      <address><email>jg@w3.org</email></address>
     3558    </author>
     3559    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
     3560      <organization>Digital Equipment Corporation, Western Research Laboratory</organization>
     3561      <address><email>mogul@wrl.dec.com</email></address>
     3562    </author>
     3563    <author initials="H." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
     3564      <organization>MIT Laboratory for Computer Science</organization>
     3565      <address><email>frystyk@w3.org</email></address>
     3566    </author>
     3567    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
     3568      <organization>MIT Laboratory for Computer Science</organization>
     3569      <address><email>timbl@w3.org</email></address>
     3570    </author>
     3571    <date month="January" year="1997"/>
     3572  </front>
     3573  <seriesInfo name="RFC" value="2068"/>
    37123574</reference>
    37133575
     
    37263588
    37273589<reference anchor="RFC2145">
    3728 <front>
    3729 <title abbrev="HTTP Version Numbers">Use and Interpretation of HTTP Version Numbers</title>
    3730 <author initials="J.C." surname="Mogul" fullname="Jeffrey C. Mogul">
    3731 <organization>Western Research Laboratory</organization>
    3732 <address>
    3733 <postal>
    3734 <street>Digital Equipment Corporation</street>
    3735 <street>250 University Avenue</street>
    3736 <street>Palo Alto</street>
    3737 <street>California</street>
    3738 <street>94305</street>
    3739 <country>USA</country></postal>
    3740 <email>mogul@wrl.dec.com</email></address></author>
    3741 <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
    3742 <organization>Department of Information and Computer Science</organization>
    3743 <address>
    3744 <postal>
    3745 <street>University of California</street>
    3746 <street>Irvine</street>
    3747 <street>CA 92717-3425</street>
    3748 <country>USA</country></postal>
    3749 <facsimile>+1 (714) 824-4056</facsimile>
    3750 <email>fielding@ics.uci.edu</email></address></author>
    3751 <author initials="J." surname="Gettys" fullname="Jim Gettys">
    3752 <organization>MIT Laboratory for Computer Science</organization>
    3753 <address>
    3754 <postal>
    3755 <street>545 Technology Square</street>
    3756 <street>Cambridge</street>
    3757 <street>MA 02139</street>
    3758 <country>USA</country></postal>
    3759 <facsimile>+1 (617) 258 8682</facsimile>
    3760 <email>jg@w3.org</email></address></author>
    3761 <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
    3762 <organization>W3 Consortium</organization>
    3763 <address>
    3764 <postal>
    3765 <street>MIT Laboratory for Computer Science</street>
    3766 <street>545 Technology Square</street>
    3767 <street>Cambridge</street>
    3768 <street>MA 02139</street>
    3769 <country>USA</country></postal>
    3770 <facsimile>+1 (617) 258 8682</facsimile>
    3771 <email>frystyk@w3.org</email></address></author>
    3772 <date month="May" year="1997"/>
    3773 <area>Applications</area>
    3774 <keyword>HTTP</keyword>
    3775 <keyword>hypertext transfer protocol</keyword>
    3776 <abstract>
    3777 <t>
    3778    HTTP request and response messages include an HTTP protocol version
    3779    number.  Some confusion exists concerning the proper use and
    3780    interpretation of HTTP version numbers, and concerning
    3781    interoperability of HTTP implementations of different protocol
    3782    versions.  This document is an attempt to clarify the situation.  It
    3783    is not a modification of the intended meaning of the existing
    3784    HTTP/1.0 and HTTP/1.1 documents, but it does describe the intention
    3785    of the authors of those documents, and can be considered definitive
    3786    when there is any ambiguity in those documents concerning HTTP
    3787    version numbers, for all versions of HTTP.
    3788 </t></abstract></front>
    3789 <seriesInfo name="RFC" value="2145"/>
     3590  <front>
     3591    <title abbrev="HTTP Version Numbers">Use and Interpretation of HTTP Version Numbers</title>
     3592    <author initials="J.C." surname="Mogul" fullname="Jeffrey C. Mogul">
     3593      <organization>Western Research Laboratory</organization>
     3594      <address><email>mogul@wrl.dec.com</email></address>
     3595    </author>
     3596    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
     3597      <organization>Department of Information and Computer Science</organization>
     3598      <address><email>fielding@ics.uci.edu</email></address>
     3599    </author>
     3600    <author initials="J." surname="Gettys" fullname="Jim Gettys">
     3601      <organization>MIT Laboratory for Computer Science</organization>
     3602      <address><email>jg@w3.org</email></address>
     3603    </author>
     3604    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
     3605      <organization>W3 Consortium</organization>
     3606      <address><email>frystyk@w3.org</email></address>
     3607    </author>
     3608    <date month="May" year="1997"/>
     3609  </front>
     3610  <seriesInfo name="RFC" value="2145"/>
    37903611</reference>
    37913612
     
    38143635
    38153636<reference anchor="RFC2396">
    3816 <front>
    3817 <title abbrev="URI Generic Syntax">Uniform Resource Identifiers (URI): Generic Syntax</title>
    3818 <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
    3819 <organization abbrev="MIT/LCS">World Wide Web Consortium</organization>
    3820 <address>
    3821 <postal>
    3822 <street>MIT Laboratory for Computer Science, NE43-356</street>
    3823 <street>545 Technology Square</street>
    3824 <city>Cambridge</city>
    3825 <region>MA</region>
    3826 <code>02139</code></postal>
    3827 <facsimile>+1(617)258-8682</facsimile>
    3828 <email>timbl@w3.org</email></address></author>
    3829 <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
    3830 <organization abbrev="U.C. Irvine">Department of Information and Computer Science</organization>
    3831 <address>
    3832 <postal>
    3833 <street>University of California, Irvine</street>
    3834 <city>Irvine</city>
    3835 <region>CA</region>
    3836 <code>92697-3425</code></postal>
    3837 <facsimile>+1(949)824-1715</facsimile>
    3838 <email>fielding@ics.uci.edu</email></address></author>
    3839 <author initials="L." surname="Masinter" fullname="Larry Masinter">
    3840 <organization abbrev="Xerox Corporation">Xerox PARC</organization>
    3841 <address>
    3842 <postal>
    3843 <street>3333 Coyote Hill Road</street>
    3844 <city>Palo Alto</city>
    3845 <region>CA</region>
    3846 <code>94034</code></postal>
    3847 <facsimile>+1(415)812-4333</facsimile>
    3848 <email>masinter@parc.xerox.com</email></address></author>
    3849 <date month="August" year="1998"/>
    3850 <area>Applications</area>
    3851 <keyword>uniform resource</keyword>
    3852 <keyword>URI</keyword>
    3853 </front>
    3854 <seriesInfo name="RFC" value="2396"/>
     3637  <front>
     3638    <title abbrev="URI Generic Syntax">Uniform Resource Identifiers (URI): Generic Syntax</title>
     3639    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
     3640      <organization abbrev="MIT/LCS">World Wide Web Consortium</organization>
     3641      <address><email>timbl@w3.org</email></address>
     3642    </author>
     3643    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
     3644      <organization abbrev="U.C. Irvine">Department of Information and Computer Science</organization>
     3645      <address><email>fielding@ics.uci.edu</email></address>
     3646    </author>
     3647    <author initials="L." surname="Masinter" fullname="Larry Masinter">
     3648      <organization abbrev="Xerox Corporation">Xerox PARC</organization>
     3649      <address><email>masinter@parc.xerox.com</email></address>
     3650    </author>
     3651    <date month="August" year="1998"/>
     3652  </front>
     3653  <seriesInfo name="RFC" value="2396"/>
    38553654</reference>
    38563655
     
    40583857   by the client prior to the request and closed by the server after
    40593858   sending the response. Some implementations implement the Keep-Alive
    4060    version of persistent connections described in <xref x:sec="19.7.1" x:fmt="sec" target="RFC2068"/> of RFC
    4061    2068 <xref target="RFC2068"/>.
     3859   version of persistent connections described in <xref x:sec="19.7.1" x:fmt="of" target="RFC2068"/>.
    40623860</t>
    40633861
     
    41333931<t>
    41343932   The original HTTP/1.0 form of persistent connections (the Connection:
    4135    Keep-Alive and Keep-Alive header) is documented in RFC 2068. <xref target="RFC2068"/>
     3933   Keep-Alive and Keep-Alive header) is documented in <xref target="RFC2068"/>.
    41363934</t>
    41373935</section>
     
    41413939   This specification has been carefully audited to correct and
    41423940   disambiguate key word usage; RFC 2068 had many problems in respect to
    4143    the conventions laid out in RFC 2119 <xref target="RFC2119"/>.
     3941   the conventions laid out in <xref target="RFC2119"/>.
    41443942</t>
    41453943<t>
     
    41513949<t>
    41523950   The use and interpretation of HTTP version numbers has been clarified
    4153    by RFC 2145. Require proxies to upgrade requests to highest protocol
     3951   by <xref target="RFC2145"/>. Require proxies to upgrade requests to highest protocol
    41543952   version they support to deal with problems discovered in HTTP/1.0
    41553953   implementations (<xref target="http.version"/>)
Note: See TracChangeset for help on using the changeset viewer.