Changeset 1458 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 27/10/11 19:55:03 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1452 r1458 359 359 } 360 360 @bottom-center { 361 content: "Expires April 2 5, 2012";361 content: "Expires April 29, 2012"; 362 362 } 363 363 @bottom-right { … … 409 409 <meta name="dct.creator" content="Reschke, J. F."> 410 410 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 411 <meta name="dct.issued" scheme="ISO8601" content="2011-10-2 3">411 <meta name="dct.issued" scheme="ISO8601" content="2011-10-27"> 412 412 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 413 413 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields."> … … 440 440 </tr> 441 441 <tr> 442 <td class="left">Expires: April 2 5, 2012</td>442 <td class="left">Expires: April 29, 2012</td> 443 443 <td class="right">HP</td> 444 444 </tr> … … 493 493 <tr> 494 494 <td class="left"></td> 495 <td class="right">October 2 3, 2011</td>495 <td class="right">October 27, 2011</td> 496 496 </tr> 497 497 </tbody> … … 523 523 in progress”. 524 524 </p> 525 <p>This Internet-Draft will expire on April 2 5, 2012.</p>525 <p>This Internet-Draft will expire on April 29, 2012.</p> 526 526 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 527 527 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 887 887 <p>If it does not use the list syntax, how to treat messages where the header field occurs multiple times (a sensible default 888 888 would be to ignore the header field, but this might not always be the right choice). 889 </p> 890 <p>Furthermore, intermediaries and software libraries might combine multiple header field instances into a single one, despite 891 the header field not allowing this. A robust format enables recipients to discover these situations (good example: "Content-Type", 892 as the comma can only appear inside quoted strings; bad example: "Location", as a comma can occur inside a URI). 889 893 </p> 890 894 </li>
Note: See TracChangeset
for help on using the changeset viewer.