Changeset 1042 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 22/10/10 02:05:57 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r1040 r1042 489 489 </t> 490 490 <t> 491 New methods &SHOULD; be potentially applicable to any resource. I.e., 492 they should not be specific to any particular media type, "type" of 493 resource, or application. 491 HTTP methods are generic; that is, they are potentially applicable to any 492 resource, not just one particular media type, "type" of resource, or 493 application. As such, it is preferred that new HTTP methods be registered 494 in a document that isn't specific to a single application, so that this is 495 clear. 494 496 </t> 495 497 <t> … … 501 503 </t> 502 504 <t> 503 New method s &MUST; define whether they are safe (<xref505 New method definitions need to indicate whether they are safe (<xref 504 506 target="safe.methods"/>) and whether they are idempotent (<xref 505 target="idempotent.methods"/>). They &MUST; also state whether they can be507 target="idempotent.methods"/>). They also need to state whether they can be 506 508 cached (&caching;); in particular what conditions a cache may store the 507 509 response, and under what conditions such a stored response may be used to 508 510 satisfy a subsequent request. 509 </t>510 <t>511 New methods &SHOULD; explain how conditional request headers512 (&conditional;) affect the response (if there is any effect).513 </t>514 <t>515 HTTP methods &SHOULD; be registered in a document that isn't specific to516 a single application or other use of HTTP, so that it's clear that they are517 not specific to that application or extension.518 511 </t> 519 512 </section>
Note: See TracChangeset
for help on using the changeset viewer.