Reschke, Ed., “ HTTP/1.1, part 7: Authentication”, Internet-Draft draft-ietf-httpbis-p7-auth-04 ( work in progress), August 2008. Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed., and J. Reschke, Ed., “ HTTP/1.1, part 6: Caching”, Internet-Draft draft-ietf-httpbis-p6-cache-04 ( work in progress), August 2008. Reschke, Ed., “ HTTP/1.1, part 5: Range Requests and Partial Responses”, Internet-Draft draft-ietf-httpbis-p5-range-04 ( work in progress), August 2008. Reschke, Ed., “ HTTP/1.1, part 4: Conditional Requests”, Internet-Draft draft-ietf-httpbis-p4-conditional-04 ( work in progress), August 2008. Reschke, Ed., “ HTTP/1.1, part 3: Message Payload and Content Negotiation”, Internet-Draft draft-ietf-httpbis-p3-payload-04 ( work in progress), August 2008. Reschke, Ed., “ HTTP/1.1, part 1: URIs, Connections, and Message Parsing”, Internet-Draft draft-ietf-httpbis-p1-messaging-04 ( work in progress), August 2008. Normative References Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed., and J. Content-Range) headers that it does not understand or implement and MUST return a 501 (Not Implemented) response in such cases. The recipient of the entity MUST NOT ignore any Content-* (e.g. If the resource could not be created or modified with the Request-URI, an appropriate error response SHOULD be given that reflects the nature of the problem. If an existing resource is modified, either the 200 (OK) or 204 (No Content) response codes SHOULD be sent to indicate successful completion of the request. If a new resource is created at the Request-URI, the origin server MUST inform the user agent via the 201 (Created) response. If the Request-URI does not point to an existing resource, and that URI is capable of being defined as a new resource by the requesting user agent, the origin server can create the resource with that URI. If the Request-URI refers to an already existing resource, the enclosed entity SHOULD be considered as a modified version of the one residing on the origin server. The PUT method requests that the enclosed entity be stored at the supplied Request-URI. Intellectual Property and Copyright Statements.Change Log (to be removed by RFC Editor before publication) Notational Conventions and Generic Grammar
![typestatus 2 9.3.4 typestatus 2 9.3.4](https://cdnimg.webstaurantstore.com/images/products/large/355768/1310705.jpg)
The changes in this draft are summarized in Appendix B.4.