Ignore:
Timestamp:
Oct 18, 2010, 11:02:09 PM (9 years ago)
Author:
mnot@…
Message:

Explain requirements for new method registrations; addresses #230.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1032 r1034  
    481481  The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-methods"/>.
    482482</t>
     483
     484<section title="Considerations for New Methods">
     485
     486  <t>When it is necessary to express new semantics for a HTTP request that
     487  aren't specific to a single application or media type, and currently defined
     488  methods are inadequate, it may be appropriate to register a new method.</t>
     489
     490  <t>New methods &SHOULD; be potentially applicable to any resource. I.e.,
     491  they should not be specific to any particular media type, "type" of
     492  resource, or application.</t>
     493
     494  <t>New methods &MUST-NOT; prohibit a message-body on either the request or
     495  the response message; however they &MAY; specify that only a zero-length
     496  body is allowed.</t>
     497
     498  <t>New methods &MUST; define whether they are safe (<xref
     499  target="safe.methods"/>) and whether they are idempotent (<xref
     500  target="idempotent.methods"/>). They &MUST; also state whether they can be
     501  cached (&caching;); in particular what conditions a cache may store the
     502  response, and under what conditions such a stored response may be used to
     503  satisfy a subsequent request.</t>
     504
     505  <t>New methods &SHOULD; explain how conditional request headers
     506  (&conditional;) affect the response (if there is any effect).</t>
     507
     508  <t>HTTP methods &SHOULD; be registered in a document that isn't specific to
     509  an application or other use of HTTP, so that it's clear that they are not
     510  specific to that application or extension.</t>
     511
     512</section>
     513
    483514</section>
    484515</section>
Note: See TracChangeset for help on using the changeset viewer.