Changeset 2196 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 03/03/13 14:29:49 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r2195 r2196 449 449 } 450 450 @bottom-center { 451 content: "Expires September 2, 2013";451 content: "Expires September 4, 2013"; 452 452 } 453 453 @bottom-right { … … 494 494 <meta name="dct.creator" content="Reschke, J. F."> 495 495 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 496 <meta name="dct.issued" scheme="ISO8601" content="2013-03-0 1">496 <meta name="dct.issued" scheme="ISO8601" content="2013-03-03"> 497 497 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 498 498 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation."> … … 522 522 <tr> 523 523 <td class="left">Intended status: Standards Track</td> 524 <td class="right">March 1, 2013</td>524 <td class="right">March 3, 2013</td> 525 525 </tr> 526 526 <tr> 527 <td class="left">Expires: September 2, 2013</td>527 <td class="left">Expires: September 4, 2013</td> 528 528 <td class="right"></td> 529 529 </tr> … … 553 553 in progress”. 554 554 </p> 555 <p>This Internet-Draft will expire on September 2, 2013.</p>555 <p>This Internet-Draft will expire on September 4, 2013.</p> 556 556 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 557 557 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 3321 3321 if the response they occur in has explicit freshness information; however, status codes that are defined as being cacheable 3322 3322 are allowed to be cached without explicit freshness information. Likewise, the definition of a status code can place constraints 3323 upon cache behavio ur. See <a href="#Part6" id="rfc.xref.Part6.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a> for more information.3323 upon cache behavior. See <a href="#Part6" id="rfc.xref.Part6.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a> for more information. 3324 3324 </p> 3325 3325 <p id="rfc.section.8.2.2.p.6">Finally, the definition of a new status code ought to indicate whether the payload has any implied association with an identified … … 3855 3855 <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a> <a id="attack.pathname" href="#attack.pathname">Attacks Based On File and Path Names</a></h2> 3856 3856 <p id="rfc.section.9.1.p.1">Origin servers frequently make use of their local file system to manage the mapping from effective request URI to resource 3857 representations. Implement ors need to be aware that most file systems are not designed to protect against malicious file or3857 representations. Implementers need to be aware that most file systems are not designed to protect against malicious file or 3858 3858 path names, and thus depend on the origin server to avoid mapping to file names, folders, or directories that have special 3859 3859 significance to the system.
Note: See TracChangeset
for help on using the changeset viewer.